perf-profiler
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
Best use case
perf-profiler is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
Teams using perf-profiler should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/perf-profiler/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How perf-profiler Compares
| Feature / Agent | perf-profiler | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# perf-profiler
Run profiling tools and capture hotspots with evidence.
Follow `docs/perf-requirements.md` as the canonical contract.
## Parse Arguments
```javascript
const args = '$ARGUMENTS'.split(' ').filter(Boolean);
const tool = args[0] || '';
const command = args.slice(1).join(' ');
```
## 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.Related Skills
perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
perf-benchmarker
Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.
perf-analyzer
Use when synthesizing perf findings into evidence-backed recommendations and decisions.
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.
perf-baseline-manager
Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.
perf-investigation-logger
Use when appending structured perf investigation notes and evidence.
perf-theory-tester
Use when running controlled perf experiments to validate hypotheses.
drift-analysis
Use when the user asks about plan drift, reality check, comparing docs to code, project state analysis, roadmap alignment, implementation gaps, or needs guidance on identifying discrepancies between documented plans and actual implementation state.
enhance-agent-prompts
Use when improving agent prompts, frontmatter, and tool restrictions.
learn
Research any topic online and create learning guides. Use when user asks to 'learn about', 'research topic', 'create learning guide', 'build knowledge base', or 'study subject'.
enhance-hooks
Use when reviewing hooks for safety, timeouts, and correct frontmatter.
enhance-plugins
Use when analyzing plugin structures, MCP tools, and plugin security patterns.