ForClaude CodeandCodex

100 skills.
.
Time to muster them.

Select the highlighted words to see what else goes wrong.

Muster finds every skill you've installed and sorts them into folders, from your terminal, your browser or your menu bar. It flags the ones that clash, repeat or never run, and suggests fixes and improvements.

Join the waitlist Try the demo
  • Checked every day
  • Runs on your Mac
  • No account
  • Nothing changes without you

Every skill is an expert you brought on. You have 98 now, and none of them have met. Eight came with a plugin you tried once. Your Codex copies drifted. Two give opposite rules for commit messages. Your agent has to pick a side. It never tells you which one won.

How it works

Muster gets them in line.

One line to install. It finds every skill in Claude Code and Codex, sorts them into folders, checks them every day, and lets you fix a clash in one click.

  1. 1

    You install it with one line

    Paste one command. Muster is now a command in your terminal, an app in your browser and an icon in your menu bar. No account, nothing to configure. It starts on the skills you already have.

  2. 2

    It finds every skill you have

    Claude Code, Codex, your projects, your plugins: one scan finds every skill, wherever it lives. It only reads. Nothing moves.

  3. 3

    It sorts them into folders

    No more one long list. Your skills get folders and subfolders, and every new skill gets a suggested home. The files stay where they are, so your agent still finds them.

  4. 4

    It checks them every day

    It flags what needs a look: skills that contradict each other, skills that do the same job, skills you never use, and descriptions too vague for your agent to pick. It also checks as soon as you add or change a skill, and whenever you ask.

  5. 5

    You fix them in one click

    Every flag comes with a ready fix: merge the duplicates, settle the conflicts, switch off what you never use. Nothing changes until you say so.

Installing skills is easy now. Keeping track of what you installed is the hard part.

We built Muster for our own Macs first. This is what the first cleanup did to one of them. Now we’re letting a few people in at a time.

The Muster team

229 to 75

skills on one of our Macs, before and after the first cleanup

114
switched off. All from one plugin, installed for one job.
23
duplicates merged. 8 were animation skills under different names.
17
archived after 30 days unused. Nothing deleted.
9
conflicts fixed in the 75 that stayed
Try it

Browser, menu bar or terminal.

The full app in your browser, today’s summary in your menu bar, every command in your terminal. Same skills and counts, so a fix in one shows in all three.

Safari
127.0.0.1:55350/

Privacy

Your skills stay on your Mac.

No Muster account, no Muster cloud. This is everything that moves.

Your Mac

Your skills~/.claude, ~/.agents, projects, plugins
reads
MusterKeeps its notes in its own folder
asks for the daily check
Your Claude Code or CodexRuns on your own plan
Muster serversDon’t exist
Anthropic or OpenAISame as any session you run
  • ReadsYour skills, and your Claude Code and Codex history to count which skill ran when. Counted on your Mac.
  • WritesOnly its own folder, until you apply a fix you approved.
  • SendsNothing to us. The daily check goes through your own Claude Code or Codex.
  • UninstallRemoves the app, its folder and its daily schedule. Nothing is left behind.
Roadmap

First your skills.
Then your team’s.

The first version is for one person on one Mac. What the waitlist asks for decides the order after that.

  1. Building now

    Your skills, on your Mac

    • Find, check and fix, every day
    • Folders, subfolders and usage, in your menu bar
    • Claude Code and Codex on macOS

  2. Next

    Your team

    • A shared team space next to your private one
    • Suggest a skill, an admin approves, it lands on every teammate’s Mac
    • Connectors like Linear, GitHub and Notion, set up once for everyone

  3. Later

    More agents

    • Cursor, Gemini CLI and other agents
    • Windows and Linux
    • And a few bigger ideas we’re not ready to show yet
Questions

Short answers.
No sales call.

What people ask before they point something at their ~/.claude or ~/.agents folder.

What does Muster work with?

Claude Code and Codex on macOS. It reads your global skills in ~/.claude/skills and ~/.agents/skills (plus Codex’s older ~/.codex/skills), the skill folders inside your projects, and skills that came with plugins, including ones you installed from skills.sh or GitHub. Other agents come later, then Windows and Linux.

I use both Claude Code and Codex. Does that help?

That’s where the mess grows fastest: you copy a skill over for Codex, then edit only one copy. Muster reads both, spots skills that exist in both places, shows where the copies drifted apart, and brings them back in line.

Will it change or delete my skills?

Not without asking. The scan only reads. Every fix is a suggestion: apply it, copy it and do it yourself, or skip it. Unused skills you wrote get archived, not deleted.

Does anything leave my Mac?

Nothing goes to us. There’s no Muster account and no Muster cloud. The daily check asks your own Claude Code or Codex to read your skills, so their contents go only where that agent already sends them.

Do folders change anything for my agent?

No. Folders and subfolders live in Muster, so you can sort a hundred skills however you like while every file stays exactly where Claude Code or Codex looks for it. Moving a skill between folders never touches the skill itself.

Does it use my Claude or ChatGPT plan?

Yes, if you sign in to Claude Code or Codex with your Claude or ChatGPT account: the check runs through the one you pick and counts toward that plan like any other session. With an API key, it’s billed to that key. By default it runs once a day and when you add or remove a skill; you can switch it to only when you ask.

How does it spot conflicts and duplicates?

It reads every skill’s description, which is what your agent matches your request against, and then the full instructions. Two skills only count as a conflict if both would load for the same request and it can quote the lines that contradict; similar but compatible skills are duplicates. The fix depends on who owns the skill: yours get edited or merged, installed ones get a tiebreak line in ~/.claude/CLAUDE.md or ~/.codex/AGENTS.md, and unused ones get archived or switched off.

How do I get it, and how do I remove it?

The install comes with your invite. Uninstalling removes the app, its folder and its daily schedule; Muster stores nothing anywhere else. Your skills stay as they are, apart from fixes you applied.

What about my team?

That’s next. You’ll be able to suggest a skill from your Mac to a team space; an admin approves it, and Muster puts it on every teammate’s Mac. Connectors like Linear, GitHub and Notion come with it. If that’s what you need most, pick it when you join.

Early access

Muster your skills.

We’re letting people in a few at a time, starting with the most tangled setups. Tell us what you’d fix first, and we’ll know where to start.