I have an interview for a [job title] role at [company name]. First look up the company's recent news and the usual interview format for this kind of role. Then run a mock interview with me one question at a time, mixing behavioral and role-specific questions. After each of my answers, give short honest feedback and show a stronger version using the situation, task, action, result structure. Finish with my two biggest things to improve and three good questions I should ask them.
Musecases prompts
- Template· fill in the highlighted words
Draft a delayed-flight or lost-bag claim from my bookings
Something went wrong on a trip (delay, cancellation, or lost bag) and I want a clear claim draft before I send anything. What happened: . Airline or carrier: . Booking or confirmation: . 1. Find the booking confirmation, boarding passes, and any delay or baggage emails. List the facts: dates, flight numbers, routes, what was promised vs what happened. 2. Look up the carrier's public policy for this kind of issue (compensation, expense reimbursement, baggage timeline) and summarize what I may be entitled to ask for. Label anything uncertain. 3. Draft a polite, factual claim email or form answers with: what happened, evidence I have, what I'm requesting, and my contact details placeholders. 4. List receipts or notes I should attach (hotel, meals, bag contents list) and a short checklist before I hit send. 5. Do not submit the claim, call the airline, or spend money unless I explicitly approve. Keep the tone firm and calm. If the policy clearly doesn't cover this, say so instead of overpromising. - It's open enrollment and I need to pick a plan. I'll share the plan documents or the summary page from my employer or marketplace. Compare the options side by side in plain words: monthly premium, deductible, out-of-pocket maximum, copays for common visits, prescription coverage, and whether my doctors are in network if I tell you who they are. Then ask me a few questions about how much care I expect next year and estimate my total yearly cost under each plan for a light year, a typical year, and a heavy year. Point out the deadline and anything I must actively re-select, like a health savings or flexible spending account. Don't enroll me in anything; just help me decide.
- I had Batista, my Muse conduct a treadmill repair-shop hunt produced a genuinely reusable search pattern — the brand-coverage and service-area checks are the parts most people skip. Per the routine you set up, here's the de-identified prompt draft: "I'm looking for a reputable, reasonably priced repair shop for my {{equipment type, e.g. treadmill}} made by {{brand, e.g. Horizon}}. The problem: {{describe the issue, e.g. the belt is slipping and needs a tension adjustment}}. Find 3 options and rank them best bet / runner-up / budget. Verify each one on the shop's own website — not just a directory listing: (1) they explicitly service {{brand}} equipment, checked against their serviced-brands list; (2) they do in-home visits and {{city}} is actually inside their stated service area; (3) strong reviews, 4.5+ stars with a meaningful count; (4) transparent pricing — any flat service-visit fee and warranty terms. For each shop: name, phone, distance from {{city}}, what their site says about brand coverage, and one line on the ranking. If I name my previous repair provider, check whether they're still in business and whether the silence looks like a responsiveness problem or a closure. Finish with a realistic expected price range for this kind of repair."
- Set up a self-healing watchdog for the VM you run on, following the pattern in this open-source repo: github.com/TMTrevisan/self-healing-agent-vm — read its AGENTS.md first, it has the full procedure. Context: this VM's root filesystem can be rebuilt from a base image while my home directory persists, and a rebuild can come back with pieces missing — system packages, runtimes, timezone data — which silently breaks the tools you depend on. I want that class of failure to repair itself. Do this: 1. Inventory everything your stack depends on that lives OUTSIDE my home directory (system Python stdlib, Node, tzdata, [add your own]) and stage byte-exact restore caches for them in persistent storage, using the same builds the system actually runs. For Debian/Ubuntu, extract the distro .deb packages — don't trust standalone builds, they can lack the C extension modules. 2. Install the watchdog from the repo and configure its probes for our stack: sentinel checks that still run when the system is half-broken, restores that only replace missing files (atomically, never overwriting), a trust check on the caches, timeouts on every check, and a verification pass after every heal. 3. Run it with --dry-run first. Then prove it works: move one non-critical system file aside, run the watchdog, show me the restore and the journal entry, and show me a second run reporting healthy. 4. Schedule it every [5] minutes with a heartbeat that alerts me if a run ever goes missing — silent when healthy, loud only on repairs and failures. Rules: never overwrite existing system files; caches must be owned by me or root and not group- or world-writable; keep any pip-repair step off unless we set up a pinned wheelhouse; before any step that needs elevated privileges, tell me what you're about to change.
- Set up a seasonal flu activity watch for me. Season: it starts {{date 1: October 1}} each year and ends the week I confirm I've received my flu and COVID shots. Once I confirm, pause the weekly checks until the next {{date 2: October 1}} — don't keep checking in the meantime. Weekly check: every Friday, after my state health department posts its Thursday flu update. (Example source: Minnesota Department of Health, Weekly Influenza Activity: Statistics — {{state flu report URL}}.) Each week, record: - Percent of lab tests positive for influenza - Cumulative season hospitalizations (new this week = this total minus last week's total) - Dominant strain - School and long-term-care outbreaks Flag it as a significant increase if ANY of these happen: 1. Lab positivity at least doubles week-over-week AND rises by at least 1 percentage point 2. Positivity reaches or exceeds 5% 3. New weekly hospitalizations jump more than 50% vs. the prior week Weekly update: send it every week during the season, even when nothing jumped. Keep it to 2–3 sentences: the numbers, leading with anything that jumped, plus the trend (rising, flat, or falling) and a plain statement of whether it's getting close to flu-shot time. Keep a running log of each week's numbers so trends are easy to compare.
- I want to start a short video series on a topic I care about. Ask me the topic, who it is for, where I want to post it, how long each video should be, and how many episodes I'm aiming for. Then suggest a series title and an episode lineup where each video stands on its own but builds on the last. For each episode, write a hook for the first few seconds, a simple outline, a full script in a natural speaking voice, and a short description with a call to action. Finish with a realistic posting schedule and a checklist of what I need to record each one. Offer to set reminders for each recording and posting day.
- Template· fill in the highlighted words
Family day out: find an open time and the best ticket price
Plan a family outing to on for . Check which time slots are still open, compare ticket prices for each option (weekday vs weekend, family bundles, member or online discounts), and add parking or extra fees so I see the true total. Show me the 2-3 best choices in a short table with the time, total cost, and anything to know (age limits, what to bring). Do not book or pay for anything until I say which one I want. - Template· fill in the highlighted words
Turn my saved X bookmarks into an organized, searchable library
I've saved hundreds of posts on X and never go back to them. Help me turn them into something I'll actually use. Read only, never post, like, unbookmark, or message anyone. 1. Read my X bookmarks (most recent is fine to start). 2. Group them into or so clear topics based on what they're actually about, not keywords. Put anything that doesn't fit in an "Other" pile. 3. For each topic, give me a short summary of the main ideas, then list the posts with one line each on why it's worth keeping and the link. 4. Pull out anything actionable (tools to try, how-to threads, recommendations) into a separate "Try this" list. 5. Flag near-duplicates and posts that are probably outdated so I can skip them. 6. Save the whole thing as a document I can search later, and tell me where it is. End with the 5 bookmarks you think I'd get the most out of revisiting this week.