Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →yzhao062/my-router
Context-aware router that detects work type and dispatches to the right skill. Ships with a minimal default routing table; extend it in a fork, or register project-local skills in a consuming repo via routing-table.local.md or an AGENTS.local.md Routing section.
Passed 21 of 24 test cases with the skill, and 10 of 24 without it.
and 15 more in the full report
11 fixed10 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/4/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to explicitly dispatch tasks in parallel across multiple worker sub-agents for fan-out execution. Which domain skill key in the routing table corresponds to this intent?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies prun as the skill for parallel fan-out execution. | Missed | Passed |
The instructions your model reads when the skill loads.
A routing layer that sits between the outer workflow (e.g., superpowers brainstorm/plan/execute/verify) and domain skills. The router reads the working directory, file types, and user prompt to decide which skill to invoke, so the user does not need to remember skill names.
In this repo's shipped form, the routing table has concrete entries for the six shipped skills (implement-review, ci-mockup-figure, readme-polish, editable-figure, my-router itself, and prun for explicit parallel fan-out intent). It is also designed as a pattern you extend. A fork of this repo edits references/routing-table.md directly. A consuming project, where that file is overwritten on every bootstrap, instead registers its own skills in a bootstrap-proof local file (routing-table.local.md at the repo root, or a ## Routing section in AGENTS.local.md); the router reads those rows and dispatches to them. See Extending the Router.
The router decides this. Not all tasks need superpowers' full ceremony.
| Task shape | Route | Why |
|---|---|---|
| Clear, scoped task with an obvious skill match (e.g., "review staged changes") | Direct dispatch — router picks the domain skill and runs it immediately | Brainstorming and planning add no value when the task is already well-defined |
| Open-ended, multi-step, or ambiguous task (e.g., "build a new feature", "restructure the paper") | Superpowers first — brainstorm → plan → execute (router dispatches during execute) → verify | These benefit from thinking before doing |
| Quick edit or fix (e.g., "fix the typo on line 42", "rename this variable") | Neither — just do it directly | No routing or workflow needed |
| Effort signal words in prompt (e.g., "extensively", "deep", "thorough", "in-depth", "carefully", "comprehensive") | Superpowers + extended thinking — enable extended thinking (Alt+T) and route through superpowers regardless of task shape | The user is explicitly asking for more deliberation |
The rule: if the domain skill is obvious and the scope is clear, skip superpowers and dispatch directly. If the task needs exploration or planning, let superpowers run the outer loop and the router dispatches during execution. If the user signals they want deep effort, always use superpowers with extended thinking enabled.
When superpowers is active, it handles workflow phases: brainstorm → plan → execute → verify. The router activates during the execute phase and dispatches to the right domain skill.
When superpowers is not active (direct dispatch or quick task), the router works standalone.
At dispatch time, the router checks three signals in order (keywords, file types, project structure). In a consuming project, before applying the shipped table below, it first merges any consumer-local routing extensions: a routing-table.local.md at the repo root, or a ## Routing section in AGENTS.local.md. These two files survive bootstrap (the shipped table does not), so they are where a consuming repo registers its own skills; on a keyword or file-type conflict, the local row wins. See Extending the Router.
The user's prompt often contains the clearest signal. The shipped routing table includes keyword entries for implement-review, ci-mockup-figure, readme-polish, and editable-figure. Add entries for your own skills in your fork's references/routing-table.md, or, in a consuming project, in a bootstrap-proof local file (see Extending the Router).
When a figure request explicitly asks for PowerPoint or native editability, take the editable-figure route ahead of the generic figure, README-polish, or slide routes. A request to simplify an existing editable figure stays on that route. An explicit HTML mockup, TikZ, screenshot, or prompt-only request keeps its requested format. Before taking that route, check that the session can perform the desktop PowerPoint validation editable-figure requires. If it cannot, explain the limitation and offer ci-mockup-figure only when its output fits the request. Do not silently substitute HTML for an explicitly requested PPTX.
See references/routing-table.md for the current table and the extension template.
For a paper or proposal explanatory figure, especially an overview or "Figure 1", read editable-figure/references/gallery/index.md through the normal skill lookup. Do this whichever figure skill the route selects, including a project-local variant such as nsf-figure-builder. When working for Yue Zhao, enforce its required preference-first design protocol as the top design priority. Inspect selected images and feedback, map confirmed qualities to the new design, and carry that mapping into prompts and implementation. Compare the result against those references. Preserve the requested output format; reading the gallery does not require PowerPoint or change a prompt-only task into a figure build.
test cases passed, vs 10 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.