benchmark

Collect navigation and resource timing metrics with the browse daemon for baseline comparisons.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Baseline-driven performance regression detection to identify and track changes across PRs using the browse daemon.

Core Features & Use Cases

  • Baseline capture for pages and branches.
  • Automated collection of TTFB, FCP, LCP, and other metrics with resource analysis.
  • Comparison against baselines with regression/warning classification and trend analysis.

Quick Start

Run the benchmark on a URL to collect metrics, save a baseline, and compare current performance against it.

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 continuous integration workflows?

You can detect performance regressions by capturing baseline metrics for pages and comparing pull request results against them. This process classifies regressions or warnings across multi-page sites within continuous integration workflows.

Can I measure real user web vitals like LCP and FCP using resource timing data?

Yes, you measure web vitals by collecting navigation and resource timing data with the browse daemon. This enforces deterministic metrics including TTFB, FCP, LCP, and DOM timings for accurate page load analysis.

What is the best way to track page load trends and set baselines for multi-page sites?

The best way to track page load trends is to capture baselines and persist them to .gstack/benchmark-reports. This enables automated trend analysis and auditing of performance changes over time across multi-page sites.

Do I need the browse daemon to collect TTFB and DOM timings for automated comparisons?

Yes, the browse daemon is required to collect navigation and resource timing data for TTFB and DOM timings. This data is then used for baseline capture, PR-time comparisons, and trend analysis across branches.