Performance Profiling
CPU/memory profiling, identifying bottlenecks, flame graphs, hotspot analysis.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill performance-profilinggit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/debugging/skills/performance-profiling ~/.claude/skills/performance-profilingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Performance Profiling Finding where code spends time and memory. ## Context You are profiling code to find bottlenecks. Use CPU and memory profilers. ## Domain Context - **CPU Profiling**: Where does code spend time? Stack sampling at regular intervals - **Memory Profiling**: What allocates memory? Which objects aren't freed? - **Flame Graph**: Visual representation; width = time, stacked = call stack - **Hot Spots**: Functions consuming > 1% of time - **Allocation Profiling**: Which code allocates the most objects? ## Instructions 1. **Start Profiler**: CPU profiler (perf, pprof, Java Flight Recorder) 2. **Run Under Load**: Profile should see realistic workload 3. **Collect Data**: Run for 10-30 seconds; enough to gather signal 4. **Analyze Output**: Flame graph or profiler GUI 5. **Identify Hot Spots**: Functions consuming most time 6. **Drill Down**: Zoom into hot functions; what calls them? 7. **Measure Impact**: Change code, re-profile, compare ## Anti-Patterns - Profiling single-threaded code then deploying multi-threaded; lock contention changes profiles - Optimizing without profiling; "optimization" is just guessing - Micro-optimizing non-hotspot code; spend time on the hottest functions - Not considering cache effects; CPU cache profilers show real impact - Benchmarking without warm-up; first runs hit different code paths ## Further Reading - Brendan Gregg, _Systems Performance_ and _Flame Graphs_ - Java Flight Recorder documentation (Java)
Details
- Skill name
performance-profiling- Repository
- sethdford/claude-skills
- Path
engineer/debugging/skills/performance-profiling/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Performance Profiling skill do?
CPU/memory profiling, identifying bottlenecks, flame graphs, hotspot analysis.
How do I install the Performance Profiling skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Performance Profiling popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Release Notes
48sethdford/claude-skills
Launch and go-to-market skill for product managers.
Memory Leak Detection
48sethdford/claude-skills
Detecting memory leaks through heap dumps, retention analysis, and reference tracing.
Team Workflow
48sethdford/claude-skills
Design team workflows covering task management, collaboration rituals, and tooling.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.