perf-profiler
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
Profile →npx skills add agent-sh/agentsys --skill perf-profiler --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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.
- Parse Arguments
- Required Rules
- Output Format
- Constraints
What does the perf-profiler skill do?
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
How do I install it?
Run `npx skills add agent-sh/agentsys --skill perf-profiler --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agent-sh/agentsys, a repository with 923 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.