skill-router
Alive skill router — reads the current project's stack and loads/unloads skills dynamically. Invoke at session start or when project context changes.
npx skills add stevesolun/ctx --skill skill-router --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# skill-router Reads `~/.claude/skill-manifest.json` and `~/.claude/pending-skills.json`. Executes the 5-stage pipeline. **No skipping stages.** ## Pipeline ``` 01-scope → 02-plan → 03-build → 04-check → 05-deliver ``` ## Invoke When - Session starts (automatic via using-superpowers pattern) - User switches projects or opens a new repo - `pending-skills.json` exists (mid-session signals detected) - User asks "what skills are loaded?" or "update my skills" ## Stage Files All stage files are in `references/`. Read and follow each in order. 1. **[01-scope](references/01-scope.md)** — Is a scan needed? 2. **[02-plan](references/02-plan.md)** — Run the scanner 3. **[03-build](references/03-build.md)** — Resolve the manifest 4. **[04-check](references/04-check.md)** — Validate before loading 5. **[05-deliver](references/05-deliver.md)** — Present to user See [check-gates.md](check-gates.md) for validation questions.
- Pipeline
- Invoke When
- Stage Files
What does the skill-router skill do?
Alive skill router — reads the current project's stack and loads/unloads skills dynamically. Invoke at session start or when project context changes.
How do I install it?
Run `npx skills add stevesolun/ctx --skill skill-router --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From stevesolun/ctx, a repository with 569 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.