Perf Theory Tester
- 2 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/awesome-slash
perf-theory-tester is a skill that runs controlled single-change experiments against a baseline to accept, reject, or mark inconclusive a performance hypothesis.
About
This skill runs controlled experiments to validate performance hypotheses. A developer uses it to test one hypothesis at a time by applying a single change, measuring the delta against a clean baseline, and reverting before the next experiment. It runs at least two validation passes, forbids parallel benchmarks, and records evidence to reach an accept, reject, or inconclusive verdict.
- Runs controlled performance experiments to validate hypotheses
- Applies a single change per experiment and reverts to baseline afterward
- Runs 2+ validation passes and records evidence for each run
Perf Theory Tester by the numbers
- 2 all-time installs (skills.sh)
- Ranked #464 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
perf-theory-tester capabilities & compatibility
- Capabilities
- hypothesis testing · controlled experiment · regression detection · debugging
- Use cases
- debugging · testing
What perf-theory-tester says it does
Test hypotheses using controlled experiments.
Revert to baseline before the next experiment.
One change per experiment.
npx skills add https://github.com/avifenesh/awesome-slash --skill perf-theory-testerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/awesome-slash ↗ |
What it does
Run a controlled single-change experiment against a clean baseline to accept or reject a performance hypothesis.
Who is it for?
Developers validating a performance hypothesis with disciplined, one-change-at-a-time experiments.
Skip if: Generating hypotheses or synthesizing final recommendations, which other skills handle.
When should I use this skill?
You are running controlled perf experiments to validate hypotheses.
What you get
A per-hypothesis verdict (accept, reject, or inconclusive) with measured deltas and recorded evidence.
- experiment verdict with metric deltas and evidence
By the numbers
- one change per experiment
- 2+ validation passes
Files
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.
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512FAQ
How many changes per experiment?
Exactly one change per experiment, reverted to baseline before the next.
How many validation passes?
At least two validation passes per experiment, with no parallel benchmarks.