sharpen
Skill1 starsChanged 19 days agoMITView on GitHub
Use whenever a message about a task says ultrathink, think deeper, go deeper or this is too shallow, and for /sharpen. Makes the task deeper, not bigger. Names what a top professional would do, the raw material they would start from, and what would prove the result right, then does that version of the task.
38 other projects use a version of this, 13 of them edited.
Adopted by
Most recently taken up by
- Yeachan-Heo/oh-my-claude-sisyphustheir own version, first seen Nov 8, 2026
- Loner1024/skillstheir own version, first seen Nov 8, 2026
- caidanw/skillstheir own version, first seen Nov 8, 2026
- painhardcore/pstackedited, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 8, 2026
- endqwerty/endstacktheir own version, first seen Nov 8, 2026
Used with
Projects with it also use ketchup-video, maintain-formal-verification-skill and 9 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.
tristanphvnSkillketchup-video
Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.
Also in 14 projects that use this
TheOnlyFusionCubeSkillmaintain-formal-verification-skill
Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, \"is the model still true to the code\", or after merges and refactors that touched verified code without rechecking it.
Also in 18 projects that use this
- TheOnlyFusionCubeSkill
create-formal-verification-skill
Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, \"model-check this race\", \"prove this invariant\", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.
Also in 19 projects that use this
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
- ianclearySkill
principle-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
Xia-AtaraxiaSkillbenchmark-checklist
Vets performance measurements for the limiter, tuning, physical limits, errors, repeatability, relevance, and proof that timed work happened. It applies to 'check this benchmark', 'report this speedup', measured regressions, and choosing a library or configuration from numbers. It reports spread and gaps before drawing a conclusion. Not for general testing policy or choosing test oracles - use principle-testing.
Also in 26 projects that use this
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 13
- backnotprop/pstack★ 3.8k10% same
- jtaroreh/agystack★ 12810% same
- painhardcore/pstack★ 1811% same
- mariusflorescu/pstack-t3★ 1310% same
- adjohn/pstack★ 910% same
- alexnthnz/keel★ 510% same
- lucasheriques/pstack★ 310% same
- conscientiousness/herdr-pstack-orchestrator★ 210% same
- lrstanley/skills★ 110% same
- Tashila-109/tstack-skills★ 110% same
3 more not listed
Wrote their own version · 25
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- backnotprop/bro★ 176same name
- hamzafarooq/claude-code-starter★ 145same name
- joetawil7/first-pass★ 128same name
- dsebban/skills★ 71same name
- TheOnlyFusionCube/potetos-for-everyone★ 21same name
- creedants/pstack-t3★ 18same name
- caidanw/skills★ 11same name
- requie/endostack★ 4same name
15 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 repository17 other files it gives its agents.
- broooooSkill
- did-we-break-itSkill
- finish-the-prSkill
- fix-it-properlySkill
- just-tell-meSkill
- lets-build-pyramidsSkill
- next-time-fasterSkill
- no-added-commentsSkill
- onmywatchSkill
- plan-the-big-oneSkill
- show-meSkill
- statechartSkill
- talk-is-cheapSkill
- trust-issuesSkill
- trust-me-broSkill
- walk-me-throughSkill
- you-get-meSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 29 edited versions we read keep these.
3
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 13
If this is a small question or task with no deeper version, skip the rest of this skill.
- Distinctive: line 24
Do not add features, scope or extra deliverables.
- Distinctive: line 26
Leave open the choices that belong to the reader, and ask those in one short question.
“Common” is measured: kept by at least 6 in 10 of the 29 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
sharpen
Make the task deeper, not bigger. Same goal, better work.
Task: $ARGUMENTS. If that is empty, the current task.
If this is a small question or task with no deeper version, skip the rest of this skill. Give exactly what was asked, at the size asked. If it says one sentence, write one sentence.
Otherwise, answer these four in a line or two each, about this exact task:
- What would a top professional in this field do here that was not asked for?
- What is the rawest material they would start from, instead of a summary someone already made?
- Which specific methods and tools would they use?
- What, other than you or the reader, would show the result is right?
Then rewrite the task in a few lines so it asks for exactly that, and do it.
- Do not add features, scope or extra deliverables. If the rewrite is longer to build but not more correct, cut it.
- Go to the raw material yourself: the code, the logs, the data, the source of the library.
- Leave open the choices that belong to the reader, and ask those in one short question.
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.