router
Skill1 starsChanged 4 days agoMITView on GitHub
Author the smallest sufficient route of suite capabilities into ignored `route.md`. Use when the next capability is unclear, work spans several capabilities, or current state may already satisfy part of the request; skip it when one capability obviously applies.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- dcamunas/model-routertheir own version, first seen Nov 15, 2026
- grainulation/grainulatortheir own version, first seen Nov 12, 2026
- gamedev-skills/awesome-gamedev-agent-skillstheir own version, first seen Nov 11, 2026
- lizzyDeng/claude-skillstheir own version, first seen Nov 8, 2026
- apattichis/agentic-research-toolkittheir own version, first seen Nov 8, 2026
- Wellsonr/skillsettheir own version, first seen Nov 8, 2026
Used with
Projects with it also use research and setup.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- gamedev-skills/awesome-gamedev-agent-skills★ 9ksame name
- grainulation/grainulator★ 86same name
- lubusIN/frappe-skills★ 68same name
- timharris707/skills★ 44same name
- jammyfu/open-game-skills★ 13same name
- Canary-ECAD/eplan-scripting-skill★ 6same name
- Aetherdz/huntpack★ 4same name
- SunCherry/agentic-AI_analog_IC_auto-designer★ 4same name
- sam-ash-cy/sams-agentic-workflow★ 3same name
- Adnova-Group/muster★ 2same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Read Routing Policy; it selects the target repository and shapes step prompts.
- Very specific: line 38
When current state already satisfies the target, replace the numbered steps with one None: <established postcondition> line.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Router
Purpose
Author one bounded route of public capabilities from the current target and authoritative state, seal it as .first-four-hours/routes/<slug>/route.md, and return control. Never execute a routed capability, plan, edit source, publish, commit, push, or create a PR; write only that route and its local Git exclude rule.
Author
Read Routing Policy; it selects the target repository and shapes step prompts. Draft the route outside that repository:
# Route: <target>
Repository: <absolute path of the target repository>
<only the current state needed to read the steps>
## Steps
1. `<capability>`
- Why: <why it is needed now>
- Input: <authoritative input or current-state dependency>
- Result: <expected observable result>
- Prompt:
```text
<copyable request that runs this step>
```When current state already satisfies the target, replace the numbered steps with one None: <established postcondition> line.
Seal
python <skill-root>/scripts/cli.py --repo-root <Repository path> \
--input draft=<draft.md> --input slug=<route-slug> --format json runRepair each reported defect in the draft and rerun; on a repository mismatch, pass the intended repository rather than editing the line to where you run. Complete when the result names the sealed route.md under that Repository; return that path and end with step 1's sealed Prompt as the one optional next step, or none for a None: route. Only the user's later "yes" starts it, via its capability and gates, and the user runs a user-invoked step's Prompt themselves. Exhausting the route returns control; it does not by itself complete the target.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

