benchmark

Measure page load performance and detect regressions against baselines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Measure page load performance and detect regressions using the browse daemon, establishing baselines for TTFB, FCP, LCP, DOM metrics, and resource sizes.

Core Features & Use Cases

  • Baseline capture for TTFB, FCP, LCP, DOM metrics, and resource sizes.
  • Compare current results against historical baselines, surface regressions, and generate trend reports.
  • Use cases include PR performance gating, page-specific optimization, and regression alerting.

Quick Start

Run the benchmark against a URL to collect performance data and compare it to 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 page load performance regressions in a PR?

You can detect page load performance regressions by capturing baseline metrics for TTFB, FCP, LCP, and DOM sizes, then comparing current PR results against that baseline to surface any degradation.

What web vitals can I track for baseline performance capture?

Baseline performance capture supports tracking TTFB, FCP, LCP, DOM metrics, and resource sizes to establish a historical reference for your page load performance.

How do I set up canary-style monitoring for page-specific performance?

Canary-style monitoring for page-specific performance is set up by running the benchmark against a URL to collect data, establishing a baseline, and generating trend reports to alert on regressions.

Does benchmarking with the browse daemon require external dependencies?

No external dependencies are required; the benchmarking process is implemented entirely with Bash tooling and JSON outputs using the browse daemon, with optional telemetry and policy controls.

What is the best way to compare current performance results against a historical baseline?

The best way to compare current results against a historical baseline is to run a diff analysis, which surfaces regressions and generates trend reports across PRs for continuous monitoring.

Can I gate pull requests based on web vital regressions?

Yes, PR performance gating is a supported use case; you compare current page load metrics against established baselines and use the resulting diff and trend reports to block regressions.