
Perf Profiler
When you need to find out why your service is pegging CPU or leaking memory, this skill runs perf, JFR, or similar profilers and generates flame graphs as evidence. It enforces a contract: verify debug symbols first, capture file and line numbers for every hotspot, and output artifacts you can actually inspect. The skill won't let you profile without a clear scenario, which is good discipline. It's built around a minimal output format that lists the tool, command, hotspots with reasons, and paths to the flame graph or profile data. If you're doing performance work and want Claude to drive the profiler instead of fumbling through man pages, this gives you a structured way to do it.
- GitHub stars
- 1.7K
- last updated
- May 1, 2026
Install
$ npx -y skills add composiohq/awesome-claude-plugins --skill perf-profiler --agent claude-codeInstalls into .claude/skills of the current project.
Files
perf-profiler
Run profiling tools and capture hotspots with evidence.
Follow docs/perf-requirements.md as the canonical contract.
Required Rules
- Verify debug symbols before profiling.
- Capture file:line for hotspots.
- Provide flame graph or equivalent output when possible.
Output Format
tool: <profiler>
command: <command>
hotspots:
- file:line - reason
artifacts:
- <path to flame graph or profile>
Constraints
- No profiling without a clear scenario.
- Keep outputs minimal and evidence-backed.
Sponsors
Details
- Repository
- github.com/composiohq/awesome-claude-plugins
- Category
- Debugging
- First seen
- Jun 11, 2026
More from composiohq/awesome-claude-plugins
All 23- Reflecting On Sessions
- Remove Sub
- Senior Frontend
- Theme Factory
- Perf Theory Gatherer
- Perf Theory Tester
- Unpause Subs
- Add Sub
- Perf Analyzer
- Artifacts Builder
- Perf Baseline Manager
- Perf Benchmarker
- Canvas Design
- Changelog Generator
- Perf Code Paths
- Developer Growth Analysis
- Frontend Design
- Help
- Perf Investigation Logger
- List Subs
- Mcp Builder
- Pause Subs