benchmark

Measure baseline-enabled web page performance metrics via the browse daemon.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/amanik/sailor-score-debug --skill benchmark-amanik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/amanik/sailor-score-debug/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/amanik/sailor-score-debug --skill benchmark-amanik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection and benchmarking for web pages using the browse daemon, enabling baselines and PR-level comparisons to prevent slow deployments.

Core Features & Use Cases

  • Baseline capture and historical trend analysis for web performance metrics (TTFB, FCP, LCP, DOM timings) across pages.
  • Per-page resource analysis and automated reporting (Markdown/JSON) for CI, dashboards, and stakeholder reviews.
  • Use Case: Run /benchmark on a URL to compare current performance against a baseline and generate actionable recommendations.

Quick Start

Run a full performance audit for a URL with /benchmark <url> to establish a baseline and compare against it.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I establish a web performance baseline for my web pages?

Establish a web performance baseline by running a performance audit on a URL to collect deterministic navigation and resource metrics via the browse daemon. This captures core web vitals like TTFB, FCP, and LCP into a JSON baseline file for future trend comparison.

How do I detect web performance regressions during PR reviews?

Detect web performance regressions during PR reviews by comparing current page metrics against stored historical baselines. Running a benchmark on the target URL generates a Markdown report highlighting deviations to prevent slow deployments from merging.

Can I automate web vitals reporting for CI dashboards?

You can automate web vitals reporting for CI dashboards by generating JSON and Markdown outputs from your benchmark runs. These formats support automation pipelines, stakeholder reviews, and alerting systems to track ongoing performance budgets.

What is the best way to maintain performance budgets across historical baselines?

Maintain performance budgets by analyzing historical baselines collected from deterministic browse daemon data. Comparing per-page resource analysis and DOM timings against these baselines identifies regressions and helps optimize your ongoing performance thresholds.

Do I need the browse daemon to collect resource timing metrics for my web pages?

Yes, the browse daemon is required to collect deterministic navigation and resource timing metrics for your web pages. It enables the data collection needed to generate actionable performance reports and establish baselines for comparison.

Why does deterministic data collection matter for web performance benchmarking?

Deterministic data collection matters for web performance benchmarking because it ensures consistent, reproducible metric capture. This consistency is required to accurately compare current page performance against historical baselines and identify true regressions.