# W Perf

> Measure bottlenecks with repository tools, then recommend or apply evidenced optimizations.

- Skill: `blockmatic/w-perf` (Agent Skill)
- Install (CLI): `npx get-skill add blockmatic/w-perf`
- Raw SKILL.md: https://api.skillmd.com/api/skills/blockmatic/w-perf/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: blockmatic (https://skillmd.com/u/blockmatic)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/blockmatic/w-perf

---


Find performance issues with a measured baseline. Do not invent SLOs or impact percentages. Report-only unless the user asked to implement.

1. Read testing docs for budgets if present. Capture a baseline with the repo profiler, traces, tests, or `gh` job timing — not estimates.
2. Locate the owning hot path (query, render, allocation) with that evidence.
3. Recommend the smallest change. Implement only when authorized. Re-measure after a change.
4. If a new budget is required, document it in existing testing docs instead of inventing an SLO here.
5. Docs: `/w-docs` if behavior or commands changed.

