perf-analyzer
Use when synthesizing perf findings into evidence-backed recommendations and decisions.
Best use case
perf-analyzer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when synthesizing perf findings into evidence-backed recommendations and decisions.
Teams using perf-analyzer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/perf-analyzer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How perf-analyzer Compares
| Feature / Agent | perf-analyzer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when synthesizing perf findings into evidence-backed recommendations and decisions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# perf-analyzer Synthesize performance investigation results into clear recommendations. Follow `docs/perf-requirements.md` as the canonical contract. ## Inputs - Baseline data - Experiment results - Profiling evidence - Hypotheses tested - Breaking point results ## Output Format ``` summary: <2-3 sentences> recommendations: - <actionable recommendation 1> - <actionable recommendation 2> abandoned: - <hypothesis or experiment that failed> next_steps: - <if user should continue or stop> ``` ## Constraints - Only cite evidence that exists in logs or code. - If data is insufficient, say so and request a re-run.
Related Skills
perf-profiler
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
perf-baseline-manager
Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.
perf-investigation-logger
Use when appending structured perf investigation notes and evidence.
perf-theory-tester
Use when running controlled perf experiments to validate hypotheses.
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.
perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
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.
repo-intel
Use when user asks to "run repo intel", "generate repo map", "analyze repo", "query hotspots", "check ownership", or "bus factor". Unified static analysis - git history, AST symbols, project metadata.
consult
Cross-tool AI consultation. Use when user asks to 'consult gemini', 'ask codex', 'get second opinion', 'cross-check with claude', 'consult another AI', 'ask opencode', 'copilot opinion', or wants a second opinion from a different AI tool.
enhance-claude-memory
Use when improving CLAUDE.md or AGENTS.md project memory files.
sync-docs
Sync documentation with code. Use when user asks to update docs, check docs, fix stale documentation, update changelog, or after code changes.
enhance-cross-file
Use when checking cross-file consistency: tools vs frontmatter, agent references, duplicate rules, contradictions.