# Perf Benchmarker

Use when running performance benchmarks, establishing baselines, or validating...

- Repository: https://github.com/composio-community/awesome-claude-plugins (1978 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-07-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add composio-community/awesome-claude-plugins --skill perf-benchmarker -g -a claude-code -y`
Codex: `npx skills add composio-community/awesome-claude-plugins --skill perf-benchmarker -g -a codex -y`
Cursor: `npx skills add composio-community/awesome-claude-plugins --skill perf-benchmarker -g -a cursor -y`
Gemini CLI: `npx skills add composio-community/awesome-claude-plugins --skill perf-benchmarker -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add composio-community/awesome-claude-plugins`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.