Benchmark

Spins up performance measurements across pages, APIs, and builds, then tracks them in .ecc/benchmarks so your team shares baselines. You run it before and after a PR to catch regressions, or when someone says "it feels slow" and you need numbers. It'll measure Core Web Vitals, API latency percentiles, build times, bundle sizes, the works. The before/after comparison mode is the real draw here: it shows you exactly what got faster or slower in a table with deltas. Honest take: most teams skip this until performance is already a problem. Running it in CI from day one means you never have to guess which commit made the homepage load like molasses.

skills.sh installs: 4K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill benchmark --agent claude-code

Installs into .claude/skills of the current project.

Files

Benchmark — Performance Baseline & Regression Detection

When to Use

Before and after a PR to measure performance impact
Setting up performance baselines for a project
When users report "it feels slow"
Before a launch — ensure you meet performance targets
Comparing your stack against alternatives

How It Works

Mode 1: Page Performance

Measures real browser metrics via browser MCP:

1. Navigate to each target URL
2. Measure Core Web Vitals:
   - LCP (Largest Contentful Paint) — target < 2.5s
   - CLS (Cumulative Layout Shift) — target < 0.1
   - INP (Interaction to Next Paint) — target < 200ms
   - FCP (First Contentful Paint) — target < 1.8s
   - TTFB (Time to First Byte) — target < 800ms
3. Measure resource sizes:
   - Total page weight (target < 1MB)
   - JS bundle size (target < 200KB gzipped)
   - CSS size
   - Image weight
   - Third-party script weight
4. Count network requests
5. Check for render-blocking resources