outthislife/brooklyn-skills · Archived

perf

>- The general profile-driven perf loop for any language or runtime: baseline, profile, fix the real hot path, re-measure. Use for /perf, "this is slow", or optimization work.

First seen Aug 10, 2026

Installation

$ npx skills add outthislife/brooklyn-skills --skill perf

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from outthislife/brooklyn-skills · top by installs.

npx skills add outthislife/brooklyn-skills

Browse all from outthislife/brooklyn-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 185
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,116 B
  • docs SUMMARY.md 184 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 7 installs

SKILL.md

Perf

The general performance loop. Profiling (CPU profile, flamegraph, memory snapshot, trace) is the usual tool, but the loop is the same regardless of which one fits.

Loop

  1. Reproduce the slow path and capture a baseline number — time, memory, FPS,

request latency, whatever matters here.

  1. Profile to find the real hot path: CPU profile / flamegraph / memory snapshot

/ trace as fits. Reuse the repo's existing profiler; don't build a parallel harness.

  1. Read the profile, not your intuition — fix the actual hot path.
  2. Re-measure. Record before/after in the PR title/description.
  3. Ship in topical commits (pr-update), clean, keep CI green.

Don't

  • Optimize by guess before profiling.
  • Fiddle with the measurement system instead of improving perf.
  • Run a full suite or profile that overwhelms the machine — scope the run.
  • Report gains you didn't measure.