in-your-own-words
Skill41k starsChanged 4 days agoMITView on GitHub
Play back the goal, the problem, and the success check in your own words when a brief is genuinely ambiguous — vague, contested, or leaving real forks open — so misunderstanding is caught cheaply. Not for well-specified or routine tasks.
29 other projects use a version of this.
Trending
Quiet since January.thin dataabout the whole repository
Most recently taken up by
- caidanw/skillstheir own version, first seen Nov 8, 2026
- painhardcore/pstacktheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodeword for word, first seen Nov 8, 2026
- tristanphvn/keeltheir own version, first seen Nov 8, 2026
- hidenobunagai/astacktheir own version, first seen Nov 8, 2026
- requie/endostacktheir 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 poteto-help, principle-explain-the-number and 5 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.
ianclearySkillpoteto-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 10 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 20 projects that use this
jaydubya818Skillprinciple-test-behavior-not-implementation
Apply when tests mirror internals instead of asserting observable outcomes.
Also in 21 projects that use this
jaydubya818Skillprinciple-attack-the-premise
Apply when repeated fixes fail and a shared assumption may be wrong.
Also in 19 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 10 projects that use this
- +2 more from jaydubya818
Other versions29 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 · 28
- backnotprop/pstack★ 3.8ksame name
- jtaroreh/agystack★ 128same name
- Dimon94/dverity★ 107same name
- Dimon94/skills★ 107same name
- dsebban/skills★ 71same name
- TheOnlyFusionCube/potetos-for-everyone★ 21same name
- creedants/pstack-t3★ 18same name
- painhardcore/pstack★ 18same name
- mariusflorescu/pstack-t3★ 13same name
- caidanw/skills★ 11same name
18 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
- howSkill
- hudSkill
- intentSkill
- interrogateSkill
- 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 6 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 17
Before the first tool call on genuinely ambiguous work — a brief that is vague, contested, or leaves real forks open — say back what you …
“Common” is measured: kept by at least 6 in 10 of the 6 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
In Your Own Words
Before the first tool call on genuinely ambiguous work — a brief that is vague, contested, or leaves real forks open — say back what you understood — in your words, not the user's phrasing echoed. Misunderstanding caught now costs a sentence; caught after execution it costs the work. A well-specified brief needs no playback: start, and report what you did.
The playback
Three parts, plain language:
- The goal: what the user will have when this is done.
- The problem (if any): what stands in the way, as you understand it.
- The success check: how we will know it worked.
Then one line: "Right? Correct me where I drifted." — and stop for the
answer on risky work; proceed-and-report on clearly reversible work
(principles skill, Never block on the human).
Rules
- Playback is a paraphrase, not a copy: if you can only repeat the brief, you have not understood it yet.
- Name your assumptions inline ("I am assuming staging, not production").
- Disagreement between your playback and the brief is the point — surface it, do not smooth it.
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.

