benchmark

Compare baseline and current performance data to detect regressions across PRs.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/deveshkumars/Intentra --skill benchmark-deveshkumars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/deveshkumars/Intentra/tree/main/benchmark
Command: npx skills add https://github.com/deveshkumars/Intentra --skill benchmark-deveshkumars

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

  • Baseline capture and comparison across PRs to identify regressions.
  • Trend analysis over historical runs and per-page metrics like TTFB, FCP, LCP, and bundle sizes.
  • Automated reporting with actionable recommendations and persistence of baselines in the repo.

Quick Start

Run /benchmark <url> to start a 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 performance regressions in Core Web Vitals across pull requests?

You can detect performance regressions by capturing baseline metrics with the browse daemon and JavaScript performance APIs, then comparing current PR runs against those baselines to identify shifts in TTFB, FCP, LCP, and bundle size.

What is the best way to track bundle size and LCP trends over time in my repository?

The best way to track bundle size and LCP trends is by saving baseline performance data directly in your repository, enabling historical trend analysis and per-page metric comparisons across multiple runs over time.

How do I establish a performance baseline for page load times before deploying changes?

Establish a page load time baseline by running a performance audit on your target URL, capturing initial TTFB, DOM Interactive, DOM Complete, and resource sizes to persist in your repository for future PR comparisons.

Can I compare current performance metrics against a saved baseline for specific routes?

Yes, you can compare current performance metrics against saved baselines for specific pages or routes by applying the browse daemon to collect current data and generating an actionable regression report.

Do I need external dependencies to measure DOM Complete and TTFB for regression reporting?

No external dependencies are required to measure DOM Complete and TTFB, as regression reporting leverages the built-in browse daemon and standard JavaScript performance APIs to collect and compare page metrics.