benchmark

Measure and compare web performance metrics across pull requests.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/MissTully/Gstack --skill benchmark-misstully
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/MissTully/Gstack/tree/main/benchmark
Command: npx skills add https://github.com/MissTully/Gstack --skill benchmark-misstully

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Benchmarking and instrumentation to detect performance regressions by establishing baselines for page load times, Core Web Vitals, and resource sizes, and by comparing before/after on every PR.

Core Features & Use Cases

  • Baseline generation for performance metrics and automatic regression detection across PRs.
  • Per-page timing collection via the browse daemon and historical trend analysis.
  • Use case: quickly identify boomerang regressions after code changes and guide performance fixes.

Quick Start

Run the benchmark with a URL to measure performance and compare it to existing 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 can measure and compare page load times and Core Web Vitals against established baselines. This Skill automates before-and-after comparisons on every PR to identify regressions.

How does Core Web Vitals baseline generation work for PR analysis?▼

Core Web Vitals baseline generation works by collecting per-page timing metrics from the browse daemon for specified URLs. It establishes a performance baseline and automatically compares new PR changes against it to catch regressions.

Can I track historical performance trends for page load times?▼

Yes, you can track historical performance trends for page load times. The Skill supports a trend mode that aggregates historical metrics collected via the browse daemon to visualize performance shifts over time.

What do I need to generate a performance diff report for a specific URL?▼

To generate a performance diff report, you need the browse tool, a target URL, and existing performance baselines. The diff mode compares current metrics against these baselines to highlight resource size and timing changes.

Does this tool support quick performance checks without a full baseline?▼

Yes, the tool supports a quick mode for rapid performance checks. This mode allows you to measure current page load times and Core Web Vitals on a target URL without requiring a full baseline comparison beforehand.

What is the best way to identify boomerang regressions after code changes?▼

The best way to identify boomerang regressions after code changes is by comparing pre-merge and post-merge web performance metrics. This Skill automatically diffs page load times and resource sizes to guide your performance fixes.