benchmark

Other Community v1.0.0

Skill notes

When to invoke this skill

Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time".

First-run guidance (one-time)

If ACTIVATED is no (first skill run on this machine) AND the preamble printed a non-empty FIRST_TASK: value that is NOT nongit: show ONE short, project-specific line mapped from the token, as a heads-up, then CONTINUE with whatever the user actually asked — do NOT halt their task.

Voice

Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides.

Completion Status Protocol

When completing a skill workflow, report status using one of: DONE — completed with evidence. DONE_WITH_CONCERNS — completed, but list concerns. BLOCKED — cannot proceed; state blocker and what was tried. NEEDS_CONTEXT — missing info; state exactly what is needed.

Operational Self-Improvement

Before completing, review the session for durable learnings and log each one — this step ALWAYS runs, it is not conditional on something feeling noteworthy (#2402: 43 of 44 learnings came from explicit /learn because "if you discovered" read as optional). A durable learning is a project quirk, command fix, pitfall, or pattern that would save 5+ minutes in a future session. If

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@garrytan · v1.0.0 · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Bun
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Setup

Phase 1: Setup

02
Phase 2: Page Discovery

Same as /canary — auto-discover from navigation or use `--pages`. If `--diff` mode:

03
Phase 3: Performance Data Collection

For each page, collect comprehensive performance metrics: Then gather detailed metrics via JavaScript: Extract key metrics: TTFB (Time to First Byte): `responseStart - requestStart` FCP (First Contentful Paint): from PerformanceObserver or `paint` entries

04
Phase 4: Baseline Capture (--baseline mode)

Save metrics to baseline file: Write to `.gstack/benchmark-reports/baselines/baseline.json`.

05
Phase 5: Comparison

If baseline exists, compare current metrics against it: Regression thresholds: Timing metrics: >50% increase OR >500ms absolute increase = REGRESSION Timing metrics: >20% increase = WARNING Bundle size: >25% increase = REGRESSION

06
Phase 6: Slowest Resources

Phase 6: Slowest Resources

07
Phase 7: Performance Budget

Check against industry budgets:

08
Phase 8: Trend Analysis (--trend mode)

Load historical baseline files and show trends:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.