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
- browser MCP for page metrics (API and build modes work without it).
- Level
- Beginner — browser MCP for page metrics (API and build modes…
- 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:
Quick answer
Benchmark, Performance Baseline and Regression Detection is a free Muse skill that measures performance baselines before and after a pull request, storing before and after comparisons in git-tracked JSON. It covers browser Core Web Vitals, API latency percentiles and build times, plus page weight, resource sizes, network counts and render-blocking resources, to detect regressions early.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 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://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/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.
🔒 Security, provenance and what this touches
- It can run commands on your Muse’s computer.
What the scan found — excerpts from the install prompt
- runs commands — 3. Run the baseline with Muse, then compare after changes; results land in git-tracked .ecc/benchmarks JSON.
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : runs commands
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.