benchmark

Detect performance regressions by comparing page load timings and resource metrics.

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

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.

Core Features & Use Cases

  • Auto-baseline creation and comparison across PRs
  • Per-page timing metrics (TTFB, FCP, LCP, DOM timings) with resource analysis
  • Trend analysis and baseline reporting for long-running projects

Quick Start

Invoke /benchmark with a URL to run a full baseline-enabled performance audit.

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?

Detect performance regressions by comparing before and after page load timings on every pull request. The benchmark process establishes a baseline for Core Web Vitals and resource metrics, then outputs an automated comparison to guide improvements.

How do I establish a baseline for Core Web Vitals like LCP and FCP?

Establish a Core Web Vitals baseline by collecting per-page metrics including TTFB, FCP, LCP, and DOM timings. Running a baseline-enabled performance audit against a URL records these initial measurements for future trend analysis and comparison.

Can I track page load timings and resource metrics for long-running projects?

Track page load timings and resource metrics for long-running projects through ongoing trend analysis. The system continuously collects per-page timing data and compares it against established baselines to identify performance shifts across pages over time.

What is the best way to automate performance reporting across pages?

Automate performance reporting by invoking a baseline-enabled audit that collects resource breakdowns and page timings. The system applies this to PR workflows to generate automated comparison outputs, detecting regressions and guiding improvements without manual intervention.

Does benchmarking web vitals require specific dependencies or environments?

Benchmarking web vitals requires a browse daemon to collect page load timings and resource metrics. No additional dependencies are needed, but the environment must support collecting per-page metrics like TTFB, FCP, and LCP for baseline creation and comparison.