Conductor Orchestrator
Multi-agent Evaluate-Loop coordinator: plans, dispatches parallel workers, gates on evaluators
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 21, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 32bda9c
Located skills/conductor-orchestrator/SKILL.md via the GitHub tree and fetched it raw (HTTP 200, 52KB). Frontmatter parses with name+description; spot-checked 5 body-referenced files (leads/architecture-lead, parallel-dispatch, knowledge-manager, loop-planner SKILL.md, commands/board-meeting.md) — all returned 200. No security smells: no curl|sh, base64, or exfiltration; only a benign `claude --print` board subprocess spawn. Could NOT measure output vs baseline: the body is a state-machine that reads a scaffolded conductor/ directory (config.json, tracks/{id}/metadata.json, plan.md) and dispatches many sibling agents in parallel background Tasks over a file-based message bus — none of which exists in a bare context, so any "artifact" would just restate its own rules. Verdict setup: the un-runnable manual step is /…:setup scaffolding plus installing the full plugin so ${CLAUDE_PLUGIN_ROOT} and sibling skills resolve.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 5/10
- Docs & honesty 4/5
What Conductor Orchestrator does
A master orchestrator skill for the SupaConductor plugin that runs an autonomous plan-evaluate-execute-fix loop over "tracks": it reads conductor/ state files, dispatches specialized sibling agents (planner, board-of-directors, parallel workers, evaluators) via the Task tool, and coordinates them through a file-based message bus. Triggers on /go <goal>, /conductor implement, "start track", "run the loop", "orchestrate", or "automate track". Requires the full plugin scaffold (conductor/ directory plus the bundled sibling skills) to function, so it is not runnable as a standalone one-file skill.
How to install Conductor Orchestrator
git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git /tmp/conductor-orchestrator-src
mkdir -p ~/.claude/skills
cp -R /tmp/conductor-orchestrator-src/skills/conductor-orchestrator ~/.claude/skills/conductor-orchestrator
# NOTE: this places SKILL.md at ~/.claude/skills/conductor-orchestrator/SKILL.md, but the skill
# is a plugin orchestrator: its body references ${CLAUDE_PLUGIN_ROOT}/skills/leads/*,
# skills/loop-planner, skills/board-of-directors, skills/parallel-dispatch, worker-templates, etc.
# Those siblings are NOT copied above and the ${CLAUDE_PLUGIN_ROOT} var is only set for plugins.
# For real use install the whole plugin instead:
# /plugin marketplace add Ibrahim-3d/orchestrator-supaconductor
# /plugin install orchestrator-supaconductor
# Then scaffold a project with /orchestrator-supaconductor:setup and run /orchestrator-supaconductor:go <goal>
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Conductor Orchestrator
-
/conductor-orchestratorMulti-agent Evaluate-Loop coordinator: plans, dispatches parallel workers, gates on evaluators
It also activates on plain-language prompts like these:
-
Start a track and orchestrate the workers -
Run the conductor loop on this goal -
Automate this track with parallel agents
Frequently asked questions
- Is the Conductor Orchestrator skill free?
- Yes. The skill itself is free from Ibrahim-3d/orchestrator-supaconductor. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Conductor Orchestrator work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 21, 2026. Verdict: Works with setup. Located skills/conductor-orchestrator/SKILL.md via the GitHub tree and fetched it raw (HTTP 200, 52KB). Frontmatter parses with name+description; spot-checked 5 body-referenced files (leads/architecture-lead, parallel-dispatch, knowledge-manager, loop-planner SKILL.md, commands/board-meeting.md) — all returned 200. No security smells: no curl|sh, base64, or exfiltration; only a benign `claude --print` board subprocess spawn. Could NOT measure output vs baseline: the body is a state-machine that reads a scaffolded conductor/ directory (config.json, tracks/{id}/metadata.json, plan.md) and dispatches many sibling agents in parallel background Tasks over a file-based message bus — none of which exists in a bare context, so any "artifact" would just restate its own rules. Verdict setup: the un-runnable manual step is /…:setup scaffolding plus installing the full plugin so ${CLAUDE_PLUGIN_ROOT} and sibling skills resolve.
- What is the Conductor Orchestrator SkillProof Score?
- 7.6/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 5/10, docs & honesty 4/5.
- How do I install Conductor Orchestrator?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Conductor Orchestrator with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.