benchmark

Benchmark web pages against baselines and detect performance regressions.

Updated Mar 22, 2026

Search Tags:#performance #reports #monitoring #lighthouse #benchmark #web-vitals #pages

Ready to run

npx skills add https://github.com/jeisenback/original-curse-killer --skill benchmark-jeisenback

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/jeisenback/original-curse-killer/tree/main/.claude/skills/benchmark
Command: npx skills add https://github.com/jeisenback/original-curse-killer --skill benchmark-jeisenback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Measures web performance and detects regressions by benchmarking pages against baselines.

Core Features & Use Cases

Baseline capture and comparison across PRs to identify performance regressions.
Quick audit and multi-page analysis, including navigation timing and resource metrics.
Trend analysis over time to track performance improvements or degradations.

Quick Start

Run /benchmark <url> to start a full performance audit and baseline comparison.

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

You can detect web performance regressions by benchmarking pages against established baselines. This skill captures TTFB, FCP, LCP, and resource sizes, comparing current PR metrics against saved baselines to identify degradations.

What web performance metrics can I capture for a specific URL?▼

For a specific URL, you can capture TTFB, FCP, LCP, DOM timings, resource sizes, and bundle metrics. Running a quick audit collects these navigation timing and resource metrics via the browse daemon for comprehensive analysis.

How do I track web performance trends over time?▼

Track web performance trends by saving structured reports to .gstack/benchmark-reports over time. This allows you to analyze historical navigation timing and resource metrics data to monitor performance improvements or degradations.

Does benchmarking pages require any external dependencies?▼

Benchmarking pages requires no external dependencies. The skill operates independently using the browse daemon to collect TTFB, FCP, LCP, DOM timings, and resource sizes, saving all structured reports internally.

Can I analyze multiple pages in a single performance audit?▼

You can analyze multiple pages in a single performance audit using page lists. The skill supports multi-page analysis, capturing navigation timing and resource metrics across all specified pages for comprehensive comparison.

Where are web performance benchmark reports stored?▼

Web performance benchmark reports are saved as structured data to .gstack/benchmark-reports. This storage format enables baseline comparisons, trend analysis, and regression detection across branches and PRs.