- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add michael-denyer/pstack-claude --skill benchmark-checklist -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add michael-denyer/pstack-claude --skill benchmark-checklist -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add michael-denyer/pstack-claude --skill benchmark-checklist -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add michael-denyer/pstack-claude --skill benchmark-checklist -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/michael-denyer/pstack-claude/tree/HEAD/plugins/pstack/skills/benchmark-checklistDel publicador
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.mdResumen general
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.
Preguntas frecuentes
Descarga plugins/pstack/skills/benchmark-checklist/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/michael-denyer/pstack-claude.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.