benchmark

Name: benchmark
Availability: InStock
Author: concept2cure

Baseline web performance, compare PR changes, and alert on regressions.

1|Updated Nov 13, 2025

Search Tags:#performance #benchmark #web-vitals #baselines #browser-daemon #trend-analysis #load-time

Ready to run

npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill benchmark-concept2cure

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a repeatable framework to measure, baseline, and compare web performance across PRs, enabling early detection of regressions and data-driven optimization.

Core Features & Use Cases

Automated baseline capture: Create and store historical performance baselines for pages and metrics.
Regression detection: Compare current runs against baselines and flag regressions with per-metric detail.
Trend analysis & reporting: Generate trend charts and summary reports for teams, including per-page and resource insights.

Quick Start

Run the benchmark against a URL to capture and compare performance data.

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 pull requests?▼

To detect web performance regressions in pull requests, you can capture a baseline and compare current runs against it to flag per-metric regressions using the browser daemon. This allows early detection of load time and Core Web Vitals changes.

How does baseline performance trend analysis work for web apps?▼

Baseline performance trend analysis works by capturing historical performance metrics for pages and comparing them across runs to generate trend charts. This reveals per-page and resource insights, helping teams track load time and Core Web Vitals changes over time.

Can I use browser performance entries to monitor Core Web Vitals in CI pipelines?▼

Yes, you can use browser performance entries to monitor Core Web Vitals in CI pipelines. The framework measures load times and resource usage, supporting canary releases and feature flags to ensure data-driven optimization during automated builds.

What's the best way to compare web performance across feature flag deployments?▼

The best way to compare web performance across feature flag deployments is to run diff modes against a stored project baseline file. This approach isolates performance impacts and alerts on regressions for specific metrics like Core Web Vitals and load times.

Do I need a project baseline file to measure load time changes?▼

Yes, you need a local or project baseline file to measure load time changes. The framework requires this baseline to compare current performance entries accessed via the browser daemon, enabling regression detection and trend analysis for web pages.

How do I track Core Web Vitals for multiple pages simultaneously?▼

You can track Core Web Vitals for multiple pages simultaneously by passing a pages array to the benchmark. This captures and compares performance data across all specified URLs, generating per-page insights and alerting on any detected regressions.