- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add michael-denyer/pstack-claude --skill benchmark-checklist -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add michael-denyer/pstack-claude --skill benchmark-checklist -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add michael-denyer/pstack-claude --skill benchmark-checklist -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add michael-denyer/pstack-claude --skill benchmark-checklist -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/michael-denyer/pstack-claude/tree/HEAD/plugins/pstack/skills/benchmark-checklistFrom the publisher
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.
For a quick ballpark the user asked for, one run is enough. Still check questions 4 and 7, and say that it is one run. Skip the rest unless that run looks wrong. A choice between options is never a ballpark.
uptime and the core count with nproc. 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.top, pidstat), a runtime profiler (node --cpu-prof, py-spy, perf), I/O wait, and syscall counts (strace -c on Linux), then map the hot spot to source. Watch the load generator too: if it saturates first, you measured the load generator. If a change did not move the number, the limiter explains why, so find it before you call the change useless.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 re
---name: benchmark-checklistdescription: Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work…---# plugins/pstack/skills/benchmark-checklist/SKILL.mdOverview
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.
FAQ
Download plugins/pstack/skills/benchmark-checklist/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/michael-denyer/pstack-claude.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.