benchmark-checklist
Skill0 starsChanged 4 months agoNo licenceView on GitHub
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.
We split this skill into the rules it gives an agent
6 rules. 4 are common, 0 are distinctive, and 2 are very specific to this project.
4
Common
Most of the 22 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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 22 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.
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 21
- backnotprop/pstack★ 2.7k80% same
- uzairansaruzi/p3-stack★ 12694% same
- mariusflorescu/pstack-t3★ 980% same
- creedants/pstack-t3★ 877% same
- alexnthnz/keel★ 480% same
- anis-dr/skills★ 380% same
- lucasheriques/pstack★ 379% same
- fullerzz/agent-skills★ 270% same
- Timmyy3000/skills★ 294% same
- conscientiousness/herdr-pstack-orchestrator★ 180% same
11 more not listed
Wrote their own version · 2
- jtaroreh/agystack★ 128same name
- woodbeary/later-dog★ 2same 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.
Used alongsideProjects with it also use poteto-help, principle-explain-the-number and 10 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 9 projects that use this
juancamiloqhzSkillprinciple-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 16 projects that use this
alexnthnzSkillin-your-own-words
Restate in your own words what you think the user's goals are and what problem they're trying to solve. Use for /keel:in-your-own-words.
Also in 8 projects that use this
fullerzzSkillcreate-formal-verification-skill
Generate a reusable project-local skill for model checking or proving code-linked properties. Use explicitly for /create-formal-verification-skill, model-checking a race, or proving an invariant; UI and service journey checks belong to create-verification-skill.
Also in 4 projects that use this
instructureSkillketchup
Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories
Also in 12 projects that use this
- fullerzzSkill
maintain-formal-verification-skill
Refresh a project's formal checks after covered code changes, distinguish verification drift from product bugs, and retain per-check coverage checkpoints. Use explicitly for /maintain-formal-verification-skill or auditing whether a model still describes the code.
Also in 3 projects that use this
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- apiSkill
- architectSkill
- arenaSkill
- automate-meSkill
- bennySkill
- blast-radiusSkill
- broSkill
- browserSkill
- cicdSkill
- correctSkill
- craft-helpSkill
- craft-modeSkill
- dbSkill
- debugSkill
- designSkill
- distilSkill
- documentSkill
- figure-it-outSkill
- gitSkill
- gpuSkill
- howSkill
- initSkill
- interrogateSkill
- issue-triageSkill
- make-bot-uiSkill
- mlSkill
- obsidianSkill
- orcaSkill
- principle-architectureSkill
- principle-backendSkill
- principle-frontendSkill
- principle-programmingSkill
- principle-testingSkill
- recallSkill
- refactorSkill
- reflectSkill
- researchSkill
- securitySkill
- show-me-your-workSkill
- swarmSkill
- tailscaleSkill
- tddSkill
- teachSkill
- unslopSkill
- whySkill
- write-prdSkill
- write-reportSkill
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.