benchmark

Name: benchmark
Availability: InStock
Author: geoffreywoo

Analyze web page performance metrics to detect regressions across PR changes.

1|Updated Feb 27, 2026

Search Tags:#performance #metrics #regression #benchmark #ci #web-performance

Ready to run

npx skills add https://github.com/geoffreywoo/clawfable --skill benchmark-geoffreywoo

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams baseline, measure, and detect web performance regressions across PR changes using a browser-based performance daemon. It centralizes data collection, comparison against historical baselines, and reporting to keep performance at the forefront of CI.

Core Features & Use Cases

Baseline capture and comparison across builds to identify regressions.
CI-ready workflow for PR validation with per-page metrics like TTFB, FCP, LCP, and DOM timings.
Resource and bundle-size analysis to surface heavy scripts and assets.
Trend analysis across historical baselines to reveal gradual degradation and opportunities for optimization.
Output reports (JSON/Markdown) stored under .gstack/benchmark-reports for auditability.

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 web performance regressions in CI across PR changes?▼

You can detect web performance regressions by running a performance audit on modified pages to compare current metrics against historical baselines. This CI-ready workflow analyzes TTFB, FCP, LCP, and DOM timings to surface degradations before merging.

What web performance metrics are captured during a baseline comparison?▼

The performance baseline comparison captures per-page metrics including TTFB, FCP, LCP, and DOM timings. It also collects navigation and resource entries to analyze bundle sizes and identify heavy scripts or assets.

Can I analyze bundle sizes and resource loading for web pages?▼

Yes, you can analyze bundle sizes and resource loading by collecting resource entries during a browser-based performance audit. This process surfaces heavy scripts and assets that may cause performance degradation.

Do I need a browse daemon to run performance audits on modified pages?▼

Yes, the browse daemon is required to execute performance audits and collect navigation and resource entries. It operates as the browser-based performance daemon for gathering baseline JSON data and generating Markdown reports.

How do I track web performance trends across historical builds?▼

You can track web performance trends by capturing baselines across builds and comparing them over time. This trend analysis reveals gradual degradation and highlights opportunities for optimization in metrics like LCP and bundle sizes.

Where are web performance audit reports stored for CI checks?▼

Web performance audit reports are stored as JSON and Markdown files under the .gstack/benchmark-reports directory. This output structure ensures auditability and historical tracking for CI baseline comparisons.