benchmark

Measure web performance and detect regressions against baselines in CI workflows.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/GTC6244/ToolBridge --skill benchmark-gtc6244
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/GTC6244/ToolBridge/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/GTC6244/ToolBridge --skill benchmark-gtc6244

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Performance regression detection across web pages using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes, and compares changes across PRs.

Core Features & Use Cases

  • Baseline management: capture and store baselines for repeatable comparisons.
  • Page-level metrics: collect TTFB, FCP, LCP, DOM timing, and resource usage.
  • Trend analysis: track performance over time and across branches to spot regressions.
  • Use case: run /benchmark on a PR page to detect regressions before merge.

Quick Start

Run the benchmark against a URL to measure performance, compare it to the baseline, and generate a report.

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

Core Web Vitals tracking involves measuring TTFB, FCP, and LCP metrics during page loads, then comparing these metrics against stored baselines to identify performance regressions across different branches and pull requests.

How do I establish performance baselines for page load times?

Establishing performance baselines for page load times requires running a benchmark against a URL to capture and store initial metrics for DOM timing, Core Web Vitals, and resource sizes as a reference point for future comparisons.

Do I need a browse daemon to track Core Web Vitals over time?

Yes, you need a browse daemon to track Core Web Vitals over time, because the benchmark tooling depends on this daemon to collect page-level metrics, access baselines storage, and generate trend comparison reports.

What is the best way to track resource size changes across branches?

The best way to track resource size changes across branches is to use performance benchmarking with baselines, which captures resource usage during page loads and compares these metrics to detect regressions over time.

Can I use benchmark baselines for CI workflow performance testing?

Yes, you can use benchmark baselines for CI workflow performance testing by applying the regression detection tooling to pull requests, which measures page load times and compares them against stored baseline data before merge.