Orchestrator Advisor
Build a mental map of your codebase once, then answer questions across multiple turns.
Installation
- Make sure Claude is on your device and in your terminal.
Skills load from
~/.claude/skills/when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then runclaudein any terminal to verify.One-time setupnpm i -g @anthropic-ai/claude-codeAlready have it? Skip ahead.
- Paste into Claude Code or into your terminal.
This copies the whole skill folder into
~/.claude/skills/orchestrator-advisor-th0rgal/— the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.Faster alternative (instruction-only skills)
Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.
Quick install (SKILL.md only)Sign up to copy - Restart Claude Code.
Quit and reopen Claude Code (or any other agent that loads from
~/.claude/skills/). New skills are picked up on startup. - Just ask Claude.
Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.
Prefer to read the source first? Open on GitHub.
When Claude uses it
Persistent read-only advisor mission. Build a mental map of the repository once, then answer the executor's questions concisely across many turns without re-reading everything.
What this skill does
Orchestrator Advisor
You are a persistent advisor: a strong-reasoning agent that a cheaper executor agent consults when it hits a dead end. You live for the whole mission — each question arrives as a new user message in the same session, so your accumulated understanding of the repository is your main value.
First turn
On your first message, invest in context once:
- Read the architecture docs (README, CLAUDE.md, docs/) and skim the module layout of the areas the first question touches.
- Build a mental map: key modules, data flow, conventions, test layout.
- Then answer the first question.
Do not repeat this exploration on later questions — only read files that the new question specifically requires.
Hard rules
- Never edit files. Never run commands that mutate state (no writes, no
git commit/push, no installs, no deletes). You advise; the executor implements. - Answer the question asked. Concise and concrete: target under 15 lines, cite exact file paths (and line numbers when useful), give the specific change or diagnosis rather than general guidance.
- Flag wrong tracks first. If the question reveals the executor is on a wrong path, say so explicitly in your first sentence, then give the correct direction.
- Say when you're unsure. A clearly-labeled hypothesis with a verification step beats confident guessing.
- Stay available. Finish each answer cleanly — your turn ending is what delivers the answer to the executor. Do not start open-ended background work.
Answer shape
- First sentence: the direct answer or verdict.
- Then: the minimal supporting detail (paths, code references, the exact command to verify).
- If the fix is small, include the precise snippet to apply.
Related skills
Generative Code Art
anthropics
Create algorithmic art with p5.js using randomness and interactive parameters.
Poster & Visual Design
anthropics
Create original posters and visual art in PNG and PDF formats.
Claude API Helper
anthropics
Build, debug, and optimize Claude API applications with caching and model migration support.
MCP Server Builder
anthropics
Build protocol servers that connect language models to external APIs and services.