Perf Profiler
- 2 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/awesome-slash
perf-profiler is a skill that runs profiling tools to capture CPU and memory hot paths, flame graphs, and file:line hotspot evidence.
About
This skill runs profiling tools to capture CPU and memory hot paths with concrete evidence. A developer uses it to find hotspots, generate flame graphs, and capture JFR or perf output tied to a specific scenario. It verifies debug symbols first, records file and line for each hotspot, and keeps outputs minimal and evidence-backed.
- Profiles CPU and memory hot paths and captures hotspot evidence
- Generates flame graphs or JFR/perf artifacts with file:line hotspots
- Verifies debug symbols before profiling and requires a clear scenario
Perf Profiler by the numbers
- 2 all-time installs (skills.sh)
- Ranked #467 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
perf-profiler capabilities & compatibility
- Capabilities
- profiling · flame graph generation · hotspot analysis · debugging
- Use cases
- debugging · data analysis
What perf-profiler says it does
Run profiling tools and capture hotspots with evidence.
Verify debug symbols before profiling.
No profiling without a clear scenario.
npx skills add https://github.com/avifenesh/awesome-slash --skill perf-profilerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/awesome-slash ↗ |
What it does
Profile CPU or memory hot paths for a scenario and capture flame graphs and file:line hotspot evidence.
Who is it for?
Developers who need to locate CPU or memory hotspots with flame graphs and precise file:line evidence.
Skip if: Profiling without a clear scenario, which the skill explicitly forbids.
When should I use this skill?
You are profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
What you get
Flame graphs and hotspot listings with file:line and captured profiling artifacts.
- flame graph artifact
- hotspot file:line list
By the numbers
- captures file:line per hotspot
Files
perf-profiler
Run profiling tools and capture hotspots with evidence.
Follow docs/perf-requirements.md as the canonical contract.
Parse Arguments
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
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512FAQ
What must happen before profiling?
Debug symbols must be verified, and there must be a clear scenario to profile.
What evidence does it capture?
File and line for hotspots plus a flame graph or equivalent profiling artifact.