Benchmark, Performance Baseline and Regression Detection
Measure performance baselines before and after a PR: browser Core Web Vitals, API latency percentiles and build times, with before/after comparisons stored in git-tracked JSON.
- What
- Measure performance baselines before and after a PR: browser Core Web Vitals, API latency percentiles and build times, with before/after comparisons stored in git-tracked JSON.
- Cost
- Free
- Needs
- Use "Benchmark, Performance Baseline and Regression Detection" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: measure performance baselines and detect regressions across three modes. Mode 1, page performance, measures real browser metrics via browser MCP: Core Web Vitals (LCP target under 2.5s, CLS under 0.1, INP under 200ms, plus FCP and TTFB), resource sizes (total page weight target under 1MB, JS bundle under 200KB gzipped, CSS, images, third-party scripts), network request counts, and render-blocking resources. Mode 2, API performance, hits each endpoint 100 times and measures p50, p95, p99 latency plus response size and status codes. Mode 3 covers build and test feedback times. Before/after comparisons are stored in git-tracked `.ecc/benchmarks` JSON, so a PR's performance impact is reviewable like code. Use when checking page speed, responding to "it feels slow" reports, verifying launch performance targets, or comparing stack alternatives. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: page metrics need a browser MCP available; synthetic lab numbers are not real-user data, treat them as direction not verdict. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Benchmark, Performance Baseline and Regression Detection" with your Muse. Prerequisites: browser MCP for page metrics (API and build modes work without it). 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/benchmark/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Benchmark [page/endpoint] before and after this PR" or "Set up performance baselines for this project." 3. Run the baseline with Muse, then compare after changes; results land in git-tracked .ecc/benchmarks JSON. Tip: capture the baseline before the PR, not after; a baseline taken on the changed code is just a number. Safety: a skill is plain-text instructions; it runs nothing by itself. Benchmark staging or local URLs, not production endpoints under load.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.