perf-theory-tester
Use when running controlled perf experiments to validate hypotheses.
Profile →npx skills add agent-sh/agentsys --skill perf-theory-tester --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# perf-theory-tester Test hypotheses using controlled experiments. Follow `docs/perf-requirements.md` as the canonical contract. ## Required Steps 1. Confirm baseline is clean. 2. Apply a single change tied to the hypothesis. 3. Run 2+ validation passes. 4. Revert to baseline before the next experiment. ## Output Format ``` hypothesis: <id> change: <summary> delta: <metrics> verdict: accept|reject|inconclusive evidence: - command: <benchmark command> - files: <changed files> ``` ## Constraints - One change per experiment. - No parallel benchmarks. - Record evidence for each run.
- Required Steps
- Output Format
- Constraints
What does the perf-theory-tester skill do?
Use when running controlled perf experiments to validate hypotheses.
How do I install it?
Run `npx skills add agent-sh/agentsys --skill perf-theory-tester --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agent-sh/agentsys, a repository with 923 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.