benchmark

Name: benchmark
Availability: InStock
Author: fray-cloud

Detect performance regressions by comparing JS timing data against baselines.

Updated Mar 23, 2026

Search Tags:#performance #reporting #lighthouse #benchmark #web-vitals #baselines #trend-analysis

Ready to run

npx skills add https://github.com/fray-cloud/coin --skill benchmark-fray-cloud

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/fray-cloud/coin/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/fray-cloud/coin --skill benchmark-fray-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers detect performance regressions by baseline benchmarking and comparing current page metrics to historical baselines using the browse daemon and JavaScript timing data.

Core Features & Use Cases

Baseline capture: Save performance metrics for a URL and branch to a baseline file.
Comparison and alerts: Compare current metrics against baseline and surface regressions or warnings.
Trend analysis: Show performance trends from recent benchmarks to guide optimizations.
Resource and bundle insights: Identify slow resources and large bundles to target for improvements.

Quick Start

Run a full performance audit against a URL and compare it to the current baseline.

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 on a pull request?▼

To detect web performance regressions on a pull request, you compare current benchmark metrics against a historical baseline. This surfaces specific regressions and warnings by analyzing browse daemon and JavaScript timing data for the target pages.

What is baseline benchmarking for web vitals?▼

Baseline benchmarking for web vitals is the process of capturing initial performance metrics for a specific URL and branch to establish a baseline file. It enables later comparison to identify slow resources and track performance trends over time.

How do I track web performance trends and identify slow resources?▼

You track web performance trends and identify slow resources by running audits that compare current benchmarks against saved baselines. This structured reporting highlights large bundles and resource bottlenecks to guide your optimizations.

Do I need a baseline.json file to run a performance audit?▼

Yes, you need a baseline.json file to run a performance audit. The comparison requires both a baseline and a current benchmark to generate a structured report exported under .gstack/benchmark-reports.

Can I use browse daemon timing data for production-like pages?▼

Yes, you can use browse daemon timing data for production-like pages. Applying performance benchmarking to these environments allows you to effectively surface resource bottlenecks, trends, and regressions before deployment.