benchmark

Run automated browser benchmarks and compare timing metrics against baselines.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/anishs1207/agentic-cli --skill benchmark-anishs1207
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/anishs1207/agentic-cli/tree/main/.agents/skills/gstack-benchmark
Command: npx skills add https://github.com/anishs1207/agentic-cli --skill benchmark-anishs1207

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and quantify performance regressions by running automated browser-based benchmarks and comparing against baselines.

Core Features & Use Cases

  • Auto-discovers pages to test and collects detailed timing data (TTFB, FCP, LCP, DOM Interactive, DOM Complete, Full Load) and resource breakdowns.
  • Baseline capture and comparison across branches, with visual and text reports highlighting regressions and warnings.
  • Trend analysis and slowest resources identification to guide optimization efforts.
  • Telemetry and reporting to share results with team and stakeholders.

Quick Start

Run /benchmark <url> to perform a full performance audit and compare against your baseline.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I detect web performance regressions across branches?

Detect web performance regressions by running automated browser-based benchmarks against established baselines. The tool compares timing metrics across development branches and generates visual reports highlighting any performance degradation to surface regressions early.

What timing metrics are collected for web page benchmarking?

Web page benchmarking collects standard timing metrics including TTFB, FCP, LCP, DOM Interactive, DOM Complete, and Full Load. It also gathers detailed resource breakdowns to identify slowest resources and guide optimization efforts.

How do I automate performance audits for staging and production environments?

Automate performance audits for staging and production by running the benchmark command against target URLs. The tool auto-discovers pages, captures timing data, and compares results against baseline files to flag regressions in any environment.

Do I need a browse daemon to run multi-page performance benchmarks?

Yes, a browse daemon is required to run multi-page performance benchmarks. The daemon handles automated browser interactions to collect timing data across multiple page scenarios for accurate regression detection.

What is the best way to establish a performance baseline for regression detection?

Establish a performance baseline by running the benchmark tool against a stable version of your web application. The tool captures standard timing metrics and saves them as baseline files for automated comparison during future branch testing.

Can I generate reports from web performance benchmark results to share with stakeholders?

Yes, the benchmark tool generates visual and text reports highlighting regressions and warnings. These reporting outputs provide actionable insights and telemetry data suitable for sharing performance trends with your team and stakeholders.