which-skilllisted

Recommends which skill, or which ordered chain of skills, to run for the task at hand — across every installed pack. Use it whenever the request is about choosing the tool rather than doing the work — "which skill", "what should I use", "what's the right workflow", "where do I start", "how do I approach this". Use it too when someone pastes a review report, a bug, a plan or a backlog and asks how to proceed, because what they want is an order of operations, not the execution. Prefer this skill over answering from memory — a developer with several packs installed has many skills that do almost the same job, and arbitrating between them is worth far more than listing them.
whichskill/whichskill · ★ 0 · AI & Automation · score 58

Install: claude install-skill whichskill/whichskill

# Which skill to run You route. You do not do the work. The failure mode this skill exists to remove: naming every plausible skill. A list of nine names is worse than no answer — the person walks away holding the entire arbitration, which is the problem they came with. Your output is a chain, an order, and the arbitration already settled. ## Before you route: the catalogue must be real `references/catalogue.md` lists the skills actually installed on **this** machine. It is generated, never hand-written. **If it is missing, or still carries the `NOT GENERATED` marker, run `scripts/build-catalogue.sh` before routing.** Routing against someone else's catalogue is the one way this skill produces confident, useless answers: it will name commands the person does not have. Regenerate it too whenever it looks stale — packs get installed and removed. ## Method ### 1. Place the request in the loop Five positions. The position decides which third of the catalogue is even relevant. | Position | What is true | Where to look | |---|---|---| | **Framing** | Nobody knows what to build yet, or not precisely enough | `/office-hours`, `/spec`, `/grill-with-docs`, `superpowers:brainstorming`, `/wayfinder` | | **Building** | The what is settled; it remains to be done | `/implement`, `/tdd`, `/to-tickets`, `/codebase-design` | | **Checking** | It is built — does it work, is it safe, does it look right | `/qa`, `/review`, `/cso`, `/design-review`, `/benchmark` | | **Shipping** | It works a