benchmark

Measures web, API, and build performance baselines and detects regressions across pull requests.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill benchmark-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/benchmark
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill benchmark-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often ship changes without knowing their performance impact, discovering slowdowns only after users complain. This Skill establishes measurable performance baselines and compares metrics before and after changes so regressions are caught before release. ## Core Features & Use Cases - Page Performance Measurement: Captures Core Web Vitals (LCP, CLS, INP, FCP, TTFB), resource sizes, request counts, and render-blocking resources via browser automation. - API and Build Benchmarking: Measures p50/p95/p99 endpoint latency under concurrency, plus cold build, hot reload, test, type-check, and lint durations. - Before/After Comparison: Saves a baseline, then compares post-change metrics in a delta table with BETTER/WARN verdicts. - Use Case: Before merging a PR that adds a new dependency, run a baseline, apply the change, then compare to see that bundle size grew by 40KB and LCP regressed by 300ms. ## Quick Start Ask the AI to run a performance baseline on your key pages and API endpoints, then compare the results after your next change.

Frequently Asked Questions about benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I measure Core Web Vitals for my web pages?▼

Navigate to each target URL in a real browser and record LCP, CLS, INP, FCP, and TTFB against standard targets such as LCP under 2.5s and CLS under 0.1. Also track page weight, JS bundle size, and render-blocking resources.

How to benchmark API endpoint latency under load?▼

Hit each endpoint 100 times and record p50, p95, and p99 latency along with response sizes and status codes. Then test with 10 concurrent requests and compare the results against your SLA targets.

How do I detect performance regressions in a pull request?▼

Save a baseline of current metrics before making changes, then run a comparison after the change. The output is a delta table showing before, after, and verdict (BETTER or WARN) for each metric, which can run in CI on every PR.

What build performance metrics should I track?▼

Track cold build time, hot reload (HMR) time, test suite duration, TypeScript check time, lint time, and Docker build time. These metrics quantify the development feedback loop and reveal tooling regressions.

Where are performance baselines stored and shared?▼

Baselines are stored as JSON files in the .ecc/benchmarks/ directory. Because they are git-tracked, the whole team shares the same baselines and can compare results consistently across machines and CI.