hyperfine-benchmarking — Claude Code skill
hyperfine-benchmarking — a skill that runs commands with warmup cycles and collects timing statistics. Compare tool variants or validate performance changes before committing, with exportable evidence.
no license 251 installs ★ 61 updated 2026-10-24
npx skills add akillness/jeo-skills --skill hyperfine-benchmarking -a claude-codeWhat hyperfine-benchmarking does
Available for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. The skill wraps hyperfine to go beyond one-off time runs: it executes multiple passes with warmup, computes mean and variance, and exports results to JSON and Markdown suitable for code review.
Built-in safeguards ensure stable environment, identical inputs across compared commands, and enough repetitions for confident conclusions. Examples cover two-command comparison, parameter sweeps, and guidance on interpreting results—when variance is high, add more runs rather than drawing conclusions from noise.
Requires hyperfine in PATH. Absolute speed depends on command complexity and system load, but relative speedup of one variant over another (with all else equal) comes out reliably.
What it helps with
- measure performance difference between two tool versions
- prove a script optimization actually speeds things up
- gather timing statistics for a performance report
- test which command parameters run fastest
- attach benchmark evidence to a pull request
Example prompts for the agent
- Compare curl and wget download speed, run each 10 times with 3 warmups and show the results.
- Run a parameter sweep testing fast, balanced, and thorough modes, then export all three to JSON and Markdown.
- Benchmark my script before and after my changes, export both results so I can see the speedup.
How to install hyperfine-benchmarking
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill hyperfine-benchmarking -a claude-code2Manually: put the files in place
~/.claude/skills/hyperfine-benchmarking/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/hyperfine-benchmarking/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill hyperfine-benchmarking -a codex2Manually: put the files in place
.agents/skills/hyperfine-benchmarking/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill hyperfine-benchmarking -a cursor2Manually: put the files in place
.cursor/skills/hyperfine-benchmarking/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install akillness/jeo-skills .agent-skills/hyperfine-benchmarking/SKILL.md2Manually: put the files in place
.github/skills/hyperfine-benchmarking/SKILL.md1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill hyperfine-benchmarking -a gemini-cli2Platform CLI
gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/hyperfine-benchmarkingManually: put the files in place
.devin/skills/hyperfine-benchmarking/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill hyperfine-benchmarking -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about hyperfine-benchmarking
How do I install hyperfine-benchmarking in Claude Code?
Run npx skills add akillness/jeo-skills --skill hyperfine-benchmarking -a claude-code, then open ~/.claude/skills/hyperfine-benchmarking/SKILL.md.
What does hyperfine-benchmarking do?
Executes commands multiple times with warmup, collects timing for each run, computes mean and variance, and exports results to JSON and Markdown for analysis.
What does the skill need to work?
Hyperfine must be in PATH—install it via your system package manager. Input data and environment must be identical across all commands you compare.