benchmark-guardian
Validates performance claims through rigorous, data-driven benchmarking.
Install
mkdir -p .claude/skills/benchmark-guardian && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11044" && unzip -o skill.zip -d .claude/skills/benchmark-guardian && rm skill.zipInstalls to .claude/skills/benchmark-guardian
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use for JS/TS performance-sensitive changes, benchmark additions, benchmark regressions, benchmark result JSON, or any claim that code is faster, smaller, cheaper, or not slower.Key capabilities
- →State a benchmark hypothesis
- →Add focused benchmarks for iteration
- →Write structured JSON to `benchmarks/results/*latest.json`
- →Run correctness tests or fuzzers for the same path
- →Update evidence documentation for performance
- →Include command, output path, key rows, and caveats in final response
How it works
This skill guides the benchmarking workflow by requiring a hypothesis, focused benchmarks, structured JSON results, and correctness tests. It also updates performance documentation.
Inputs & outputs
When to use benchmark-guardian
- →Benchmark code optimization
- →Verify performance regressions
- →Generate benchmarking docs
About this skill
Benchmark Guardian
Do not make performance claims from intuition.
Workflow
-
State the benchmark hypothesis:
- target behavior,
- metric,
- fixture,
- command,
- acceptance threshold or baseline.
-
Prefer focused benchmarks while iterating:
npx evidence-kit add-benchmark --name core --language js
npm run bench:evidence
-
Write structured JSON to
benchmarks/results/*latest.json. -
Run correctness tests or fuzzers for the same path before saying a performance change is safe.
-
Update evidence docs:
npm run docs:perf
npm run docs:perf:search -- <benchmark topic>
Result Rules
- Keep timeout, error, unsupported, and bad-result rows visible.
- Report exact command and output file.
- Report fixture-level rows, not only aggregate scores.
- If benchmark scope changed, run
npm run bench:scopeornpx evidence-kit scope. - If the benchmark came from external research, cite the fetch manifest and source note path.
Final Response
Include the command, output path, key rows, and caveats such as dirty worktree, missing baseline, or local machine noise.
When not to use it
- →When making performance claims from intuition without benchmarks
- →When not needing structured JSON benchmark results
- →When not requiring correctness tests or fuzzers for performance changes
Limitations
- →Do not make performance claims from intuition
- →Benchmark results must be written to `benchmarks/results/*latest.json`
- →Final response must include command, output path, key rows, and caveats
How it compares
This skill enforces a structured benchmarking workflow with explicit steps for hypothesis, iteration, and documentation, unlike ad-hoc performance testing.
Compared to similar skills
benchmark-guardian side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| benchmark-guardian (this skill) | 0 | 2mo | Review | Intermediate |
| react-best-practices | 22 | 3mo | No flags | Intermediate |
| react-component-performance | 2 | 5mo | No flags | Advanced |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
react-best-practices
redpanda-data
Client-side React performance optimization patterns.
react-component-performance
Dimillian
Analyze and optimize React component performance issues (slow renders, re-render thrash, laggy lists, expensive computations). Use when asked to profile or improve a React component, reduce re-renders, or speed up UI updates in React apps.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
reviewing-nextjs-16-patterns
djankies
Review code for Next.js 16 compliance - security patterns, caching, breaking changes. Use when reviewing Next.js code, preparing for migration, or auditing for violations.
validate-typescript
BerryKuipers
Run TypeScript compiler type-checking (tsc --noEmit) to validate type safety and catch type errors. Works with any TypeScript project. Returns structured output with error counts, categories (type/syntax/import errors), and affected files. Used for quality gates and pre-commit validation.
ts-testing
johnlindquist
Design, implement, and maintain high‑value TypeScript test suites using popular JS/TS testing libraries. Use this skill whenever the user is adding tests, debugging failing tests, or refactoring code that should be covered by tests.