skills.rest
kunalrawat425
kunalrawat425COMMUNITY
Explore all skills by this author →
GitHub

benchmark

Measure and compare web performance metrics to detect regressions.

Updated Apr 4, 2026
Search Tags:#performance#diff#benchmark#web-vitals#baselines#trend
One-click install
npx skills add https://github.com/kunalrawat425/conductor-playground --skill benchmark-kunalrawat425
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/kunalrawat425/conductor-playground/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/kunalrawat425/conductor-playground --skill benchmark-kunalrawat425

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions creep into PRs; benchmarks establish baselines for load times, Core Web Vitals, and resource sizes, enabling reliable detection.

Core Features & Use Cases

  • Baseline capture per PR and historical trend analysis to surface regressions early.
  • Per-page and overall site metrics collection including TTFB, FCP, LCP, and resource breakdown.
  • Automated comparisons and alert-style reporting to help teams prioritize optimizations.

Quick Start

Run a performance audit on a URL to generate baselines, compare results, and view trend reports.

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

To detect web performance regressions in a pull request, you capture baseline metrics for load times, Core Web Vitals, and resource sizes, then compare new results against these baselines to surface any degradations early.

What is the best way to track Core Web Vitals trends for live URLs?▼

Tracking Core Web Vitals trends for live URLs involves collecting per-page metrics like TTFB, FCP, and LCP over time, generating baseline reports to establish historical trends and identify performance shifts through automated comparisons.

Do I need a browse tool to collect navigation and resource timing data?▼

Yes, you need a browse tool to collect navigation and resource timing data. The benchmark process relies on a browse tool to gather the required web performance metrics for per-page analysis and baseline capture.

How do I generate a performance baseline for pages in my repository?▼

To generate a performance baseline for pages in your repository, run a performance audit on the target URLs to collect metrics, which are then stored as baseline reports in the .gstack/benchmark-reports directory for future diffing.

Can I compare resource breakdowns and load times across multiple pages?▼

Yes, you can compare resource breakdowns and load times across multiple pages. The benchmark process supports per-page and overall site metrics collection, enabling automated comparisons to help prioritize optimizations.

Related Skills

Explore More Software Engineering Skills→
chriswesttchriswestt

benchmark

Measure page performance and detect regressions against saved baselines.

Community
Advanced
bajajvinamrbajajvinamr

benchmark

Measure and compare web performance metrics across pull requests using the browse daemon.

Community
Advanced
jangtrinhjangtrinh

performance-profiling

Run Lighthouse audits on web applications and analyze category scores.

Community
Intermediate
JaykaijackJaykaijack

benchmark

Measure browser performance metrics and compare them to stored baselines.

Community
Advanced