perf-profiler
$
npx mdskill add ComposioHQ/awesome-claude-plugins/perf-profilerRun profilers to capture CPU and memory hotspots with evidence.
- Identifies performance bottlenecks in code execution paths.
- Requires debug symbols and specific profiling scenarios.
- Executes tools to generate flame graphs and evidence files.
- Delivers minimal outputs with file:line locations and artifacts.
SKILL.md
.github/skills/perf-profilerView on GitHub ↗
--- name: perf-profiler description: "Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence." version: 1.0.0 argument-hint: "<tool> <command>" --- # 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.
More from ComposioHQ/awesome-claude-plugins
- add-subSubscribe to a skill event. Adds a subscription that injects context before or after a skill runs. Supports optional conditions at both insert-level (inherited by all subscriptions) and subscription-level (AND-stacked). Conditions include fileExists, gitBranch, envSet, envEquals, fileContains (with optional regex).
- helpShow skill-bus overview, status, and available commands. Quick reference for all skill-bus features.
- list-subsList all active skill-bus subscriptions across global and project scopes, showing merge status, insert-level and subscription-level conditions, effective condition stacking, and what would fire for each skill.
- pause-subsTemporarily disable the skill bus. Quick toggle to stop all subscriptions from firing without removing them.
- perf-analyzer"Use when synthesizing perf findings into evidence-backed recommendations and decisions."
- perf-baseline-manager"Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version."
- 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-code-paths"Use when mapping code paths, entrypoints, and likely hot files before profiling."
- perf-investigation-logger"Use when appending structured perf investigation notes and evidence."
- perf-theory-gatherer"Use when generating performance hypotheses backed by git history and code evidence."