which
Skill1 starsChanged 9 days agoMITView on GitHub
Use when the user types /which to ask which ras skill fits a task. Answers with one or two skills, their order, and one line of reason each.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- petr-korobeinikov/skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- petr-korobeinikov/skills★ 1same name
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.
In this repository13 other files it gives its agents.
- architectureSkill
- artifactsSkill
- buildSkill
- debtSkill
- deep-reviewSkill
- diagnoseSkill
- distributed-architectureSkill
- finalizeSkill
- handoffSkill
- rulesSkill
- security-checkSkill
- sparSkill
- specSkill
The file
Files
Which
| Skill | Use when | Example request |
spec | A plan first, or a risky path was denied | "/spec add a retry" |
spar | Stress-test a plan or a decision by interview. User call only | "/spar my cache plan" |
build | Gate lane: implement an approved spec | "Spec approved, go ahead" |
finalize | Gate lane: defects, cuts, fresh checks, report | "Wrap it up" |
diagnose | The cause of a failure is unknown | "The export crashes, I do not know why" |
architecture | Styles, trade-offs, module interfaces, ADRs | "Monolith or modules for this app?" |
distributed-architecture | Split a system: service size, data ownership, transactions | "Should billing become its own service?" |
deep-review | Strict maintainability review of existing messy code | "Run a deep review of this module" |
artifacts | Build or check an HTML Artifact page | "Make this plan a page" |
security-check | A change touches auth, secrets, permissions, deletes or production | "Add an admin delete endpoint" |
debt | List the marked shortcuts. User call only | "/debt" |
handoff | Pass the work to a fresh session or another agent. User call only | "/handoff" |
rules | Install the coding rules. User call only | "/rules" |
A normal change needs no skill. The gate lane (risky path or /spec) runs spec, build, finalize. For a diff review, use the built-in /code-review.
Rule: answer with one or two skills and their order. Give one line of reason for each. Then stop. Make no edits.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.