benchmark

Collect timing metrics from running pages to detect performance regressions.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands --skill benchmark-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/cloudofgeorge/AI-hands/tree/main/skills/gstack/benchmark
Command: npx skills add https://github.com/cloudofgeorge/AI-hands --skill benchmark-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions sneak in gradually across PRs and deployments, making it difficult to identify root causes before they impact users.

Core Features & Use Cases

  • Automated data collection of navigation timing metrics and resource data from running pages.
  • Baseline and trend analysis to compare current performance against historical data across branches and deployments.
  • Actionable insights highlighting regressions and hotspots to guide optimization.

Quick Start

Provide a URL to run and generate a regression report that highlights regressions versus baseline.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I detect frontend performance regressions across pull requests?

Capture web-vitals like TTFB, FCP, and LCP by collecting real user-facing performance data from a running page. The browse daemon gathers navigation timing metrics and resource data to measure actual page load behavior.

How do I track web-vitals and resource budgets for a running page?

Capture web-vitals like TTFB, FCP, and LCP by collecting real user-facing performance data from a running page. The browse daemon gathers navigation timing metrics and resource data to measure actual page load behavior.

Does this automated benchmarking approach require external dependencies?

No external dependencies are required to run this automated benchmarking approach. It operates independently to collect navigation timing metrics, resource data, and bundle sizes for baseline and trend analysis.

What is the best way to baseline and trend navigation timing metrics?

The best way to baseline and trend navigation timing metrics is to provide a URL to run and generate a regression report. This compares current performance against historical data across branches to highlight regressions and hotspots.

Can I measure DOM metrics and bundle sizes for a specific URL?

Yes, you can measure DOM metrics and bundle sizes for a specific URL by providing it as input. The tool runs the page, collects real user-facing performance data, and generates a report highlighting regressions versus the baseline.

Why does performance regression detection focus on real user-facing data?

Performance regression detection focuses on real user-facing data because regressions sneak in gradually across deployments. Measuring actual running pages ensures you identify root causes and hotspots before users experience the degradation.