Performance Benchmark captures page performance metrics (TTFB, FCP, LCP, DOM timings, resource sizes), stores baselines, compares current runs against baselines, and generates regression reports with actionable recommendations. It supports per-page audits, diff-based runs for PRs, trend analysis, and performance budgets.
Use this skill when you want to: capture a baseline before a large change, validate that a PR doesn't regress Core Web Vitals, run quick timing checks, or produce trend reports across historical runs. Common triggers include manual audits, CI checks on PRs, and periodic performance monitoring.
Likely compatible with Claude Code / browse daemon based agents and CLI-driven automation (benchmarks rely on the browse daemon and shell tools).
Performance regression detection skill for the gstack ecosystem. Uses a browse daemon to collect Core Web Vitals, TTFB, bundle sizes, and resource timing from live pages, then compares against saved baselines. Well-documented 9-phase workflow with concrete metric collection commands and clear regression thresholds. However, it's a .tmpl template with unresolved placeholders ({{PREAMBLE}}, {{BROWSE_SETUP}}) and depends entirely on the gstack browse daemon ($B) and gstack-slug binary, making it unusable outside that ecosystem.
gstack browse daemon ($B)gstack-slug binary (~/.claude/skills/gstack/bin/gstack-slug)Solid conceptual design for performance benchmarking. The template approach limits portability. No security concerns beyond mild shell eval risk from gstack-slug binary.