benchmark

Collect per-page timing metrics via the browse daemon to identify performance regressions.

107|19|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mr-daedalium/ostack --skill benchmark-mr-daedalium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/mr-daedalium/ostack/tree/main/benchmark
Command: npx skills add https://github.com/mr-daedalium/ostack --skill benchmark-mr-daedalium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance engineers need a reliable way to detect regression across PR changes by measuring run-time metrics and storing baselines for comparison.

Core Features & Use Cases

  • Baseline capture for pages and PR changes to establish historical performance.
  • Per-page timing metrics (TTFB, FCP, LCP, DOM Interactive, DOM Complete, Full Load) and resource analysis.
  • Trend reporting and regression alerts to guide optimization.

Quick Start

Run a full performance audit against a URL to generate baseline-ready reports.

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 across PR changes?

Detect web performance regressions by collecting runtime metrics via the browse daemon, storing baselines, and comparing per-page timings against historical data to identify and quantify drops in speed.

What web vitals do I need to capture for a performance baseline?

A performance baseline requires capturing key web vitals like TTFB, FCP, LCP, DOM Interactive, DOM Complete, and Full Load times per page to establish a historical reference for future comparisons.

Can I run a web vitals performance audit without external dependencies?

Yes, you can run a web vitals performance audit without external dependencies, relying solely on the browse daemon to collect metrics and output JSON reports directly into your local .ostack directory.

How do I generate trend reports for page load metrics across deployments?

Generate trend reports for page load metrics by analyzing stored baselines and per-page JSON outputs across multiple URLs and deployments, allowing you to visualize performance history and trigger regression alerts.

What is the best way to track LCP and FCP regressions for specific URLs?

Track LCP and FCP regressions for specific URLs by capturing initial baseline metrics, then collecting per-page timing data on subsequent visits or PR changes to quantify any degradation.

Where are performance baseline metrics stored for regression analysis?

Performance baseline metrics for regression analysis are stored as JSON files and baseline outputs within the .ostack/benchmark-reports directory, ensuring historical data is preserved for trend reporting.