benchmark

Detect web page performance regressions by comparing metrics against baselines.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/curielmc/beat-SPY --skill benchmark-curielmc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/curielmc/beat-SPY/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/curielmc/beat-SPY --skill benchmark-curielmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time.

Core Features & Use Cases

  • Baseline creation for TTFB, FCP, LCP, DOM metrics, and resource sizes.
  • PR regression detection by comparing current runs against baselines with alerting.
  • Trend analysis across history to identify degradation and guide optimizations.

Quick Start

Run the benchmark against a target URL to measure and compare performance and save results to .gstack/benchmark-reports.

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 on a pull request?

To detect web performance regressions on a pull request, this Skill collects baseline page load metrics and resource sizes, then compares current runs against stored baselines to alert on degradations before merging changes.

What is the best way to track Core Web Vitals trends over time?

Tracking Core Web Vitals trends over time involves establishing baselines for metrics like TTFB, FCP, and LCP, then analyzing historical run data stored in benchmark reports to identify long-term performance degradation.

Can I measure page load times and resource sizes without external dependencies?

Yes, you can measure page load times and resource sizes without external dependencies by using the built-in browse daemon to gather data, storing results directly under the local .gstack/benchmark-reports directory.

How does baseline creation work for web vitals and DOM metrics?

Baseline creation for web vitals and DOM metrics works by running the benchmark against a target URL to measure current performance, saving those initial TTFB, FCP, LCP, and resource size values as a comparison anchor for future runs.

Why do I need to monitor performance across commits?

You need to monitor performance across commits to catch regressions early during PR validation, ensuring that recent code changes do not degrade established page load baselines or increase resource sizes over time.