benchmark

Measure web and API performance metrics and save git-tracked baselines.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/samymity/node-poc --skill benchmark-samymity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/samymity/node-poc/tree/main/.claude/skills/benchmark
Command: npx skills add https://github.com/samymity/node-poc --skill benchmark-samymity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common pain point of undetected performance regressions reaching production, and the lack of consistent, shareable performance baselines across development teams, which makes it difficult to enforce performance standards or diagnose speed issues proactively.

Core Features & Use Cases

  • Multi-Mode Performance Testing: Supports 4 core testing workflows: page performance (Core Web Vitals, resource sizes, network request analysis), API performance (latency percentile measurement, load testing), build performance (build time, HMR speed, test suite duration tracking), and before/after change comparison.
  • Shared Baseline Tracking: Saves performance metrics to a git-tracked directory so entire teams can reference consistent performance targets and automatically flag regressions between versions.
  • Use Case: Run this Skill before merging a PR that modifies critical user paths to verify no performance regressions were introduced, or before a product launch to confirm all performance SLA targets are met.

Quick Start

Use the benchmark skill to measure your application's current page load performance and save the results as a shared baseline for future regression checks.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I catch performance regressions before merging a pull request?

Core Web Vitals monitoring tracks page load performance metrics like resource sizes and network requests to establish shared performance baselines. These git-tracked baselines allow teams to enforce performance standards and automatically flag regressions between versions.

How do I track API latency percentiles for SLA compliance verification?

API benchmarking measures latency percentiles and conducts load testing to verify SLA compliance before product launches. Results are saved to a git-tracked directory so entire teams can reference consistent performance targets and automatically flag regressions.

What is the best way to establish shareable performance baselines for a web application?

The best way to establish shareable performance baselines is to measure page performance and save the results to a git-tracked directory. This allows entire development teams to reference consistent targets and automatically flag regressions between versions.

Can I measure build performance and HMR speed alongside page load metrics?

Build performance tracking measures build time, HMR speed, and test suite duration to detect regressions in the development workflow. It operates alongside page performance and API benchmarking to provide comprehensive regression detection across multiple testing modes.

Does this performance testing approach work for post-change impact measurement?

Yes, this performance testing approach supports post-change impact measurement through before and after change comparison workflows. It validates pre-PR changes, checks launch readiness, and verifies SLA compliance by comparing current metrics against git-tracked baselines.