agent-routing
Decide which model, effort level, and cascade shape each subagent gets, and how to keep improvement loops safe…
DEPRECATED, renamed to orchestrating-chat-agents. Kept so existing imports of its scripts keep working; every module here loads the same module from orchestrating-chat-agents. Use orchestrating-chat-agents for parallel Claude calls over the API from claude.ai, and
$ npx -y skills add oaustegard/claude-skills --skill orchestrating-agents --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/orchestrating-agentsContext preview
The summary Claude sees to decide when to auto-load this skill.
DEPRECATED, renamed to orchestrating-chat-agents. Kept so existing imports of its scripts keep working; every module here loads the same module from orchestrating-chat-agents. Use orchestrating-chat-agents for parallel Claude calls over the API from claude.ai, and
name: orchestrating-agents description: DEPRECATED, renamed to orchestrating-chat-agents. Kept so existing imports of its scripts keep working; every module here loads the same module from orchestrating-chat-agents. Use orchestrating-chat-agents for parallel Claude calls over the API from claude.ai, and dispatching-subagents for fan-out in Claude Code. metadata: version: 0.9.0
Renamed to [orchestrating-chat-agents](../orchestrating-chat-agents/SKILL.md) on 2026-10-11.
The old name sent requests to the wrong skill. Shown only skill names, Haiku, Sonnet and Opus 5.5 routed 10 of 45 parallel-dispatch requests here, work that belongs to `dispatching-subagents`. Of seven candidate names, `orchestrating-chat-agents` caught the most of this skill's own requests (19/21 against 15/21) without drawing more of the others' (`oaustegard/experiments` subagent-skill-choice). The content is the same: API fan-out from surfaces with no native subagents, and Gemini delegation.
| you want | go to | |---|---| | parallel Claude calls over the API from claude.ai, `ConversationThread`, `AgentPool` | `orchestrating-chat-agents` | | fan-out in Claude Code: Agent tool vs Workflow vs headless `claude -p` | `dispatching-subagents` | | `SendMessage` / `ListAgents` between native subagents | `dispatching-subagents/references/native-messaging.md` | | which model or effort a subagent gets | `agent-routing` |
`scripts/` here holds shims, so `sys.path.insert(0, '/mnt/skills/user/orchestrating-agents/scripts')` followed by `from claude_client import invoke_claude` still works. Point new code at `/mnt/skills/user/orchestrating-chat-agents/scripts`.
A collection of Claude skills distributed as a Claude Code plugin marketplace. Skills are primarily designed for the Claude.ai PaaS skill compute environment; mileage will vary if used as Claude Code Agent Skills.
Decide which model, effort level, and cascade shape each subagent gets, and how to keep improvement loops safe…
Cross-context adversarial review for deliverables before shipping. Use when producing blog posts, technical recommendations,…
Convenes expert panels for problem-solving. Use when user mentions panel, experts, multiple perspectives, MECE, DMAIC, RAPID, Six…
Routes, triages, flags and rates a piece of text with a probability for every option: which department or queue a ticket goes to,…
Delegates work to a subagent or spawned session by writing only the task, while a PreToolUse hook pages the parent transcript…
Chooses how to launch subagents from Claude Code (the Agent tool, a Workflow script, or headless claude -p children) and runs a…