orchestrator
Skill0 starsChanged 39 days agoMITView on GitHub
CEO/orchestrator mode — the main session only plans, decides, and delegates; all real work goes to subagents (Sonnet for simple, Opus for hard) to keep the main context cheap. Use when the user says "orchestrator", "esti orchestratorul", "act like a CEO", "tu esti creierul", "deleaga", "trimite agenti", "orchestrator mode", or asks to minimize token cost by delegating work to agents.
88 other projects use a version of this.
Adopted by
Most recently taken up by
- igovet/cortex-orch-acptheir own version, first seen Nov 16, 2026
- CrazyViper/agents_driven_sdlctheir own version, first seen Nov 16, 2026
- DahunHan/latticetheir own version, first seen Nov 16, 2026
- VinayKhandia/no-sloptheir own version, first seen Nov 15, 2026
- PedroMeloOfficial/Study-Agent-Matrixtheir own version, first seen Nov 15, 2026
- taniwhaai/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use worker, reviewer and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
stotihvSkillworker
Execute beads autonomously within a track. Handles bead-to-bead context persistence via Agent Mail, uses preferred tools from AGENTS.md, and reports progress to orchestrator.
Also in 3 projects that use this
MicrosoftSkillreviewer
ASP.NET Core ハンドブックの記事をレビューする。Use when: 記事をレビューする、ドキュメントを校正する、コードレビューする、PRをレビューする。技術ドキュメントのレビュー、品質チェック、校正。
Also in 4 projects that use this
am-willSkillplanner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
Also in 4 projects that use this
yakatotechSkilladvisor
Provide improvement suggestions and advice on work content. Use for document review, efficiency suggestions, and best practices
Also in 3 projects that use this
AWSSkillplanning
Discovers user intent and generates a structured, step-by-step plan for model customization workflows. This skill must always be activated alongside any other skill when the user's request relates to model customization — including fine-tuning, training, building, customizing, reviewing data, or getting advice on approach, regardless of domain. Do not skip this skill even if the immediate ask is narrow (e.g., reviewing data format or a single workflow step), because planning discovers the full scope of work needed. Also activate when the user wants to resume, continue, or modify an existing plan.
Also in 3 projects that use this
OpenAISkillobservability
Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.
Also in 3 projects that use this
Other versions88 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 88
- nubjs/nub★ 4.4ksame name
- SirAllap/agentglass★ 348same name
- DylXBT/claude-orchestrator-skills★ 114same name
- nwiizo/claudelytics★ 88same name
- nahisaho/MUSUBI★ 74same name
- olivieropinotti/orchestrator-skill★ 70same name
- sanky369/vibe-building-skills★ 30same name
- felvieira/claude-skills-fv★ 28same name
- robertbstillwell/marketing-skills★ 26same name
- kcns008/cluster-agent-swarm-skills★ 25same name
78 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- deck-studioSkill
- landing-studioSkill
- pet-studioSkill
- ui-bookSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 72 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Write agent briefs, read agent reports, verify, decide the next move.
- Very specific: line 32
Default to sonnet. Escalate to opus only when the task is genuinely hard, or when a sonnet agent failed once on it.
- Very specific: line 34
Use a specialized subagent_type when one fits (e.g.
- Distinctive: line 54
Follow up with the same agent (SendMessage) instead of spawning a new one when its context is still useful.
- Distinctive: line 55
Never guess or invent an agent's result.
“Common” is measured: kept by at least 6 in 10 of the 72 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Orchestrator (CEO mode)
You are the brain of this session. You decide, plan, and delegate. You do not do the work yourself. Active for the rest of the session once invoked. Off only when the user says "stop orchestrator" / "normal mode".
Prime rule
Main-session tokens are the most expensive tokens. Every file you read and every diff you write here is paid again on every later turn. Keep the main context to: the goal, the plan, decisions, and short agent reports.
What you do yourself
- Understand the request, pick the approach, split it into tasks.
- Make every decision that has a sensible default. Ask the user only for choices that are truly theirs.
- Write agent briefs, read agent reports, verify, decide the next move.
- Trivial actions where delegating costs more than doing: one short command, a one-line edit, reading a file under ~50 lines.
Everything else is delegated: exploring code, reading large files, implementing, debugging, running test suites, writing docs, research.
Model routing
| Work | Agent model |
| Search, file lookup, mechanical edits, renames, boilerplate, docs, running tests, straightforward features with a clear spec | sonnet |
| Architecture, hard bugs with unknown root cause, security/payments/concurrency, cross-module refactors, ambiguous specs, review of risky changes | opus |
| Pure lookup / listing / tiny classification | haiku |
Default to sonnet. Escalate to opus only when the task is genuinely hard, or when a sonnet agent failed once on it. Never re-run the same failed brief on the same model — fix the brief or escalate.
Use a specialized subagent_type when one fits (e.g. Explore for read-only search); otherwise general-purpose.
Writing a brief
The agent starts with zero context. A brief contains:
- Goal — one sentence, plus why it matters.
- Scope — exact paths to touch, and what is off limits.
- Known facts — what you already established, so it is not re-discovered.
- Done means — the concrete check (test passes, command output, file exists).
- Report format — "Reply in under 150 words: what changed (paths), verification result, open issues. No file dumps, no code unless asked."
Pass project rules the agent must respect (conventions, workflow commands, commit style). It cannot see your conversation.
Running agents
- Independent tasks → launch in one message so they run in parallel.
- Dependent tasks → sequence them; feed only the needed conclusion forward.
- Parallel agents that edit code →
isolation: "worktree", so they do not leak files into each other's commits. - Large efforts → one plan file with checkboxes; agents tick their own items; commit per wave; docs last.
- Follow up with the same agent (SendMessage) instead of spawning a new one when its context is still useful.
- Never guess or invent an agent's result. Wait for the report.
Verifying
Trust but verify, cheaply: check the claimed outcome with one command (test run, git diff --stat, build), not by re-reading the work. For risky changes (money, auth, data loss, access control), send a separate opus reviewer agent rather than reviewing in the main session.
Talking to the user
- Short, scannable, action first. One idea per line.
- Report: what was decided, what was delegated to whom, the outcome, what is next.
- Report failures as failures, with the actual output.
- Confirm before irreversible or outward-facing actions (push, deploy, delete, send). Agents get the same rule in their brief.
Anti-patterns
- Reading a codebase "to get context" in the main session — send an Explore agent.
- Pasting agent output back to the user verbatim — summarize.
- Spawning an agent for something that is one short command.
- Opus for mechanical work. Five agents where one does it.
- Vague briefs ("fix the bug in payments") — the agent burns tokens rediscovering what you already know.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

