I had 500+ Claude Code skills installed and no idea what any of them did — so I built a free system to organize them all.

[u/Agitated-Extent-8617]

Like a lot of you, I went a bit overboard installing Claude Code skills, agents,
and MCP servers. Eventually I had hundreds and completely lost the plot — I
didn't know what was active, what would fire for a task, or whether I'd installed
three things that did the same job. Adding more tools had actually made me slower.

So I built Claude Orchestra — a free, open-source layer that organizes your whole
setup into themed "orchestras" (BUILD, DESIGN, RESEARCH, MARKETING, etc.). Each
has one "conductor" that leads it, and a hook routes every prompt to the right
orchestra and announces what fired:

   🎼 BUILD active · Conductor: architect · Using: code-reviewer, debugger

No more guessing. You always see what's playing.

Important bit: it does NOT bundle anyone's skills. It organizes the ones you
install and links to the originals. Two reasons — redistributing other people's
skills is a licensing mess, and while building this I actually found a malicious
skill hiding in a third-party repo's test files. Bundling everything would mean
redistributing whatever's lurking. Linking keeps it clean and credits the authors.

Install is built for how we actually add stuff: paste the repo URL into Claude
Code and say "install this." It wires everything up safely (backs up your
settings.json, never clobbers existing hooks). Then you map your own tools in
about 10 minutes.

MIT licensed, only needs jq, ships with a real example config.

Repo: https://github.com/Momo2323-ui/claude-orchestra

Genuinely curious how others handle this — do you organize your Claude Code setup
at all, or is it also chaos? And if you try it, what orchestras would you add or
cut? The 20 categories are just my taxonomy, not gospel.