skills.rest
binfen1
binfen1COMMUNITY
Explore all skills by this author →
GitHub

benchmark

Measure performance regressions with browse daemon baselines across PRs.

Updated Mar 23, 2026
Search Tags:#performance#benchmarking#regression#web-vitals#perf-analysis#page-load#browse-daemon
One-click install
npx skills add https://github.com/binfen1/my-skills --skill benchmark-binfen1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/binfen1/my-skills/tree/main/claude-code/benchmark
Command: npx skills add https://github.com/binfen1/my-skills --skill benchmark-binfen1

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. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time". (gstack)

Core Features & Use Cases

  • Phase 1: Setup baseline and report directories
  • Phase 2: Page discovery and data collection using the browse daemon perf commands
  • Phase 3: Collect navigation and resource performance metrics (TTFB, FCP, LCP, DOM times, etc.)
  • Phase 4: Baseline capture, compare current metrics to baseline, generate reports
  • Phase 5: Trend analysis, slowest resources, performance budgets, and recommendations

Quick Start

Invoke the skill with /benchmark <url> to begin full performance regression testing.

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 PRs?▼

Detect web performance regressions by establishing baselines for page load times, Core Web Vitals, and resource sizes, then comparing before and after metrics on every PR using the browse daemon.

What metrics are collected for Core Web Vitals performance benchmarking?▼

Core Web Vitals performance benchmarking collects navigation and resource timing data from the browser, including TTFB, FCP, LCP, and DOM times, to establish baseline performance metrics for comparison.

How do I set up page load time tracking for multiple URLs?▼

Set up page load time tracking by running perf commands through the browse daemon to discover pages, collect timing data, and store baselines in .gstack/benchmark-reports for multiple URLs.

Can I track bundle size and resource sizes in my PR workflow?▼

Yes, you can track bundle size and resource sizes in PR workflows by applying performance regression detection to page-speed audits, Lighthouse-style checks, and bundle-size tracking across multiple URLs.

What's the best way to analyze slowest resources and performance trends?▼

Analyze slowest resources and performance trends by capturing baseline metrics, comparing current results to baselines, and generating reports that include trend analysis, slowest resource identification, and performance budget recommendations.

Related Skills

Explore More Software Engineering Skills→
steadyfallsteadyfall

benchmark

Collect end-to-end web performance metrics from the browse daemon across pages.

Community
Advanced
GeneralJerelGeneralJerel
6

audit-performance

Audit performance budgets for Core Web Vitals, bundle size, and API latency.

Community
Advanced
involvexinvolvex

web-perf

Analyze web performance with Chrome DevTools MCP tools to measure Core Web Vitals.

Community
Advanced
GTC6244GTC6244

benchmark

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

Community
Intermediate