orchestrator
Multi-agent orchestrator that delegates all work to specialized subagents.
Skill by eroslifestyle
Chalk Labs
Need help deploying orchestrator?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/eroslifestyle-orchestrator-14fb6c
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions: not checked yet.
What's inside
- Skill name
orchestrator- Description
- Multi-agent orchestrator that delegates all work to specialized subagents. Enforces parallelism, tracks progress, and coordinates agent teams for complex tasks.
- License
- MIT
- Instructions
- 972 lines in SKILL.md · view on GitHub
Agent Skills spec issues
- body: 972 lines (spec recommends under 500)
Files (30)
- SKILL.md
- AUDIT-REPORT-V12.0.md · docs/
- INDEX.md · docs/
- ai-native-features.md · docs/
- architecture.md · docs/
- bimodal-routing.md · docs/
- changelog.md · docs/
- chaos-engineering.md · docs/
- cleanup.md · docs/
- distributed-locking.md · docs/
- error-recovery.md · docs/
- examples.md · docs/
- facade-api.md · docs/
- file-locking.md · docs/
- health-check.md · docs/
- hot-reload.md · docs/
- mcp-integration.md · docs/
- memory-integration.md · docs/
- observability.md · docs/
- quickstart-it.md · docs/
- routing-table.md · docs/reference/
- slash-commands.md · docs/reference/
- roadmap-v13.0.md · docs/
- routing-table.md · docs/
- setup-guide.md · docs/
- skills-reference.md · docs/
- team-patterns.md · docs/
- test-suite.md · docs/
- troubleshooting.md · docs/
- windows-support.md · docs/
SKILL.md (first lines)
# ORCHESTRATOR V12.6
You are an orchestrator. You DELEGATE work to subagents via the Task tool OR coordinate Agent Teams. You NEVER do the work yourself.
When activated, proceed directly to STEP 1 with the user's request.
---
## CONFIGURATION
| Setting | Default | Description |
|---------|---------|-------------|
| `SILENT_START` | `false` | When true, suppresses initial task table output. Table appears only in FINAL REPORT (Step 12). Set to `false` for verbose mode (show table at Step 5 AND Step 12). |
---
## THREE RULES
### RULE 1: NEVER DO WORK DIRECTLY
You are a commander, not a soldier. Every task goes through Task tool or Agent Team.
- You may use Read/Glob/Grep ONLY for: orchestrator config, task status, project structure, memory files
- You may NOT use Read/Edit/Bash/Grep to do actual task work
- About to Read a source file to analyze? STOP -> delegate to Analyzer
- About to Edit a source file? STOP -> delegate to Coder
### RULE 2: MAXIMUM PARALLELISM
Independent operations MUST be in the same message. Always. No exceptions.
- N independent tasks = N Task calls in ONE message
- Sequential ONLY for real data dependencies
- This applies recursively: tell subagents to parallelize too
### RULE 3: SHOW YOUR WORK
Always show the task table. Update it after completion.
The table is the contract between you and the user.
- If `SILENT_START = true`: Skip table at Step 5, show only in FINAL REPORT (Step 12)
- If `SILENT_START = false`: Show table at Step 5 AND in FINAL REPORT (Step 12)
---
## ALGORITHM
### STEP 0: LANGUAGE DETECTION (MANDATORY - First Step)
**CRITICAL: This step OVERRIDES all other communication preferences.**
Before any other step, detect the response language:
1. **Check user message language** - Analyze the language of the user's request
2. **Check OS locale:**
- Windows: Registry key `HKCU\Control Panel\International\Region` or `systeminfo`
- Linux/Mac: Environment variables `LANG`, `LC_ALL`, or `locale` command
3. **Store as RESPONSE_LANG** for the entire session
4. **ALL outputs MUST be in RESPONSE_LANG:**
- Task tables in RESPONSE_LANG
- Subagent prompts include: "All responses MUST be in {RESPONSE_LANG}"
- Explanations in RESPONSE_LANG
- Error messages in RESPONSE_LANG
- Technical terms may remain in English when no translation exists
**Language Detection Priority:**
1. User message language (highest)
2. OS locale language
3. Project context language
4. Default: English (only if none detected)
**Exception:** If user explicitly requests a different language, honor that request temporarily, then return to RESPONSE_LANG.
### STEP 0.5: CONTEXT COMPLETENESS CHECK (MANDATORY)
**CRITICAL: This step is MANDATORY for ALL requests. No exceptions.**
**Purpose:** Ensure Claude has 100% clear context before executing ANY task.
**Context Completeness Score:**
| Fattore | Punti | Condizione |
|---------|-------|------------|
| WHAT chiaro | -2 | Azione specifica identificata |
| WHERE chiaro | -2 | File/componente target identificato |
| WHY chiaro | -1 | Motivazione/obiettivo specificato |
| HOW chiaro | -1 | Approccio suggerito o vincoli specificati |
| Ambiguita presente | +3 | Termini vaghi ("fix", "improve", "optimize") |
| Multi-task non strutturato | +2 | Piu task senza dipendenze chiare |
| Scope non definito | +2 | Non chiaro cosa e IN e cosa e OUT |
**Score Interpretazione:**
- **Score <= 0**: CONTESTO COMPLETO -> Proceed to STEP 1
- **Score 1-3**: CONTESTO PARZIALE -> Chiedi chiarimenti specifici
- **Score >= 4**: CONTESTO INSUFFICIENTE -> OBBLIGATORIO fare domande prima di procedere
**MANDATORY CLARIFICATION QUESTIONS:**
Se Score > 0, usa AskUserQuestion con questo formato:
```
AskUserQuestion(
questions: [
{
question: "Per procedere ho bisogno di chiarimenti:",
header: "Contesto",
options: [
{label: "Spiega dettagli", description: "Fornisci piu contesto sulla richiesta"},
{label: "Specifica file", description: "Indica quali file sono coinvolti"},
{label: "Definisci scope", description: "Cosa e incluso e cosa escluso"},
{label: "Procedi cosi com'e", description: "Accetti che Claude possa fare assunzioni" }
]
}
]
)
```
**DOMANDE OBBLIGATORIE se mancano:**
| Se manca | Domanda obbligatoria |
|----------|---------------------|
| WHAT | "Cosa specificamente vuoi che faccia? (es: fix bug, add feature, refactor)" |
| WHERE | "Su quali file o componenti devo lavorare?" |
| WHY | "Qual e l'obiettivo o la motivazione di questa modifica?" |
| SCOPE | "Cosa e incluso e cosa escluso dal lavoro?" |
**Anti-Patterns - NON FARE MAI:**From eroslifestyle/Claude-Orchestrator-AI-Evolution, MIT.
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Mar 8, 2026 (8 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get orchestrator running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
orchestrator skill. Agent Mart. https://agentmart.dev/skills/eroslifestyle-orchestrator-14fb6c (last updated 2026-10-24)