benchmark

Measure performance baselines and detect regressions across web pages, APIs, and builds.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill benchmark-zescode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/ZESCODE/Zes-Orchestration-System/tree/main/.agents/skills/benchmark
Command: npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill benchmark-zescode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of visibility into performance regressions during the development lifecycle, ensuring that code changes do not negatively impact user experience or system efficiency.

Core Features & Use Cases

  • Performance Baselines: Establish and track metrics for page load, API latency, and build times.
  • Regression Detection: Automatically compare current performance against saved baselines to identify slowdowns before deployment.
  • Use Case: Run a benchmark comparison before and after a major refactor to ensure that the new code meets Core Web Vitals targets and maintains build speed.

Quick Start

Use the benchmark skill to compare the current system performance against the saved baseline.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I detect performance regressions before deploying code changes?

To detect performance regressions, you can compare current system metrics against saved baselines for page load, API latency, and build times. This comparative analysis identifies slowdowns before deployment.

How do I measure API latency and build times against a performance baseline?

You measure API latency and build times by establishing a performance baseline using local storage for baseline JSON tracking. This allows you to track metrics and compare current system performance against the saved data.

Does benchmarking web pages require integration with browser MCP tools?

Yes, measuring performance baselines for web pages requires integration with browser MCP tools. This integration facilitates tracking Core Web Vitals and detecting regressions across page loads.

What is the best way to ensure code changes do not negatively impact Core Web Vitals?

The best way to ensure code changes do not impact Core Web Vitals is to run a benchmark comparison before and after a major refactor. This verifies that the new code maintains performance targets.

Can I track performance baselines using local storage?

Yes, you can track performance baselines using local storage for baseline JSON tracking. This approach facilitates comparative analysis of system metrics before and after code changes to ensure performance targets are met.