Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
avifenesh avatar

Perf Profiler

  • 66 installs
  • 931 repo stars
  • Updated July 26, 2026
  • avifenesh/agentsys

perf-profiler is a Claude Code skill that profiles CPU and memory hot paths, capturing hotspots and flame graphs with evidence.

About

perf-profiler runs profiling tools to capture CPU and memory hot paths with evidence. It verifies debug symbols first, captures file:line for each hotspot, and produces a flame graph or equivalent artifact where possible. A developer uses it to pinpoint exactly where time or memory is being spent during a performance scenario. It refuses to profile without a clear scenario and keeps outputs minimal and evidence-backed.

  • Runs profiling tools to capture CPU/memory hotspots with evidence
  • Generates flame graphs or equivalent output and captures file:line hotspots
  • Verifies debug symbols before profiling

Perf Profiler by the numbers

  • 66 all-time installs (skills.sh)
  • Ranked #269 of 596 Debugging skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

perf-profiler capabilities & compatibility

Capabilities
perf code paths · perf benchmarker · perf analyzer
Use cases
debugging · data analysis
From the docs

What perf-profiler says it does

Run profiling tools and capture hotspots with evidence.
SKILL.md
Verify debug symbols before profiling.
SKILL.md
No profiling without a clear scenario.
SKILL.md
npx skills add https://github.com/avifenesh/agentsys --skill perf-profiler

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs66
repo stars931
Last updatedJuly 26, 2026
Repositoryavifenesh/agentsys

What it does

Profile CPU and memory hot paths and capture file:line hotspots with a flame graph.

Who is it for?

Pinpointing CPU/memory hotspots with file:line evidence and a flame graph.

Skip if: Profiling without a clear scenario, which it refuses.

When should I use this skill?

You are profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.

What you get

  • Hotspot file:line list plus a flame graph or profile artifact

Files

SKILL.mdMarkdownGitHub ↗

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

Debuggingbackendtesting

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.