Performance Analysis Skill
Identify bottlenecks, profile swarm operations, generate performance reports, and
apply optimisation recommendations for Claude Flow swarms.
When To Use
- Profiling swarm performance or diagnosing slow agents
- Detecting communication / processing / memory / network bottlenecks
- Generating performance reports (json/html/markdown) for review or CI/CD
- Tuning topology, concurrency, caching, and resource allocation
When Not To Use
- CUDA GPU kernel profiling → use the cuda skill
- Full dev pipelines with quality gates and testing → use build-with-quality
- Truth scoring and automatic rollback of bad changes → use verification-quality
- General swarm orchestration without a performance focus → use swarm-advanced
- AgentDB vector-search performance tuning → use agentdb-vector-search
Claude Code only: the mcp__claude-flow__* tool call below needs the
claude-flow MCP server registered (already wired in this container). On Codex
/ GPT-6 Astra: use the CLI form instead.
Quick Start
Verified against the deployed CLI (claude-flow performance --help and
claude-flow performance bottleneck --help, ruflo v3.38.21) — there is no
top-level bottleneck or analysis command; both live under performance:
# Detect bottlenecks in the current swarm (quick pass; -d full for deep analysis)
claude-flow performance bottleneck -d full
# View/export metrics (there is no `analysis performance-report`; use metrics)
claude-flow performance metrics -t 24h -f prometheus
# Run optimisation recommendations and apply them
claude-flow performance optimize --apply
From Claude Code (MCP):
mcp__claude-flow__bottleneck_analyze({ timeRange: "1h", threshold: 20, autoFix: false })
Core Capabilities
- Bottleneck detection — communication, processing, memory, and network,
with real-time profiling and severity-ranked output.
- Report generation — executive summary, metrics, bottleneck analysis, and
prioritized recommendations in json/html/markdown.
- Optimisation —
--fix applies topology, caching, concurrency, priority,
and resource optimisations; review before applying.
References
Load these on demand for the full detail:
references/bottleneck-detection.md —
performance bottleneck options, the metric taxonomy, output format, common
patterns, and MCP integration (JSON result shapes).
references/reporting.md —
performance metrics formats, sections, examples, and a sample report.
references/optimisation-and-operations.md —
performance optimize catalog, expected performance impact, continuous monitoring, CI/CD
integration, custom scripts, best practices, and troubleshooting recipes.
Related
Verified against claude-flow --help (ruflo v3.38.21) — swarm monitor,
token, and cache are not real top-level or subcommands in this build:
claude-flow performance metrics — real-time and historical metrics (no swarm monitor exists)
claude-flow agent metrics — agent performance metrics
claude-flow performance benchmark — benchmark suites (wasm/neural/memory/search)
- swarm-advanced · agentdb-memory-patterns
Version: 1.1.0 · Last Updated: 2026-07-28 · Maintainer: Claude Flow Team
1---2name: performance-analysis3description: Performance analysis, bottleneck detection, and optimisation for Claude Flow swarms. Use when profiling swarm performance, diagnosing slow agents, or tuning topology and resource allocation.4---56# Performance Analysis Skill78Identify bottlenecks, profile swarm operations, generate performance reports, and9apply optimisation recommendations for Claude Flow swarms.1011## When To Use12- Profiling swarm performance or diagnosing slow agents13- Detecting communication / processing / memory / network bottlenecks14- Generating performance reports (json/html/markdown) for review or CI/CD15- Tuning topology, concurrency, caching, and resource allocation1617## When Not To Use18- CUDA GPU kernel profiling → use the **cuda** skill19- Full dev pipelines with quality gates and testing → use **build-with-quality**20- Truth scoring and automatic rollback of bad changes → use **verification-quality**21- General swarm orchestration without a performance focus → use **swarm-advanced**22- AgentDB vector-search performance tuning → use **agentdb-vector-search**2324Claude Code only: the `mcp__claude-flow__*` tool call below needs the25claude-flow MCP server registered (already wired in this container). On Codex26/ GPT-6 Astra: use the CLI form instead.2728## Quick Start2930Verified against the deployed CLI (`claude-flow performance --help` and31`claude-flow performance bottleneck --help`, ruflo v3.38.21) — there is no32top-level `bottleneck` or `analysis` command; both live under `performance`:3334```bash35# Detect bottlenecks in the current swarm (quick pass; -d full for deep analysis)36claude-flow performance bottleneck -d full3738# View/export metrics (there is no `analysis performance-report`; use metrics)39claude-flow performance metrics -t 24h -f prometheus4041# Run optimisation recommendations and apply them42claude-flow performance optimize --apply43```4445From Claude Code (MCP):46```javascript47mcp__claude-flow__bottleneck_analyze({ timeRange: "1h", threshold: 20, autoFix: false })48```4950## Core Capabilities511. **Bottleneck detection** — communication, processing, memory, and network,52 with real-time profiling and severity-ranked output.532. **Report generation** — executive summary, metrics, bottleneck analysis, and54 prioritized recommendations in json/html/markdown.553. **Optimisation** — `--fix` applies topology, caching, concurrency, priority,56 and resource optimisations; review before applying.5758## References59Load these on demand for the full detail:6061- [`references/bottleneck-detection.md`](references/bottleneck-detection.md) —62 `performance bottleneck` options, the metric taxonomy, output format, common63 patterns, and MCP integration (JSON result shapes).64- [`references/reporting.md`](references/reporting.md) —65 `performance metrics` formats, sections, examples, and a sample report.66- [`references/optimisation-and-operations.md`](references/optimisation-and-operations.md) —67 `performance optimize` catalog, expected performance impact, continuous monitoring, CI/CD68 integration, custom scripts, best practices, and troubleshooting recipes.6970## Related71Verified against `claude-flow --help` (ruflo v3.38.21) — `swarm monitor`,72`token`, and `cache` are not real top-level or subcommands in this build:73- `claude-flow performance metrics` — real-time and historical metrics (no `swarm monitor` exists)74- `claude-flow agent metrics` — agent performance metrics75- `claude-flow performance benchmark` — benchmark suites (wasm/neural/memory/search)76- [swarm-advanced](../swarm-advanced/SKILL.md) · [agentdb-memory-patterns](../agentdb-memory-patterns/SKILL.md)7778---7980**Version**: 1.1.0 · **Last Updated**: 2026-07-28 · **Maintainer**: Claude Flow Team