how
Skill41k starsChanged 4 days agoMITView on GitHub
Walk through how a subsystem works — a fast explorer maps the territory, an explainer writes the layered walkthrough. Use for "how does X work", onboarding on unfamiliar code, or before changing a subsystem you cannot yet explain.
90 other projects use a version of this.
Trending
Quiet since January.thin dataabout the whole repository
Most recently taken up by
- Loner1024/skillstheir own version, first seen Nov 8, 2026
- caidanw/skillstheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodeword for word, first seen Nov 8, 2026
- endqwerty/endstacktheir own version, first seen Nov 8, 2026
- tristanphvn/keeltheir own version, first seen Nov 8, 2026
- dhruvsaxena1998/skillstheir own version, first seen Nov 8, 2026
Who's talking about Yeachan-Heo/oh-my-claude-sisyphus
- A Hacker News story“Sisyphus Now Lives in Oh My Claude”Hacker News · Jan 11, 2026 · 52 points
- Yeachan-Heo/oh-my-claudecode“Silent update security issue”GitHub · Jan 10, 2026 · 1 reactions
- anthropics/claude-plugins-official“feat: Add oh-my-claude-sisyphus multi-agent orchestration plugin”GitHub · Jan 12, 2026
The biggest 3 of 3 mentions linking to the repository that our crawl found. Each line is their own headline.
Used with
Projects with it also use setup-pstack, principle-explain-the-number and 2 more.
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.
bnemaSkillsetup-pstack
Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.
Also in 25 projects that use this
ianclearySkillprinciple-explain-the-number
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
Also in 28 projects that use this
- ianclearySkill
poteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
Also in 14 projects that use this
eryzerzSkillmake-bot-ui
Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.
Also in 19 projects that use this
Other versions90 projects use a version of this.
Word for word · 1
- Yeachan-Heo/oh-my-claudecode★ 41k100% same
Edited · 0
None found.
Wrote their own version · 89
- backnotprop/pstack★ 3.8ksame name
- poteto/how★ 878same name
- moeru-ai/xsai★ 667same name
- jtaroreh/agystack★ 128same name
- uzairansaruzi/p3-stack★ 126same name
- Dimon94/dverity★ 107same name
- Dimon94/skills★ 107same name
- dsebban/skills★ 71same name
- roerohan/skills★ 29same name
- overextended/skills★ 22same name
79 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.
In this repository90 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- src/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- .github/CLAUDE.mdCLAUDE.md
- commandsSkill
- agent-doc-disciplineSkill
- ai-slop-cleanerSkill
- architectSkill
- architecture-surveySkill
- arenaSkill
- ask-navigatorSkill
- askSkill
- autopilotSkill
- autoresearchSkill
- babysitSkill
- benchmark-checklistSkill
- blast-radiusSkill
- broSkill
- cancelSkill
- configure-notificationsSkill
- correctSkill
- create-formal-verification-skillSkill
- create-verification-skillSkill
- debugSkill
- deepinitSkill
- deep-interviewSkill
- diagramSkill
- drydockSkill
- executeSkill
- external-contextSkill
- figure-it-outSkill
- fix-ciSkill
- fix-merge-conflictsSkill
- get-pr-commentsSkill
- graphSkill
- harborSkill
- hillclimbSkill
- hudSkill
- intentSkill
- interrogateSkill
- in-your-own-wordsSkill
- ketchupSkill
- ketchup-videoSkill
- launchSkill
- loftSkill
- maintain-formal-verification-skillSkill
- maintain-verification-skillSkill
- mapSkill
- minimal-code-disciplineSkill
- minimal-prose-disciplineSkill
- modelsSkill
- omc-doctorSkill
- omc-setupSkill
- personal-modeSkill
- omc-planSkill
- principlesSkill
- project-session-managerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 88 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Every behavioral claim cites code you or the explorer read this session.
“Common” is measured: kept by at least 6 in 10 of the 88 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
How
Explain how a subsystem works, layered so each layer stands alone. Two roles, two passes:
- Explore (read-only, fast): dispatch
oh-my-claudecode:exploreto map the subsystem — entry points, main flows, data shapes, state, external calls, and the files that own each. Explorer returns a map with file:line citations, not prose. - Explain (lead): write the walkthrough from the map, reading the cited code yourself where the claim is load-bearing.
Output shape
- One paragraph: what the subsystem does and for whom, no jargon.
- Walkthrough: the main path end to end, step by step, each step citing
file:line. Diverge into how errors and retries are handled at the point they occur. - Edge cases and invariants: what must stay true for the walkthrough to hold, and what happens when it does not.
- Boundaries: what this subsystem deliberately does not do.
Rules
- Every behavioral claim cites code you or the explorer read this session; an uncited claim is labeled a guess.
- The walkthrough explains the code as it is, not as it should be; design
critique belongs to
whyandreview. - Size the depth to the ask: a routing question gets one paragraph plus the relevant slice, not the full walkthrough.
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.