benchmark

Measure real-browser performance by collecting navigation and resource metrics for target URLs.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ClyptAI/Clypt-Backend --skill benchmark-clyptai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/ClyptAI/Clypt-Backend/tree/main/.agents/skills/gstack/benchmark
Command: npx skills add https://github.com/ClyptAI/Clypt-Backend --skill benchmark-clyptai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions in web apps are hard to spot. This skill automates measurement by collecting browser metrics to reveal slowdowns and provide actionable baselines.

Core Features & Use Cases

  • Baseline capture and comparison across PRs and branches.
  • Diff analysis focusing on changed pages.
  • Trend viewing across historical runs.
  • Generated reports stored under .gstack/benchmark-reports.

Quick Start

Run /benchmark on a URL to perform a full performance audit and compare it to your baseline.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I measure web performance and establish a baseline for my URLs?

To measure web performance, the Skill collects real-browser navigation and resource metrics for target URLs to establish a structured JSON baseline. This baseline is stored for subsequent comparisons.

What is the best way to compare web performance across different branches or PRs?

Comparing web performance across PRs is handled through diff analysis against a saved baseline. This focuses specifically on changed pages to quickly reveal performance regressions.

Can I view web performance trends across multiple historical runs?

Yes, you can view web performance trends across multiple historical runs. The Skill tracks historical metrics to visualize performance shifts over time.

How do I generate and store per-page performance reports?

Per-page performance reports are generated automatically after auditing target URLs. These reports are written and stored as files under the .gstack/benchmark-reports directory.

Does web performance benchmarking require any external dependencies?

Web performance benchmarking requires no external dependencies to run. It relies on a real-browser environment to collect navigation and resource metrics for target URLs.

Why are my web app performance regressions hard to spot during development?

Performance regressions are hard to spot without automated measurement. The Skill solves this by collecting browser metrics to reveal slowdowns and provide actionable baselines.