benchmark-checklist
Skill74 starsChanged 2 days agoLicence not identifiedView on GitHub
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.
54 other projects use a version of this, 32 of them edited; most edited versions we compared are an older text (12 of 31); 4 new projects in the last 4 weeks, against 0 the 4 before.
How people change it
Most projects run an older version: 12 of 31 add nothing and lack rules this one has, most likely added since.
Of the 31 edited versions we compared: 14 keep every rule, 12 are an older text, 5 made changes of their own.
Not in older versions
- Use this when you produce a performance number: a PR's before and after, a regression claim, a hillclimb harness, or a library or config choice. Answer each question with evidence from a run, not a guess about the code.missing from 8 of 12
- Check the load average with
uptimeand the core count withnproc. If the machine is busy, find out what is running. If you cannot stop it, interleave the sides so both see the same noise, and say so in the report.missing from 6 of 12
Rules people drop
- Use this when you produce a performance number: a PR's before and after, a regression claim, a hillclimb harness, or a library or config choice. Answer each question with evidence from a run, not a guess about the code.dropped by 3 of 5
- Write down the claim you expect to make, in the words you would ship ("export is 30% faster at p50 on the 60k-row dataset"). The questions test that sentence.dropped by 2 of 5
- Read the measurement script. Note what it times, counts, and ignores.dropped by 2 of 5
- Check the load average with
uptimeand the core count withnproc. If the machine is busy, find out what is running. If you cannot stop it, interleave the sides so both see the same noise, and say so in the report.dropped by 1 of 5 - Keep a PR body to one primary number, per the Opening a PR playbook. Put the runs, range, and limiter evidence in a linked artifact or notes file.dropped by 1 of 5
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Surging: 4 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- GoBeromsu/craft-skillsedited, first seen Nov 16, 2026
- gfunc/skillsword for word, first seen Nov 16, 2026
- shiwenbin1617/pstackword for word, first seen Nov 16, 2026
- 0xrsydn/pstack-piedited, first seen Nov 15, 2026
- Scino/fstackedited, first seen Nov 15, 2026
- Dimon94/dverityword for word, first seen Nov 15, 2026
Used with
Projects with it also use 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.
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 14 projects that use this
Other versions54 projects use a version of this.
Word for word · 14
- backnotprop/pstack★ 4.2k100% same
- Dimon94/dverity★ 107100% same
- Dimon94/skills★ 107100% same
- mariusflorescu/pstack-t3★ 13100% same
- adjohn/pstack★ 9100% same
- alexnthnz/keel★ 5100% same
- shiwenbin1617/pstack★ 4100% same
- conscientiousness/herdr-pstack-orchestrator★ 2100% same
- kwaa/skills★ 2100% same
- gfunc/skills★ 1100% same
4 more not listed
Edited · 32
- uzairansaruzi/p3-stack★ 12678% same
- dsebban/skills★ 7197% same
- painhardcore/pstack★ 22100% same
- TheOnlyFusionCube/potetos-for-everyone★ 2196% same
- creedants/pstack-t3★ 1896% same
- Scino/fstack★ 1398% same
- caidanw/skills★ 1196% same
- krishhgg/t3term★ 1119% same
- mdsmithaustin/pstack★ 9100% same
- 0xrsydn/pstack-pi★ 799% same
22 more not listed
Wrote their own version · 8
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- jtaroreh/agystack★ 128same name
- jimyag/dotfiles★ 11same name
- requie/endostack★ 4same name
- wilbeibi/wilbeibi-skills★ 2same name
- woodbeary/later-dog★ 2same name
- morochena/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 repository73 other files it gives its agents.
- algorithms/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-reachSkill
- architectSkill
- arenaSkill
- automate-meSkill
- bklite-ops-product-designSkill
- blast-radiusSkill
- broSkill
- codebase-designSkill
- code-reviewSkill
- correctSkill
- create-formal-verification-skillSkill
- create-verification-skillSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- figure-it-outSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- howSkill
- implementSkill
- improve-codebase-architectureSkill
- interrogateSkill
- in-your-own-wordsSkill
- ketchupSkill
- ketchup-videoSkill
- maintain-formal-verification-skillSkill
- maintain-verification-skillSkill
- make-bot-uiSkill
- no-commentsSkill
- poteto-modeSkill
- 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-type-system-disciplineSkill
- recallSkill
- reflectSkill
- setup-matt-pocock-skillsSkill
- setup-pstackSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 4 are common, 1 is distinctive, and 1 is very specific to this project.
4
Common
Most of the 38 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.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 38 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.
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.

