Copy the setup prompt
It points your Muse at the pack and says exactly what to do with it.
Muse field guide · updated by itself every 6 hours
Everything your Muse
can do
A working library of what people actually run with Muse — 350+ real cases, 250+ with the exact prompt behind them. Hand the whole thing over in one paste, or take the single prompt you need.
0
Muse cases
0
With the exact prompt
0
Categories
0
Reusable loops
Hand it over
Your Muse knows none of this until you give it the pack. Paste one prompt and it loads every case, every prompt, the operating rules — then it can work from the whole list instead of waiting to be told.
Paste it into Muse
Any session works. It reads the pack, then comes back with what it can do for you.
Ask for anything
It matches your request to the closest case and runs it end to end, pausing only where your approval matters.
- What it knows after:
- every case, by category, with the prompt that ran it
- how to run one: match → ask once → execute → verify
- the six guardrails and the twelve loops
- what it must stop and ask you about
Start here: the Chief of Staff prompt
If you're trying out @muse, @bot or any other personal assistant, the best first move is to connect the accounts you want it to reach — calendar, and email too if you yolo like me. Then paste this. It sets up the entire working relationship: what it learns, what it remembers, and what it must ask you before doing.
What it does first
Checks which integrations are connected, reads the last 90 days of mail and calendar, then briefs you on what it found — separating facts, guesses and gaps.
How it learns
Keeps durable memory of your people, preferences and delegation rules, and runs a weekly self-review so it stops repeating the same miss.
Where it stops
No messages, events or commitments on your behalf during onboarding. Afterwards it acts inside the boundaries you two agree.
The library
Every case below is real — pulled from the field guide, a crowd feed and cases people sent in, then merged and de-duplicated on a schedule. Copy one prompt, or take the lot via the pack. Community bot prompts from botdirectory.ai live in the Bots tab.
Category
Works with
Taking one case instead
You don't have to hand over the whole pack. Every card carries the exact prompt that ran
the job — copy it, swap the [bracketed] details for yours, send it.
- Filter to the job you want done — or search for it.
- Hit Copy prompt on the card.
- Replace anything in
[square brackets]. - Paste it in. Muse asks for what's still missing, then runs it.
Master prompt wrapper
Optional, but it sharpens every case
The twelve loops
Most "new" use cases are combinations of these shapes. Compose them and you can invent cases that aren't in the library yet.
Guardrails worth writing in
Caveats that showed up again and again in hands-on reports. Put them in the prompt before you hand over anything important.
Send in your case
Ran something good? Send it in. Reviewed cases land in the library and in the capability pack on the next sync — with your handle on it if you want the credit.
- What counts: something you actually ran, not a hypothetical.
- The prompt: paste it verbatim if you have it. No prompt? Describe it and link the post.
- Review: every submission is read before it ships. Spam isn't.
- Credits: add a handle or link and it stays attached.
Prefer git? The library and the worker are open source — send a pull request instead.
Open source, end to end
The page, the sync worker and the capability pack are MIT licensed. Fork it, run your own instance, point it at your own sources — or send a case in as a pull request.
Repository
everyai-com/muse-use-cases
Worker, page, build scripts and docs. One command to deploy your own.
github.com → LicenseMIT
Use it, fork it, ship it commercially. Attribution appreciated, not required.
Read the license → Public APIRead the whole library
/api/use-cases for JSON, /muse/capabilities.md for the pack.
Send a case by PR
Add the case, run the build, open the pull request. Reviewed like any other.
How to contribute →git clone https://github.com/everyai-com/muse-use-cases cd muse-use-cases/worker && wrangler deploy node scripts/build-muse-site.mjs && wrangler pages deploy dist/muse
Where all of this comes from
Nothing here is invented. Every case traces back to a post, a guide or a person.
Field guide
Muse use cases
Collected from public posts on X, Threads, Instagram and Hacker News. Re-read live on every sync, so new cases land here without anyone touching the site.
muse.ai → Crowd feedmusecases.netlify.app
A continuously refreshed feed of Muse cases spotted on X. These arrive as descriptions — cards without a published prompt link straight to the post.
musecases → Botsbotdirectory.ai
An open, MIT-licensed directory of agent prompts for Grok Bot, Rakazo and anything else. Queried live in the Bots tab.
botdirectory → CommunitySent in by readers
Cases submitted through the form or a pull request, reviewed before they ship, credited to whoever sent them.
Add yours →
How it stays fresh
—
- Field guide
- —
- Crowd feed
- —
- Community
- —
- Exa discovery
- —
Prompts are community- and user-generated and unverified. They're starting points, not guarantees — read one before you run it, keep payments and account changes under your own approval, and be clear about what your agent may read, send or buy. Some newer cases arrive before they have a published prompt; those are marked and link to the original post.