hyperfine-benchmarking
/hyperfine-benchmarking
Use this skill to benchmark shell commands reliably with warmup runs, statistical summaries, and exportable artifacts using hyperfine.
- Author
- akillness ↗
- Repository
- jeo-skills ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use this skill to benchmark shell commands reliably with warmup runs, statistical summaries, and exportable artifacts using hyperfine.
Original author description
Use this skill to benchmark shell commands reliably with warmup runs, statistical summaries, and exportable artifacts using hyperfine.
How it works
- When to use this skill
- Instructions
- Examples
- Best practices
- References
SKILL.md preview
---
name: hyperfine-benchmarking
description: Use this skill to benchmark shell commands reliably with warmup runs, statistical summaries, and exportable artifacts using hyperfine.
allowed-tools: Bash Read Write
---
# hyperfine-benchmarking
Benchmark CLI commands with reproducible methodology instead of one-off `time` output.
## When to use this skill
- Compare two or more command variants (`tool-a` vs `tool-b`)
- Validate performance impact before/after script changes
- Attach benchmark evidence to PRs
## Instructions
1. Confirm tool availability.
2. Keep input/workdir/environment stable across compared commands.
3. Run warmups and enough runs for stable variance.
4. Export JSON/markdown outputs for review.
5. Summarize relative speedup + risk notes.
## Examples
### Availability check
```bash
hyperfine --version
```
### Two-command comparison
```bash
hyperfine \
--warmup 3 \
--min-runs 10 \
'cmd_a --with flags' \
'cmd_b --with flags'
```
### Parameter sweep
```bash
hyperfine \
--warmup 3 \
--parameter-list mode fast,balanced,thorough \
'mytool --mode {mode} input.txt'
```
### Export artifacts
```bash
hyperfine \
--warmup 3 \
--min-runs 10 \
--export-json benchmark.json \
--export-markdown benchmark.md \
'cmd_a' 'cmd_b'
```
## Best practices
- Prefer relative speedup and confidence ranges over single-run claims.
- Do not compare commands with different semantics unless outputs are normalized.
- If variance is high, increase runs or reduce background noise before concluding.
- Record dataset/path and exact command strings in PR text.
## References
- hyperfine project: https://github.com/sharkdp/hyperfine
- Docs: https://github.com/sharkdp/hyperfine#readme
Versions
The database has no other skills named hyperfine-benchmarking.
Database snapshot: 13.11.2026 · package version bb34912a5d78 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100benchmark-controls
Benchmark control hazards: mutated controls, disagreeing harnesses, VM lock scaling, hyperfine 2.0 exports. Use when benchmarking, comparing timings, A/B runs, hyperfine. - 90but-performance-tests
Use when creating, changing, running, or debugging shell-based `but` CLI performance scenarios under `crates/but/tests/performance`, including Hyperfine runs, fixture setup, setup-to-test state, and output inspection. - 100benchmark
Run scalex performance benchmarks, profiling, and timing analysis. Use this skill whenever the user asks to benchmark scalex, measure performance, profile index/query times, compare before/after performance of a change, investigate bottlenecks, or mentions \"benchmark\",… - 100benchmark
Run scalex performance benchmarks, profiling, and timing analysis. Use this skill whenever the user asks to benchmark scalex, measure performance, profile index/query times, compare before/after performance of a change, investigate bottlenecks, or mentions \"benchmark\",… - 100modern-cli-tools
Safe, current usage of ripgrep, fd, bat, eza, fzf, zoxide, sd, jq, yq, hyperfine, delta, bottom, dust, duf, procs, btop, and tldr. Use when selecting or invoking modern Unix CLI tools, especially instead of fragile shell pipelines. - 100time
Command execution timing — microsecond precision, statistical analysis, comparison. Zero barrier — use with x-cmd or shell built-in time command. Use for "timing", "benchmark", "performance", "profiling".