sharpen
Skill4 starsChanged 15 days agoMITView on GitHub
Rewrite a draft prompt so it asks for an expert-depth version of the same task (expert moves, raw sources, named methods, an outside check) without widening scope. Returns the rewritten prompt and does not do the task. Use for "/sharpen <prompt>" or "make this prompt better before I send it".
38 other projects use a version of this.
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/pstacktheir own version, 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 and poteto-help.
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
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
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 38
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- backnotprop/pstack★ 3.8ksame name
- backnotprop/bro★ 176same name
- hamzafarooq/claude-code-starter★ 145same name
- joetawil7/first-pass★ 128same name
- jtaroreh/agystack★ 128same name
- dsebban/skills★ 71same name
- TheOnlyFusionCube/potetos-for-everyone★ 21same name
- creedants/pstack-t3★ 18same name
28 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 repository61 other files it gives its agents.
- architectSkill
- arenaSkill
- automate-meSkill
- benchmark-checklistSkill
- blast-radiusSkill
- broSkill
- catch-upSkill
- catch-up-videoSkill
- correctSkill
- create-formal-verification-skillSkill
- create-verification-skillSkill
- figure-it-outSkill
- howSkill
- interrogateSkill
- in-your-own-wordsSkill
- maintain-formal-verification-skillSkill
- maintain-verification-skillSkill
- make-bot-uiSkill
- no-commentsSkill
- principle-attack-the-premiseSkill
- principle-boundary-disciplineSkill
- principle-build-the-leverSkill
- principle-encode-lessons-in-structureSkill
- principle-exhaust-the-design-spaceSkill
- principle-experience-firstSkill
- principle-explain-the-numberSkill
- principle-fix-root-causesSkill
- principle-foundational-thinkingSkill
- principle-guard-the-context-windowSkill
- principle-laziness-protocolSkill
- principle-make-operations-idempotentSkill
- principle-migrate-callers-then-delete-legacy-apisSkill
- principle-minimize-reader-loadSkill
- principle-model-the-domainSkill
- principle-never-block-on-the-humanSkill
- principle-outcome-oriented-executionSkill
- principle-prove-it-worksSkill
- principle-redesign-from-first-principlesSkill
- principle-separate-before-serializing-shared-stateSkill
- principle-sequence-verifiable-unitsSkill
- principle-subtract-before-you-addSkill
- principle-test-behavior-not-implementationSkill
- principle-treat-input-as-untrustedSkill
- principle-type-system-disciplineSkill
- recallSkill
- reflectSkill
- security-reviewSkill
- setup-endostackSkill
- show-me-your-workSkill
- statechartSkill
- swarmSkill
- tarique-helpSkill
- tarique-modeSkill
- tddSkill
- teachSkill
- technical-writingSkill
- threat-modelSkill
- try-endostackSkill
- typescript-best-practicesSkill
- unslopSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 29 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Do not start the task. If the user wants the work done now, do it without this skill.
- Distinctive: line 20
Leave decisions that belong to the user open in the rewrite, and mark each one, for example "(you decide: keep backward compatibility or …
“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
Take the prompt the user is about to send and return a deeper version of it. Depth means the same task done the way the best practitioner would do it. Scope stays the same: do not add features, extra deliverables, or neighbouring problems.
Do not start the task. If the user wants the work done now, do it without this skill. If the user wants to check that you understood them, use the in-your-own-words skill.
Steps
- Answer four questions about the task in the draft, one short paragraph each:
- Expert moves. What would a top practitioner in this field do here that the draft does not ask for?
- Raw sources. What primary, unprocessed material would that expert start from, instead of the summaries or second-hand material the draft relies on? For example the source code instead of the docs, the raw logs instead of a dashboard, the specification instead of a blog post, the production data instead of a fixture.
- Methods. Which concrete methods and tools would that expert apply? Name them.
- Outside check. What check, independent of your opinion and the user's, would show the result is correct? For example a test that fails before and passes after, a comparison against a reference implementation, a measurement, a second reviewer from outside the work.
- Rewrite the draft so it asks explicitly for those things. Keep the user's goal, constraints, and voice. Keep it about as short as the work allows: a prompt that names the method and the check is enough, and the agent receiving it will fill in the steps.
- Leave decisions that belong to the user open in the rewrite, and mark each one, for example "(you decide: keep backward compatibility or not)". Do not settle them on the user's behalf.
Output
The four answers, then the rewritten prompt in a code block so the user can copy it. Nothing else.
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.