benchmark

Detects web performance regressions by comparing Core Web Vitals and bundle sizes against baselines.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill benchmark-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/benchmark
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill benchmark-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web applications slow down gradually as each pull request adds small delays and bundle weight, and teams often cannot pinpoint when performance degraded. This Skill measures real page performance, captures baselines, and flags regressions before they reach production. ## Core Features & Use Cases - Baseline Capture & Comparison: Record TTFB, FCP, LCP, DOM timings, transfer sizes, and request counts per page, then compare current metrics against stored baselines with regression thresholds. - Resource & Bundle Analysis: Identify the slowest and largest resources, track JS/CSS bundle growth, and check results against industry performance budgets. - Trend Tracking: Review historical benchmark data to spot gradual performance degradation over time. - Use Case: Before merging a PR, run a benchmark against your staging URL to discover that LCP doubled and the JS bundle grew 60%, then get specific recommendations like code-splitting or deferring third-party scripts. ## Quick Start Ask the AI to run /benchmark against your local dev server URL to audit page performance and compare it with the saved baseline.

Frequently Asked Questions about benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect performance regressions in a pull request?

Capture a baseline with /benchmark <url> --baseline before making changes, then run /benchmark <url> on your branch. The skill compares TTFB, FCP, LCP, bundle sizes, and request counts, flagging regressions above defined thresholds.

How to measure Core Web Vitals like LCP and FCP from the command line?

The skill uses the browse daemon's perf command and JavaScript Performance API entries to extract FCP, LCP, TTFB, and DOM timings from real page loads. Results are reported per page with baseline deltas.

What counts as a performance regression in the benchmark report?

Timing metrics regress when they increase over 50% or by more than 500ms; bundle sizes regress above 25% growth. Smaller increases (20% timing, 10% bundle, 30% request count) are flagged as warnings.

Can I benchmark only the pages affected by my current branch?

Yes, use /benchmark --diff to benchmark only pages affected by the current branch. It diffs against the PR base branch or default branch to determine which pages changed.

Does the benchmark skill modify my application code?

No, the skill is read-only. It measures performance, generates reports in .gstack/benchmark-reports/, and offers recommendations, but never modifies code unless explicitly asked.