which-skilllisted
Install: claude install-skill OmarBenje/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, and never shipped — a fresh install has no catalogue at all.
**If it is missing, run the generator before routing.** It sits next to this file, so use the path of the skill directory you were loaded from and not a relative one — your working directory is the person's project, not the skill:
```bash
bash ~/.claude/skills/which-skill/scripts/build-catalogue.sh
```
If the skill was installed by `npx skills`, that path is `~/.agents/skills/which-skill/` instead. Routing against someone else's catalogue is the one way this skill produces confident, useless answers: it names commands the person does not have. Regenerate it too whenever it looks stale — the file carries its own `Last generated:` date, and 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