← ClaudeAtlas

skills-orchestratorlisted

Use when a task needs two or more skills, or has separate parts that could be split across multiple agents — for coding work (bugs, features, tests, reviews), documents and business work (reports, slides, spreadsheets, PDFs, research), or a mix of both, such as "fix this bug and write a report for my manager". Also use when no installed skill fits part of a task, when two skills give conflicting instructions, or when the user says "reset score for" a skill, such as "reset score for pdf".
YahyaLendani/Claude-Skills-orchestrator · ★ 1 · Data & Documents · score 70
Install: claude install-skill YahyaLendani/Claude-Skills-orchestrator
# Skills Orchestrator Pick and combine the right skills for a task without being asked, split big jobs across agents (each with its own task and skills), and learn from what worked. Works in two modes, chosen automatically: **coding** and **documents**. ## When to use - The task needs two or more skills (e.g. debugging + a report). - The task has separate parts (different kinds of work, or parts that could run in parallel). A single piece of work done in a few steps with one skill does not count. - Part of the task has no installed skill that fits. - Two skills you would use give opposite instructions. ## When not to use - The task needs one skill or none (e.g. "rename this variable", "make me one chart"). Use that skill directly, or just do the task. Don't show a mode line, a preview, or write memory. - The user asked to do it a specific way that doesn't involve orchestration. ## Flow 1. **Decide whether to orchestrate.** Check "When to use" above. If it doesn't apply, stop here and just do the task. 2. **Pick the mode.** Read the `## Clues` of [coding](modes/coding.md) and [documents](modes/documents.md). - Clues point one way → that mode. - Clues point both ways → split the task into parts; each part gets its own mode and its own agent. - Being inside a code repository only counts toward coding when the task has a coding part. A documents-only task in a repo (e.g. "summarise these PDFs") is documents mode, with no coding part to split off. - No clear clu