benchmark

Analyze browser performance data to detect regressions across pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection and baseline establishment for web apps, using the browse daemon to measure and compare metrics across PRs.

Core Features & Use Cases

  • Baseline and compare core web metrics like TTFB, FCP, LCP, and DOM events.
  • Track resource sizes and overall page performance over time to surface regressions.
  • Use case: Before merging a PR that changes critical UI, run benchmark to ensure no slowdowns or regressions.

Quick Start

Run the benchmark workflow against a target URL to capture metrics and compare them to baselines.

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 pull requests?

To detect web performance regressions across pull requests, you analyze browser performance data using a benchmarking workflow that establishes baselines for Lighthouse and Web Vitals metrics. It then compares current PR measurements against these stored baselines to surface slowdowns.

What core web vitals are tracked when establishing a page load baseline?

When establishing a page load baseline, the tracked core web vitals include TTFB, FCP, LCP, and DOM events. The benchmark also captures resource-size breakdowns to monitor overall page performance and resource loading changes over time.

How do I ensure a UI change doesn't slow down page load before merging?

To ensure a UI change doesn't slow down page load before merging, run a benchmark workflow against your target URL. It captures current metrics and compares them to established baselines, alerting you to any page load or resource-size regressions.

Does this benchmarking approach work without external dependencies?

Yes, this benchmarking approach works without external dependencies. It relies on a built-in browse daemon to capture browser performance data, measuring web vitals and resource sizes directly to establish baselines and detect regressions.

What is the best way to track resource-size changes over time for web apps?

The best way to track resource-size changes over time for web apps is by capturing resource breakdowns through a browse daemon. This stores the data as baselines, allowing you to compare subsequent page load measurements and detect size regressions across PRs.