perf-benchmarker

Run sequential performance benchmarks with enforced minimum durations and JSON output.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RnR-DND/ARC-HAWK-DD --skill perf-benchmarker-rnr-dnd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perf-benchmarker
Source: https://github.com/RnR-DND/ARC-HAWK-DD/tree/main/.agent/agentsys/.kiro/skills/perf-benchmarker
Command: npx skills add https://github.com/RnR-DND/ARC-HAWK-DD --skill perf-benchmarker-rnr-dnd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a standardized way to run performance benchmarks that meet specific duration and sequencing requirements, helping users establish reliable performance baselines and detect regressions.

Core Features & Use Cases

  • Sequential Benchmarking: Guarantees benchmarks run one after another without parallel execution.
  • Duration Enforcement: Ensures each run lasts at least 60 seconds (or 30 seconds for binary search), including warmup phases.
  • Use Case: A developer wants to validate that their application's response times remain consistent across releases by automatically executing benchmarks with strict timing rules.

Quick Start

Provide the benchmark command and duration to run a performance test adhering to the required rules.

Frequently Asked Questions about perf-benchmarker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate performance benchmarking with strict minimum run times?

Performance benchmarking automation is achieved by sequentially executing tests while enforcing strict minimum run durations of 60 or 30 seconds. This Skill validates performance, detects anomalies, and automatically re-runs benchmarks to output reliable JSON metrics.

What is the best way to enforce sequential execution and detect anomalies during benchmarking?

Enforcing sequential execution during benchmarking requires running tests strictly one after another without parallel processes. This Skill monitors timing to detect anomalies, automatically triggering re-runs to ensure performance validation conforms to strict timing rules.

Does this benchmarking approach output JSON metrics for regression testing analysis?

Yes, this benchmarking approach outputs JSON-formatted metrics specifically designed for regression testing analysis. It standardizes performance validation by providing reliable JSON metrics to establish baselines and detect software regressions across releases.

Can I use this for performance validation requiring 60-second minimum durations and warmup phases?

Yes, you can use this for performance validation requiring 60-second minimum durations. It strictly enforces timing rules including warmup phases to ensure each benchmark run lasts at least the specified duration, guaranteeing accurate timing measurements.

Why does my performance benchmark require a re-run when timing anomalies appear?

Performance benchmarks require a re-run when timing anomalies appear to ensure strict timing rules and measurement accuracy. This automated anomaly detection mechanism re-executes benchmarks to validate that performance metrics conform to specified durations.