routing-capability-graph
Use when the system must translate confirmed intent, failed gates, missing artifacts, risks, and tools into the smallest safe set of outcome capabilities and techniques.
Profile →npx skills add casioreview20-glitch/forge-os --skill routing-capability-graph --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.
# Routing the Capability Graph ## Core principle Retrieve outcome candidates from intent and current gate gaps. Freeze the minimal executable route with inclusion and exclusion reasons. The runtime owns deterministic scope, coverage, policy, and evidence checks; the agent owns only the judgment that cannot be reduced safely to code. ## Do not activate when - the exact technique and provider were explicitly selected - provider installation before the desired outcome is known
- Core principle
- Do not activate when
What does the routing-capability-graph skill do?
Use when the system must translate confirmed intent, failed gates, missing artifacts, risks, and tools into the smallest safe set of outcome capabilities and techniques.
How do I install it?
Run `npx skills add casioreview20-glitch/forge-os --skill routing-capability-graph --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 casioreview20-glitch/forge-os, a repository with 11 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.