perf-profiler
A developer tool for profiling performance, generating flame graphs, and identifying system hotspots.
Install
mkdir -p .claude/skills/perf-profiler && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2363" && unzip -o skill.zip -d .claude/skills/perf-profiler && rm skill.zipInstalls to .claude/skills/perf-profiler
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.Key capabilities
- →Identify CPU/memory performance hotspots
- →Capture execution path data
- →Generate flame graphs for visualization
- →Verify debug symbol accessibility
- →Provide file-and-line level performance evidence
How it works
Attaches a profiler to a running process to sample execution points and aggregate them into report artifacts.
Inputs & outputs
When to use perf-profiler
- →Profiling CPU hot paths
- →Generating flame graphs
- →Capturing performance evidence
About this skill
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.
When not to use it
- →In production environments without strict resource controls
- →When profiling highly volatile code without a stable scenario
Prerequisites
Limitations
- →Performance overhead during profiling
- →Requires debug symbols to be meaningful
How it compares
Forces an evidence-based approach by requiring flame graphs and hotspot justification before reporting.
Compared to similar skills
perf-profiler side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| perf-profiler (this skill) | 1 | 6mo | No flags | Advanced |
| chrome-devtools | 41 | 7mo | Review | Intermediate |
| python-performance-optimization | 27 | 2mo | No flags | Intermediate |
| analyzing-logs | 14 | 27d | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ComposioHQ
View all by ComposioHQ →You might also like
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
python-performance-optimization
wshobson
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.
analyzing-logs
jeremylongshore
Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.
redis-inspect
civitai
Inspect Redis cache keys, values, and TTLs for debugging. Supports both main cache and system cache. Use for debugging cache issues, checking cached values, and monitoring cache state. Read-only by default.
obsidian-performance-tuning
jeremylongshore
Optimize Obsidian plugin performance for smooth operation. Use when experiencing lag, memory issues, or slow startup, or when optimizing plugin code for large vaults. Trigger with phrases like "obsidian performance", "obsidian slow", "optimize obsidian plugin", "obsidian memory usage".
obsidian-observability
jeremylongshore
Set up comprehensive logging and monitoring for Obsidian plugins. Use when implementing debug logging, tracking plugin performance, or setting up error reporting for your Obsidian plugin. Trigger with phrases like "obsidian logging", "obsidian monitoring", "obsidian debug", "track obsidian plugin".