What makes a good Muse prompt?

The same things that make a good work assignment: a goal, the context Muse can't guess, hard requirements like budgets and dates, a statement of which actions it may take, an approval rule, and the output format you want. Muse, Meta's personal AI agent, acts on your behalf — so the prompt needs to define the boundaries of that acting.

Should I always include an approval rule in a Muse prompt?

Yes, for anything involving spending, sending email, or submitting forms. Meta says Muse already checks before sensitive actions like sending an email or making a purchase, but stating 'ask me before...' removes any ambiguity about what counts as sensitive.

Can I paste these prompts into Muse on WhatsApp?

Yes. CNBC reports the WhatsApp version has the same core conversation functionality, minus the feed and ideas tool. Long structured prompts are easier to manage in the app or on muse.ai, but they work in WhatsApp too.

Do these prompts work if a task fails?

Not always on the first try. Reuters reported reliability failures in Meta's own testing, and Muse keeps an audit trail of everything it did and plans to do — use it to find the step that broke, then rerun with a narrower instruction.

Best Muse AI Prompts for Everyday Tasks

Muse, Meta's personal AI agent, does real work — sending emails, booking travel, filling forms, negotiating bills — so a vague prompt produces vague acting. The fix is structure. Every prompt below follows one template you can reuse for anything.

The anatomy of a good Muse prompt

Six parts, in this order:

Goal — the finish line, in one sentence.
Context — what Muse can't guess: people, budgets, constraints, history.
Requirements — the hard rules (price caps, dates, tone).
Actions — what Muse is allowed to do to get there.
Approval — what requires your OK first. Default to "ask before any purchase, send, or form submission."
Output — how Muse should report back: table, shortlist, one-page brief.

Copy any block below, swap the [bracketed placeholders], and paste it into the Muse app, muse.ai, or WhatsApp. If you'd rather build one from scratch, our prompt generator assembles this structure for you (it doesn't connect to Muse itself).

Trip planning prompts

1. Weekend trip planner

Goal: Plan a complete weekend trip to [city] for [number] adults on [dates].
Context: Departing from [your city]. Budget: [total] all-in. We enjoy [food/walks/museums] and dislike [early mornings].
Requirements: Flights under [$] each; hotel under [$]/night in [neighborhood]; nothing scheduled before 9 a.m.
Actions: Research flights and hotels, check reviews, draft a day-by-day itinerary with costs.
Approval: Ask me before booking flights, hotels, or any reservation.
Output: A one-page itinerary with a cost table and your top flight/hotel pick.

2. Flight price watcher

Goal: Monitor round-trip fares from [origin] to [destination] for [date range].
Context: My target price is [$]. I can fly any day within the range. [number] travelers.
Requirements: Nonstop or one-stop only; no basic-economy fares with no carry-on.
Actions: Check fares on an ongoing basis and compare across options.
Approval: Alert me when a fare is under [$] — do not book without my explicit OK.
Output: A short message with airline, dates, price, and a booking link each time the target is hit.

3. Hotel comparison

Goal: Choose the best hotel in [neighborhood, city] for [dates].
Context: [number] guests. Trip purpose: [business/leisure]. Past hotels I liked: [names].
Requirements: Under [$]/night, free cancellation, rating [4+] from at least [100] reviews.
Actions: Research [3–5] candidates, verify current prices and cancellation terms in the browser.
Approval: None needed for research — ask me before booking the winner.
Output: A comparison table (price, cancellation, walk time to [landmark], review score) plus one recommendation.

Email prompts

4. Inbox catch-up

Goal: Get me caught up on everything in my inbox since [day].
Context: My priorities this week: [projects/people]. My [client name] emails always come first.
Requirements: One-line summaries; flag anything with a deadline in the next [3] days.
Actions: Read, sort into "needs my reply," "FYI," and "junk." Do not reply to anything.
Approval: Read-only — if you think any reply is urgent, show me the draft instead of sending.
Output: A grouped list, with the reply-needed items on top.

5. Refund request

Goal: Get a refund for order [number] from [retailer].
Context: The order was placed on [date] and never arrived. Tracking shows [status]. I was charged [$].
Requirements: Firm and polite tone; reference the order number and the retailer's stated delivery window.
Actions: Find the right support channel, draft the request, include order details.
Approval: Show me the draft and wait for my OK before sending — make Muse ask first.
Output: The draft, plus the date sent once approved and any reply that comes back.

6. Follow-up nudge

Goal: Get a response from [name] about [subject].
Context: I sent [it] on [date]; no reply after [number] days. Our relationship: [context]. Their last message: [gist].
Requirements: Under [80] words, friendly, give them an easy out, one clear question.
Actions: Draft the follow-up only — do not send.
Approval: Show me the draft before anything is sent.
Output: The draft, ready to approve.

Shopping prompts

7. Product research and recommendation

Goal: Recommend the best [product category] under [$].
Context: I'll use it for [use case]. My constraints: [size/compatibility/space]. Models I've seen: [names].
Requirements: [4+] star average from [100+] owners; warranty at least [1] year; avoid brands with [known issue].
Actions: Read owner reviews, spec pages, and expert write-ups; check current prices at [number] retailers.
Approval: None — research only. Do not purchase.
Output: A shortlist of three with pros/cons, then one recommendation with the reason in two sentences.

8. Buy on price drop

Goal: Buy [specific product/model] at the right price.
Context: Current price [$]. My target: [$] or less. It's for [use/date needed].
Requirements: New only, from the official retailer or an authorized seller.
Actions: Track the price; when it hits my target, prepare the order.
Approval: Ask me before the purchase goes through — make Muse ask first on every purchase.
Output: A confirmation with the final price, order number, and return window.

Planning and admin prompts

9. Weekly plan

Goal: Build my priority plan for [week of date].
Context: My roles: [job, family, side project]. This week's fixed events: [list].
Requirements: Max [3] top priorities; protect [mornings] for deep work; nothing scheduled Friday afternoon.
Actions: Read my calendar and recent email, draft priorities, and propose which meetings to shorten or skip.
Approval: Send nothing and decline nothing — draft only.
Output: A day-by-day plan with the top three priorities at the top and a "to decline" list.

10. Find a meeting time

Goal: Schedule a [45]-minute meeting with [names] about [topic] next week.
Context: I'm unavailable [before 10 a.m. / Wednesdays]. [Name] is in [time zone].
Requirements: Weekday afternoons preferred; avoid back-to-back with my [existing meeting].
Actions: Check shared availability, propose the best slot, and prepare the invite.
Approval: Show me the proposed time and the invite text before sending anything.
Output: The chosen slot plus the ready-to-send invite.

11. Form filling

Goal: Complete [form name] for [purpose].
Context: Use my details on file: [name, address, ID numbers as needed].
Requirements: Answer every required field; leave optional fields blank; note anything you couldn't fill.
Actions: Open the form, fill it in, and do NOT submit.
Approval: Show me the completed form and wait for my explicit go-ahead — make Muse ask first before submitting anything.
Output: A summary of what was entered and what's missing.

12. Decision brief

Goal: Help me decide between [option A] and [option B].
Context: I care most about [criteria, ranked]. My budget: [$]. Deadline to decide: [date].
Requirements: Use current, checkable sources; separate facts from speculation; note where sources disagree.
Actions: Research both options, verify prices and terms, and weigh them against my criteria.
Approval: None — this is research only.
Output: A one-page brief: comparison table, recommendation, and the strongest argument against it.

Prompting habits that pay off

Numbers beat adjectives. "Under $180 a night" beats "affordable." "Before October 1" beats "soon."
Separate may-do from must-ask. Research freely; purchases, sends, and form submissions always need your OK — that matches Muse's own approval model.
Name the output. "Table," "shortlist of three," "one-page brief" — Muse can't read your mind about format.
One goal per prompt. Two jobs means two prompts, or an agent splitting its attention.
Use the audit trail when things drift. Find the wrong step, then rerun with that step corrected — that's the fastest loop, and it's how you recover from the failures Reuters documented at launch.

For more ready-made jobs, browse the full task library — every guide there includes its own prompt template.