gstack-benchmark

Detects web performance regressions by comparing page metrics against captured baselines.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill gstack-benchmark-tayiorbeii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-benchmark
Source: https://github.com/tayiorbeii/paperclip-factory-kit-hermes/tree/main/skills/paperclip/gstack-benchmark
Command: npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill gstack-benchmark-tayiorbeii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web applications slow down gradually as each pull request adds milliseconds and kilobytes, and without baselines nobody notices until the app feels sluggish. This Skill measures real page performance, compares it against saved baselines, and flags regressions before they ship. ## Core Features & Use Cases - Baseline Capture and Comparison: Record TTFB, FCP, LCP, DOM timings, transfer sizes, and request counts per page, then diff current metrics against the baseline with regression thresholds. - Resource and Bundle Analysis: Identify the slowest and largest resources, track JS and CSS bundle sizes, and check results against industry performance budgets. - Trend Tracking: Store historical benchmark reports and visualize performance trends over time to catch gradual degradation. - Use Case: Before merging a PR, run a benchmark against your staging URL to discover that LCP doubled and the JS bundle grew 60%, then pinpoint the offending resources. ## Quick Start Ask the agent to run a performance benchmark on your staging URL and compare it against the saved baseline to detect regressions.

Frequently Asked Questions about gstack-benchmark

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

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

Capture a baseline with the --baseline flag before making changes, then run the benchmark again on your branch. The skill compares TTFB, FCP, LCP, bundle sizes, and request counts against the baseline and flags regressions using relative thresholds.

What metrics does a web performance benchmark measure?▼

It measures TTFB, First Contentful Paint, Largest Contentful Paint, DOM Interactive, DOM Complete, full load time, total requests, transfer size, and JS/CSS bundle sizes. Data comes from the browser Performance API via the browse daemon.

Can I benchmark only the pages affected by my branch?▼

Yes, the --diff mode uses git diff against the base branch to identify changed files and benchmarks only the affected pages. You can also specify pages explicitly with the --pages flag.

What counts as a performance regression in the report?▼

Timing metrics regress when they increase more than 50% or 500ms absolutely; bundle sizes regress above 25% growth. Smaller increases (20% timing, 10% bundle, 30% request count) are flagged as warnings rather than regressions.

Does the benchmark tool modify my code to fix performance issues?▼

No, the skill is read-only. It produces a report with recommendations such as code-splitting or lazy loading, but it does not modify code unless you explicitly ask for changes afterward.