benchmark

Measure web performance metrics and compare results to baselines in PR workflows.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/vib795/copilot-anatomy --skill benchmark-vib795
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/vib795/copilot-anatomy/tree/main/.github/skills/gstack-benchmark
Command: npx skills add https://github.com/vib795/copilot-anatomy --skill benchmark-vib795

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams detect web performance regressions by measuring metrics, establishing baselines, and surfacing deviations in PRs.

Core Features & Use Cases

  • Baseline creation and comparison across pages and routes
  • Trend analysis over historical data to reveal slowdowns
  • Page and resource level insights to guide optimizations

Quick Start

Run a performance audit with a URL using /benchmark.

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 pull requests?

The Skill detects web performance regressions by measuring current web performance metrics and comparing them against stored baselines. It applies directly to PR workflows and uses --diff mode to surface deviations.

How does trend analysis work for web performance metrics?

Trend analysis works by compiling historical web performance data stored under .gstack/benchmark-reports. You can use the --trend mode to reveal slowdowns and analyze page-level insights over time.

What do I need to run a performance audit on a specific page?

To run a performance audit on a specific page, you need the browse daemon and navigation timing APIs. You can start an audit by providing a URL to the benchmark command.

Can I establish baselines for different web routes and compare them?

Yes, you can establish baselines for different web routes and compare them. The Skill stores baselines under .gstack/benchmark-reports to support comparisons across pages and routes.

Does this approach work with standard web-vitals measurement techniques?

Yes, it works with standard web-vitals measurement techniques by utilizing navigation timing APIs. This allows you to capture page and resource level insights to guide optimizations.