benchmark

Compare web application performance metrics across branches and commits.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/ericdahl-dev/coauthor-cleaner --skill benchmark-ericdahl-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/ericdahl-dev/coauthor-cleaner/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/ericdahl-dev/coauthor-cleaner --skill benchmark-ericdahl-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a robust solution for detecting performance regressions in web applications, ensuring optimal user experience and performance.

Core Features & Use Cases

  • Performance Regression Detection: Monitors and compares performance metrics such as load time, bundle size, and resource usage across different branches or commits.
  • Baseline Comparison: Captures and compares performance metrics against baseline data for accurate regression detection.
  • Custom Page Scanning: Allows specifying specific pages or resources for benchmarking, enhancing focus on critical areas.
  • Use Case: For a web development team looking to maintain high performance standards, this Skill can be used to automatically scan the impact of new features or changes on critical paths like landing pages or API endpoints.

Quick Start

Use the /benchmark https://example.com command to start a performance benchmark for the specified URL.

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 different commits?

To detect web performance regressions, you can monitor and compare performance metrics like load time and bundle size across different branches or commits. This Skill compares current metrics against baseline data to pinpoint regressions automatically.

What web performance metrics can I monitor for regression detection?

For performance regression detection, you can monitor web application load times, bundle sizes, and resource usage. The Skill analyzes these metrics across branches to identify degradations in user experience.

Can I benchmark specific pages or resources instead of the whole application?

Yes, you can specify individual pages or resources for benchmarking. This custom page scanning focuses analysis on critical areas like landing pages or API endpoints rather than the entire web application.

How do I run a performance benchmark on a specific URL?

You run a performance benchmark on a specific URL by executing the benchmark command followed by your target address. The Skill then scans the web application to capture and compare performance metrics.

Do I need to install external dependencies to monitor bundle size and load time?

No external dependencies are required to monitor bundle size and load time. The Skill operates autonomously using standard Bash, Read, Write, and Glob tools to analyze and report performance metrics.

When should I scan for performance regressions in my web application?

You should scan for performance regressions when adding new features or making changes to critical paths. Capturing baseline metrics beforehand allows accurate comparison to detect load time or bundle size degradations.