benchmark

Compare live page navigation and resource-timing data to baseline JSONs for PR regressions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web apps often drift in performance after changes; this Skill provides automated baselining, comparison, and trend analysis to detect and alert on regressions in page load, rendering, and resource metrics.

Core Features & Use Cases

  • Baseline capture for page load timings, Core Web Vitals, and resource sizes.
  • PR diff and trend analysis to surface regressions across releases.
  • Quick-start workflow to run benchmarks on a target URL and compare results to baseline.

Quick Start

Run a benchmark on a target URL to collect performance data and compare it against the baseline.

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?

You can detect web performance regressions by collecting real performance data from a live page and comparing it against a JSON baseline. This surfaces diffs and regression signals for critical routes directly within your PR workflows.

What is the best way to track Core Web Vitals baselines across releases?

The best way to track Core Web Vitals baselines across releases is to capture baseline page load timings and resource sizes, then apply automated trend analysis to compare new measurements against these stored baselines over time.

How do I benchmark a live URL and compare page load timings?

You benchmark a live URL by running a quick-start workflow that collects navigation and resource timing data. It then compares these real performance metrics against a previously generated JSON baseline to identify any drift.

Do I need a browse daemon to collect resource timing data for performance analysis?

Yes, you need the browse daemon to collect navigation and resource timing data from the live page. This daemon gathers the real performance metrics required to generate the JSON outputs used for baselines and comparisons.

Can I measure page rendering and resource size regressions without manual inspection?

You can measure page rendering and resource size regressions without manual inspection by applying automated baselining and comparison across your PR workflows. This automatically alerts you to performance drift in resource metrics after code changes.