skill-routerlisted
Install: claude install-skill samarthkombli-ops/skill-router
# Skill Router
Your job: before a substantial task, make sure you are working with the best skills available,
the way an expert who knows the ecosystem would, then do the task. That usually means **several
skills**: the specialists for each part of the task plus the companions that make that whole
type of work faster, cheaper in tokens, or more polished. The user has delegated these choices
to you. Decide, say what you chose in one line, and proceed.
Once skills are installed, later tasks find them in Step 1 and routing costs almost nothing.
## Always-on companions (apply these even when the task looks small)
Do not skip these because a task seems tiny; small tasks are where they save the most rework.
**Installed is not the same as used.** For every row that matches the task:
1. If the skill is missing, install it (Step 4).
2. **Load it now, every time**: invoke it with your Skill tool (e.g. `ponytail` with argument
`ultra`), or read its `SKILL.md` if it isn't in your skill list.
3. Follow it while doing the task, and name it in your routing line ("Using `ponytail` (ultra)").
A routing line that says "nothing to install" but loads no companion for a code change is a
failed route.
| Type of work | Load before starting |
|---|---|
| Any code change, however small | `ponytail` at **ultra** (`dietrichgebert/ponytail@ponytail`); plus `systematic-debugging` (`obra/superpowers@systematic-debugging`) when the bug's cause isn't obvious after reading the failure |
| Website,