# Claude Orchestra

> An operating system for your Claude Code skills, agents & MCPs — organize everything into auto-routing orchestras.

- **Type:** MCP server
- **Install:** `agentstack add mcp-momo2323-ui-claude-orchestra`
- **Verified:** Pending review
- **Seller:** [Momo2323-ui](https://agentstack.voostack.com/s/momo2323-ui)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Momo2323-ui](https://github.com/Momo2323-ui)
- **Source:** https://github.com/Momo2323-ui/claude-orchestra

## Install

```sh
agentstack add mcp-momo2323-ui-claude-orchestra
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# 🎼 Claude Orchestra

**A routing & governance layer for your Claude Code skills, agents & MCPs.**

---

I went from zero coding to 500+ Claude Code skills, agents, and MCP servers installed in a
few months. At some point I had no idea what was active, what would fire for a given task,
or whether I'd installed the same thing three times. More tools had made me *slower*.
**Claude Orchestra is what I built to fix that.**

> **Built to be forked.** This isn't a one-click install you forget about — it's a template
> you fork, customize with *your* rosters, and run on your own machine.

## The problem

```
WITHOUT Claude Orchestra:

  ~/.claude/ → 247 skills · 40 agents · 12 MCPs · 8 plugins
  → "Which one handles this task?"            🤷
  → "Did I install something for this already?" 🤷
  → "Why did THAT skill just fire?"            🤷

WITH Claude Orchestra:

  → architect: BUILD stack — code-reviewer, debugger, gh
  [the work continues here]
```

Every request routes through your constitution — silently. The only ceremony left is a
**one-line announcement when work is delegated** to a specialist (v2's always-on 🎼 ensemble
blocks are gone in v3; the work leads the reply, not the routing).

## The fix: 22 orchestras

Claude Orchestra files every tool into themed **orchestras**. Each has **one conductor** that
sequences its players, clear **triggers**, and quality **gates**. A routing hook reads every
request and activates the right orchestra(s) automatically.

Compound requests stack:

```
→ design-ux-architect: landing-page mockups, then handoff to architect for build
  (DESIGN → BUILD stack, sequenced by the constitution)
```

Idea / business-planning prompts fire **NEXUS**, the meta-conductor that sequences whole
orchestras across a 7-phase lifecycle:

```
→ NEXUS: Phase 0 Discovery — sequencing RESEARCH · PRODUCT · KNOWLEDGE
```

---

## The 22 orchestras

| # | Orchestra | What it does |
|---|---|---|
| 🌐 | **NEXUS** *(meta-conductor)* | Turns "I have an idea" into a sequenced multi-orchestra plan |
| ① | **BUILD** | Ship working, reviewed code |
| ② | **DESIGN** | Beautiful, on-brand interfaces |
| ③ | **RESEARCH** | Know more than the competition |
| ④ | **MARKETING** | Reach the right people |
| ⑤ | **CONTENT** | Words and creative that convert |
| ⑥ | **SEO + GEO** | Win search and AI answers |
| ⑦ | **LEAD GEN & SALES** | Find clients, close deals |
| ⑧ | **PRODUCT** | Build the right thing |
| ⑨ | **VIDEO + MEDIA** | Generate and edit video/image |
| ⑩ | **ANALYTICS** | Measure everything |
| ⑪ | **KNOWLEDGE & MEMORY** | Remember and connect everything |
| ⑫ | **DOCUMENTS & REPORTS** | Polished deliverables |
| ⑬ | **PAID ADS** | Ads that profit |
| ⑭ | **AUTOMATION & OPS** | Automate what repeats |
| ⑮ | **AI/ML DEVELOPMENT** | Build AI systems |
| ⑯ | **iOS / SWIFT** | Ship iOS apps |
| ⑰ | **PLANNING & PM** | Plan before building |
| ⑱ | **GROWTH & CONVERSION** | Users → revenue |
| ⑲ | **PERSONAL FINANCE** | Investment research and financial modelling |
| ⑳ | **EXECUTIVE ADVISORY** | Founder-grade strategic counsel |
| ㉑ | **AUDIT** | Verify everything. Defaults to NEEDS WORK. |
| ㉒ | **CYBERSECURITY** | Defend, detect, respond, and prove it |

The example config (`examples/my-22-orchestras.md`) shows a real filled-in setup — rosters, conductors,
and the reasoning behind each placement. Every skill links to its original author. Use it as a
starting point and prune to your own stack.

---

## What's inside v3

Seven doctrine upgrades shipped in v3 (all in `orchestra-system.md`):

- **22 orchestras** — ㉑ AUDIT (quality gate, defaults NEEDS WORK) and ㉒ CYBERSECURITY (a slot for your security tools) added
- **Silent routing** — v2's always-on 🎼 ensemble announcements are gone. Routing happens quietly; the only ceremony is a one-line delegation announcement (`→ agent: task`) when work is actually handed off.
- **Gap → Recommend** — when nothing installed fits a task, the doctrine searches the skill registries and presents vetted install candidates (installs, source reputation) instead of improvising with a generic approach. Recurring gaps are install signals.
- **Internal-first search ladder** — before going to the web, the doctrine has the model check internal sources (your notes/knowledge base → `~/.claude` docs → session memory) first, and only then search externally. Saves tokens, finds prior work first.
- **Harmony — 3-Layer Ensemble** — each orchestra activates the best *combination* of tools (an Active Ensemble loaded in full + a Standby Bench summoned by name + a named-only Reserve Bench), not just the single top match.
- **Calibration loop** — surprising failures get logged to an append-only learnings file and anchored into the doctrine, so the same mistake can't recur.
- **NEXUS phase map** — idea/business-planning prompts sequence orchestras across a full 7-phase lifecycle (Discovery → Strategy → Foundation → Build → Hardening → Launch → Operate), not just activate one team.

> **These are doctrine, not enforced code.** The hook injects the routing directive and the model
> honors it — strong conventions, not a runtime engine. Tune them to your taste.

**Optional power-up (not installed by default):** if you run a local semantic index over your skill
catalog (e.g. [qmd](https://github.com/tobi/qmd) or any embeddings store), the `skill-selector` skill can
score every installed skill against each prompt instead of relying on lexical matching. This needs
extra tooling (Python + an index) — the core system stays zero-dependency without it.

### How NEXUS sequences orchestras

| Phase | Orchestras |
|---|---|
| 0 — Discovery | RESEARCH · PRODUCT · KNOWLEDGE |
| 1 — Strategy | PRODUCT · PLANNING · MARKETING |
| 2 — Foundation | PLANNING · DESIGN |
| 3 — Build | BUILD · DESIGN · AI/ML · iOS |
| 4 — Hardening | BUILD (QA) · AUTOMATION · CYBERSECURITY · **AUDIT** *(verdict required before Phase 5)* |
| 5 — Launch | MARKETING · CONTENT · SEO · PAID ADS · GROWTH |
| 6 — Operate | ANALYTICS · GROWTH · AUTOMATION · DOCUMENTS |

### Cross-cutting: Superpowers

Some skills apply across ALL orchestras regardless of which fired. These run on discipline, not routing:

| Skill | When it fires |
|---|---|
| `brainstorming` | Before any creative or feature work |
| `writing-plans` | Multi-step spec before touching code |
| `verification-before-completion` | Before any "done" claim — Iron Law |
| `systematic-debugging` | Any non-trivially reproducible bug |
| `test-driven-development` | Any new feature |

---

## Requirements

| Need | Why | Install |
|---|---|---|
| **Claude Code** | The host this routes inside | https://claude.com/claude-code |
| **Bash 4+** | Install script is Bash | macOS / Linux preinstalled |
| **`jq`** | Safely merges `settings.json` (no clobbering) | `brew install jq` · `apt-get install jq` |

That's it. No Python, no npm, no Docker.

---

## Install — the audit-first path (recommended)

```bash
# 1. Clone
git clone https://github.com/Momo2323-ui/claude-orchestra
cd claude-orchestra

# 2. Audit — read every line you're about to run
cat install.sh

# 3. Preview — see every action without touching anything
./install.sh --dry-run

# 4. Install — idempotent, backs up every file before it changes it
./install.sh        # or: ./install.sh --minimal   (just the load-bearing trio)

# 5. Verify what changed
diff "$(ls -t ~/.claude/settings.json.bak.* | head -1)" ~/.claude/settings.json
ls -la ~/.claude/skills/orchestra-router ~/.claude/agents/auditor.md

# 6. Customize — edit your roster
$EDITOR ~/.claude/rules/orchestra-system.md
```

Open a new Claude Code session — the router fires on your next prompt.

## Install — the fast path

If you already trust the repo:

```bash
curl -fsSL https://raw.githubusercontent.com/Momo2323-ui/claude-orchestra/main/install.sh | bash
```

Or let Claude Code drive it:

```
Install this for me: https://github.com/Momo2323-ui/claude-orchestra
```

**Want to reverse the install?** See [UNINSTALL.md](UNINSTALL.md).

---

## What the installer actually does

| Target | Action |
|---|---|
| `~/.claude/skills/orchestra-router/` | Created (or refreshed if it exists) |
| `~/.claude/skills/orchestra-intake/` | Created (or refreshed if it exists) |
| `~/.claude/skills/skill-selector/` | Created (or refreshed) — skipped with `--minimal` |
| `~/.claude/skills/hallucination-guard/` | Created (or refreshed) |
| `~/.claude/agents/auditor.md` | Copied (backed up first if it exists) — the ㉑ AUDIT conductor |
| `~/.claude/hooks/orchestra-route.sh` | Copied + `chmod +x` (backed up first) |
| `~/.claude/rules/orchestra-system.md` | Copied **only if not already present** — yours wins |
| `~/.claude/.orchestra-scan.md` | An inventory of your existing tools, so you can file them into orchestras on first run |
| `~/.claude/settings.json` | One entry appended to `hooks.UserPromptSubmit` (auto-backup first) |
| `~/.claude/CLAUDE.md` | Orchestra rule appended **only if marker text not present** |

These are Claude Orchestra's *own* routing/governance skills + the auditor agent — **no third-party
tools are bundled.** Everything backs up before it mutates. Run `./install.sh --dry-run` to see
every action without touching the filesystem, or `--minimal` for just the load-bearing trio.

No network calls (except the optional curl-pipe clone), no `sudo`, no telemetry. Full breakdown in
[**SECURITY.md**](SECURITY.md).

---

## How it works

1. **The constitution** (`orchestra-system.md`) defines your orchestras — rosters, conductors, triggers, gates.
2. **The routing hook** injects a routing directive on every prompt.
3. **The router skill** matches your request to the right orchestra(s) and announces them.
4. **The intake skill** files anything new you install into the right orchestra — never archived.

→ Full walkthrough in [`docs/HOW-IT-WORKS.md`](docs/HOW-IT-WORKS.md).

## Build your own orchestras

[`docs/CREATE-YOUR-ORCHESTRA.md`](docs/CREATE-YOUR-ORCHESTRA.md) walks you through mapping
*your* tools into orchestras in about ten minutes.

## See a real setup

[`examples/my-22-orchestras.md`](examples/my-22-orchestras.md) is a real 22-orchestra config —
rosters, the reasoning behind each placement, and links to every skill so you can install the
ones you like.

---

## FAQ

**Does this install any skills/agents for me?** Only its *own* — the routing/governance skills
(`orchestra-router`, `orchestra-intake`, `skill-selector`, `hallucination-guard`) and the `auditor`
agent. It does **not** bundle anyone else's tools. The example config links to third-party skills at
their original repos so you install those yourself (and the authors get the credit).

**Will it overwrite my settings?** No. The installer backs up `settings.json`, merges with `jq`
without clobbering existing hooks, and only appends to `CLAUDE.md` if the rule isn't already there.

**Is this on PyPI / npm / homebrew?** No. It's a Bash + Markdown repo. Clone it, audit it, run
the installer. Keeping it small is the point.

**Do I have to use all 22 orchestras?** No. Delete, merge, or rename freely. The themes are a
starting taxonomy, not a rulebook.

**Does the curl installer give me the orchestras?** The curl path installs the *infrastructure*
(hook + router + intake skills). The 22-orchestra roster is a template you customize — edit
`~/.claude/rules/orchestra-system.md` to map your own tools in.

**Do I need NEXUS?** No — it's optional. Delete the section if you don't want a meta-conductor.

**Can I uninstall?** Yes — see [UNINSTALL.md](UNINSTALL.md).

---

## Security

Every install modifies your `~/.claude/`. We take that seriously — see [**SECURITY.md**](SECURITY.md)
for the full breakdown of what gets touched, how to audit before running, how to verify after, and
how to report a vulnerability privately.

## Contributing

PRs and new-orchestra ideas welcome — see [CONTRIBUTING.md](CONTRIBUTING.md).

A note for AI-assisted contributors: please verify every command, package name, and feature in
your PR actually exists in this repo before submitting. We've had AI-drafted PRs invent commands
and features that don't exist — those will be closed.

## Credits

Built by [Moksh Mittra](https://github.com/Momo2323-ui). MIT licensed — use it freely. Every skill
referenced in the example links to its original author.

## Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Momo2323-ui](https://github.com/Momo2323-ui)
- **Source:** [Momo2323-ui/claude-orchestra](https://github.com/Momo2323-ui/claude-orchestra)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** yes
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: flagged — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/mcp-momo2323-ui-claude-orchestra
- Seller: https://agentstack.voostack.com/s/momo2323-ui
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.