route · v1.0.0 · 2026-10-14 · sha256 6cf7ecae02a9542f
route v1.0.0A
Immutable. This exact content never changes and is served at /api/v1/blob/6cf7ecae02a9542f.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_kwooa44aqu4avhib/6cf7ecae02a9542fd26019121b563c030b14663f3c943dd7211f03fc39ef72fa.json
Then /plugin install route@markdownregistry-kwooa44aqu4avhib in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: route version: 1.0.0 description: Map a task to the right vskills skill — reads what the user is trying to do, names the matching skill (or sequence), and hands back a paste-ready invocation. Use when unsure which skill fits, where to start, or what to run, or as the entry point to the pipeline. disable-model-invocation: true argument-hint: "[what you're trying to do]" recommended: false --- # Route The entry question is what the user wants to happen next, not which skill sounds related. Match the intent below, name the skill, and stop — routing is not doing the work. | Intent | Skill | |---|---| | Unclear or consequential product/design choice | `grill` | | Turn an agreed outcome into tracker work | `issues` | | Execute a referenced task end to end, verified PR or evidenced blocker | `ship` | | Drive open PRs to merged: checks, threads, stacks, overnight runs | `land` | | Understand a subsystem, a call chain, or a blast radius — no changes | `investigate` | | A bug or regression whose cause isn't known | `debug` | | Checkpoint unfinished work for a later session | `snapshot` | | Pick up work a prior session or agent left | `resume` | | Commit and push under explicit authority, proven by remote SHA | `push-handoff` | | Install the GitHub-Actions review bot into a repo | `pr-review` | | Audit a whole codebase into a ranked ticket backlog | `audit` | | The constraint, not the code, decides whether work can ship | `delivery-constraints` | | One-ticket TDD at a real production seam | `implementation-tdd` | | Delegate parallel lanes without losing ownership | `subagent-delegation` | | Decide between approaches or harden a choice | `ponytail` | | Cost/throughput model for an AI subscription or provider | `ai-subscription-unit-economics` | | Benchmark a model's tokens-per-second | `test-tps` | | Turn a docs folder into a retrieval graph | `setup-obsidian` | | Install vskills on a new machine or harness | `setup-vskills` | Principles are not entry points — they are disciplines the delivery skills invoke: real-artifact, evidence-over-report, bounded-repair, named-constraints, independent-verdict. Name one when the user is asking how to think, not what to run. ## The usual sequences - Clear task → `ship`. Nothing else needed; it reads the tracker itself. - Unclear task → `grill` → `issues` → `ship` per issue → `land` to merge. - "Is it broken?" → `investigate`; "fix it" → `debug` → `ship` → `land`. - Away and back → `snapshot` out, `resume` in. ## The reply One line per hop: the skill, why it fits, and the invocation to paste — `/route` answers like "`issues` — the outcome is agreed, it needs tracker work: `/issues spec.md`". When no skill fits, say so plainly instead of forcing the nearest one.