/

/benchmark

by Composiocomposiohq/awesome-claude-plugins2k stars

644

Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.

1 file
1 KB
Updated 8 months ago
GitHub

Ask your Agent

Use this Skill: https://skilld.dev/gh/composiohq/awesome-claude-plugins/benchmark

This session only. Nothing lands on disk.

SKILL.md

1 KB raw

≈52 tokens always: the name and description. ≈195 when used: this file.

perf-benchmarker

Run sequential benchmarks with strict duration rules.

Follow docs/perf-requirements.md as the canonical contract.

Required Rules

Benchmarks MUST run sequentially (never parallel).
Minimum duration: 60s per run (30s only for binary search).
Warmup: 10s minimum before measurement.
Re-run anomalies.

Output Format

command: <benchmark command>
duration: <seconds>
warmup: <seconds>
results: <metrics summary>
notes: <anomalies or reruns>

Output Contract

Benchmarks MUST emit a JSON metrics block between markers:

PERF_METRICS_START
{"scenarios":{"low":{"latency_ms":120},"high":{"latency_ms":450}}}
PERF_METRICS_END

Constraints

No short runs unless binary-search phase.
Do not change code while benchmarking.

Source: SKILL.md on GitHub

Third-party checks

No third-party reports yet.

Provenance

Signed by skilld at 12730bf. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 8 months ago

Capability

version: 1.0.0
argument-hint: <command> [duration]