
Performance Analysis
- 1k installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
performance-analysis is a Claude Code skill at version 1.0.0 that detects bottlenecks, profiles swarm behavior, and delivers optimization recommendations for Claude Flow agent orchestration systems.
About
performance-analysis is a monitoring and profiling skill from ruvnet/ruflo at version 1.0.0 that consolidates bottleneck detection, swarm operation profiling, detailed report generation, and actionable optimization recommendations for Claude Flow swarms. It identifies performance bottlenecks across communication, processing, memory, and network layers in multi-agent systems. Tagged for performance, bottleneck, optimization, profiling, metrics, and analysis workflows. Developers reach for performance-analysis when Claude Flow swarms exhibit latency, resource contention, or degraded throughput and need structured profiling reports with concrete tuning suggestions.
- Identifies bottlenecks across communication, processing, memory, and network layers
- Real-time monitoring combined with historical performance profiling
- Generates comprehensive reports in multiple formats including HTML
- Delivers AI-powered actionable optimization recommendations
- Supports auto-fix mode with configurable performance thresholds
Performance Analysis by the numbers
- 1,006 all-time installs (skills.sh)
- +3 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #49 of 596 Debugging skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill performance-analysisAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1k |
|---|---|
| repo stars | ★ 67k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you profile bottlenecks in Claude Flow agent swarms?
Detect bottlenecks, profile swarm behavior, and receive optimization recommendations for Claude Flow agent systems.
Who is it for?
Developers operating Claude Flow multi-agent swarms who need structured bottleneck detection and optimization recommendations across swarm layers.
Skip if: Skip performance-analysis for single-agent workflows with no swarm orchestration or when profiling generic application code unrelated to Claude Flow.
When should I use this skill?
The user reports Claude Flow swarm latency, needs bottleneck detection, or wants profiling reports and optimization recommendations for agent orchestration.
What you get
Bottleneck detection reports, swarm profiling metrics, and actionable optimization recommendations across communication, processing, memory, and network layers.
- Bottleneck detection reports
- Swarm optimization recommendations
By the numbers
- Version 1.0.0 skill profiling 4 bottleneck layers: communication, processing, memory, network
Files
Performance Analysis Skill
Comprehensive performance analysis suite for identifying bottlenecks, profiling swarm operations, generating detailed reports, and providing actionable optimization recommendations.
Overview
This skill consolidates all performance analysis capabilities:
- Bottleneck Detection: Identify performance bottlenecks across communication, processing, memory, and network
- Performance Profiling: Real-time monitoring and historical analysis of swarm operations
- Report Generation: Create comprehensive performance reports in multiple formats
- Optimization Recommendations: AI-powered suggestions for improving performance
Quick Start
Basic Bottleneck Detection
npx claude-flow bottleneck detectGenerate Performance Report
npx claude-flow analysis performance-report --format html --include-metricsAnalyze and Auto-Fix
npx claude-flow bottleneck detect --fix --threshold 15Core Capabilities
1. Bottleneck Detection
Command Syntax
npx claude-flow bottleneck detect [options]Options
--swarm-id, -s <id>- Analyze specific swarm (default: current)--time-range, -t <range>- Analysis period: 1h, 24h, 7d, all (default: 1h)--threshold <percent>- Bottleneck threshold percentage (default: 20)--export, -e <file>- Export analysis to file--fix- Apply automatic optimizations
Usage Examples
# Basic detection for current swarm
npx claude-flow bottleneck detect
# Analyze specific swarm over 24 hours
npx claude-flow bottleneck detect --swarm-id swarm-123 -t 24h
# Export detailed analysis
npx claude-flow bottleneck detect -t 24h -e bottlenecks.json
# Auto-fix detected issues
npx claude-flow bottleneck detect --fix --threshold 15
# Low threshold for sensitive detection
npx claude-flow bottleneck detect --threshold 10 --export critical-issues.jsonMetrics Analyzed
Communication Bottlenecks:
- Message queue delays
- Agent response times
- Coordination overhead
- Memory access patterns
- Inter-agent communication latency
Processing Bottlenecks:
- Task completion times
- Agent utilization rates
- Parallel execution efficiency
- Resource contention
- CPU$memory usage patterns
Memory Bottlenecks:
- Cache hit rates
- Memory access patterns
- Storage I/O performance
- Neural pattern loading times
- Memory allocation efficiency
Network Bottlenecks:
- API call latency
- MCP communication delays
- External service timeouts
- Concurrent request limits
- Network throughput issues
Output Format
🔍 Bottleneck Analysis Report
━━━━━━━━━━━━━━━━━━━━━━━━━━━
📊 Summary
├── Time Range: Last 1 hour
├── Agents Analyzed: 6
├── Tasks Processed: 42
└── Critical Issues: 2
🚨 Critical Bottlenecks
1. Agent Communication (35% impact)
└── coordinator → coder-1 messages delayed by 2.3s avg
2. Memory Access (28% impact)
└── Neural pattern loading taking 1.8s per access
⚠️ Warning Bottlenecks
1. Task Queue (18% impact)
└── 5 tasks waiting > 10s for assignment
💡 Recommendations
1. Switch to hierarchical topology (est. 40% improvement)
2. Enable memory caching (est. 25% improvement)
3. Increase agent concurrency to 8 (est. 20% improvement)
✅ Quick Fixes Available
Run with --fix to apply:
- Enable smart caching
- Optimize message routing
- Adjust agent priorities2. Performance Profiling
Real-time Detection
Automatic analysis during task execution:
- Execution time vs. complexity
- Agent utilization rates
- Resource constraints
- Operation patterns
Common Bottleneck Patterns
Time Bottlenecks:
- Tasks taking > 5 minutes
- Sequential operations that could parallelize
- Redundant file operations
- Inefficient algorithm implementations
Coordination Bottlenecks:
- Single agent for complex tasks
- Unbalanced agent workloads
- Poor topology selection
- Excessive synchronization points
Resource Bottlenecks:
- High operation count (> 100)
- Memory constraints
- I/O limitations
- Thread pool saturation
MCP Integration
// Check for bottlenecks in Claude Code
mcp__claude-flow__bottleneck_detect({
timeRange: "1h",
threshold: 20,
autoFix: false
})
// Get detailed task results with bottleneck analysis
mcp__claude-flow__task_results({
taskId: "task-123",
format: "detailed"
})Result Format:
{
"bottlenecks": [
{
"type": "coordination",
"severity": "high",
"description": "Single agent used for complex task",
"recommendation": "Spawn specialized agents for parallel work",
"impact": "35%",
"affectedComponents": ["coordinator", "coder-1"]
}
],
"improvements": [
{
"area": "execution_time",
"suggestion": "Use parallel task execution",
"expectedImprovement": "30-50% time reduction",
"implementationSteps": [
"Split task into smaller units",
"Spawn 3-4 specialized agents",
"Use mesh topology for coordination"
]
}
],
"metrics": {
"avgExecutionTime": "142s",
"agentUtilization": "67%",
"cacheHitRate": "82%",
"parallelizationFactor": 1.2
}
}3. Report Generation
Command Syntax
npx claude-flow analysis performance-report [options]Options
--format <type>- Report format: json, html, markdown (default: markdown)--include-metrics- Include detailed metrics and charts--compare <id>- Compare with previous swarm--time-range <range>- Analysis period: 1h, 24h, 7d, 30d, all--output <file>- Output file path--sections <list>- Comma-separated sections to include
Report Sections
1. Executive Summary
- Overall performance score
- Key metrics overview
- Critical findings
2. Swarm Overview
- Topology configuration
- Agent distribution
- Task statistics
3. Performance Metrics
- Execution times
- Throughput analysis
- Resource utilization
- Latency breakdown
4. Bottleneck Analysis
- Identified bottlenecks
- Impact assessment
- Optimization priorities
5. Comparative Analysis (when --compare used)
- Performance trends
- Improvement metrics
- Regression detection
6. Recommendations
- Prioritized action items
- Expected improvements
- Implementation guidance
Usage Examples
# Generate HTML report with all metrics
npx claude-flow analysis performance-report --format html --include-metrics
# Compare current swarm with previous
npx claude-flow analysis performance-report --compare swarm-123 --format markdown
# Custom output with specific sections
npx claude-flow analysis performance-report \
--sections summary,metrics,recommendations \
--output reports$perf-analysis.html \
--format html
# Weekly performance report
npx claude-flow analysis performance-report \
--time-range 7d \
--include-metrics \
--format markdown \
--output docs$weekly-performance.md
# JSON format for CI/CD integration
npx claude-flow analysis performance-report \
--format json \
--output build$performance.jsonSample Markdown Report
# Performance Analysis Report
## Executive Summary
- **Overall Score**: 87/100
- **Analysis Period**: Last 24 hours
- **Swarms Analyzed**: 3
- **Critical Issues**: 1
## Key Metrics
| Metric | Value | Trend | Target |
|--------|-------|-------|--------|
| Avg Task Time | 42s | ↓ 12% | 35s |
| Agent Utilization | 78% | ↑ 5% | 85% |
| Cache Hit Rate | 91% | → | 90% |
| Parallel Efficiency | 2.3x | ↑ 0.4x | 2.5x |
## Bottleneck Analysis
### Critical
1. **Agent Communication Delay** (Impact: 35%)
- Coordinator → Coder messages delayed by 2.3s avg
- **Fix**: Switch to hierarchical topology
### Warnings
1. **Memory Access Pattern** (Impact: 18%)
- Neural pattern loading: 1.8s per access
- **Fix**: Enable memory caching
## Recommendations
1. **High Priority**: Switch to hierarchical topology (40% improvement)
2. **Medium Priority**: Enable memory caching (25% improvement)
3. **Low Priority**: Increase agent concurrency to 8 (20% improvement)4. Optimization Recommendations
Automatic Fixes
When using --fix, the following optimizations may be applied:
1. Topology Optimization
- Switch to more efficient topology (mesh → hierarchical)
- Adjust communication patterns
- Reduce coordination overhead
- Optimize message routing
2. Caching Enhancement
- Enable memory caching
- Optimize cache strategies
- Preload common patterns
- Implement cache warming
3. Concurrency Tuning
- Adjust agent counts
- Optimize parallel execution
- Balance workload distribution
- Implement load balancing
4. Priority Adjustment
- Reorder task queues
- Prioritize critical paths
- Reduce wait times
- Implement fair scheduling
5. Resource Optimization
- Optimize memory usage
- Reduce I/O operations
- Batch API calls
- Implement connection pooling
Performance Impact
Typical improvements after bottleneck resolution:
- Communication: 30-50% faster message delivery
- Processing: 20-40% reduced task completion time
- Memory: 40-60% fewer cache misses
- Network: 25-45% reduced API latency
- Overall: 25-45% total performance improvement
Advanced Usage
Continuous Monitoring
# Monitor performance in real-time
npx claude-flow swarm monitor --interval 5
# Generate hourly reports
while true; do
npx claude-flow analysis performance-report \
--format json \
--output logs$perf-$(date +%Y%m%d-%H%M).json
sleep 3600
doneCI/CD Integration
# .github$workflows$performance.yml
name: Performance Analysis
on: [push, pull_request]
jobs:
analyze:
runs-on: ubuntu-latest
steps:
- uses: actions$checkout@v2
- name: Run Performance Analysis
run: |
npx claude-flow analysis performance-report \
--format json \
--output performance.json
- name: Check Performance Thresholds
run: |
npx claude-flow bottleneck detect \
--threshold 15 \
--export bottlenecks.json
- name: Upload Reports
uses: actions$upload-artifact@v2
with:
name: performance-reports
path: |
performance.json
bottlenecks.jsonCustom Analysis Scripts
// scripts$analyze-performance.js
const { exec } = require('child_process');
const fs = require('fs');
async function analyzePerformance() {
// Run bottleneck detection
const bottlenecks = await runCommand(
'npx claude-flow bottleneck detect --format json'
);
// Generate performance report
const report = await runCommand(
'npx claude-flow analysis performance-report --format json'
);
// Analyze results
const analysis = {
bottlenecks: JSON.parse(bottlenecks),
performance: JSON.parse(report),
timestamp: new Date().toISOString()
};
// Save combined analysis
fs.writeFileSync(
'analysis$combined-report.json',
JSON.stringify(analysis, null, 2)
);
// Generate alerts if needed
if (analysis.bottlenecks.critical.length > 0) {
console.error('CRITICAL: Performance bottlenecks detected!');
process.exit(1);
}
}
function runCommand(cmd) {
return new Promise((resolve, reject) => {
exec(cmd, (error, stdout, stderr) => {
if (error) reject(error);
else resolve(stdout);
});
});
}
analyzePerformance().catch(console.error);Best Practices
1. Regular Analysis
- Run bottleneck detection after major changes
- Generate weekly performance reports
- Monitor trends over time
- Set up automated alerts
2. Threshold Tuning
- Start with default threshold (20%)
- Lower for production systems (10-15%)
- Higher for development (25-30%)
- Adjust based on requirements
3. Fix Strategy
- Always review before applying --fix
- Test fixes in development first
- Apply fixes incrementally
- Monitor impact after changes
4. Report Integration
- Include in documentation
- Share with team regularly
- Track improvements over time
- Use for capacity planning
5. Continuous Optimization
- Learn from each analysis
- Build performance budgets
- Establish baselines
- Set improvement goals
Troubleshooting
Common Issues
High Memory Usage
# Analyze memory bottlenecks
npx claude-flow bottleneck detect --threshold 10
# Check cache performance
npx claude-flow cache manage --action stats
# Review memory metrics
npx claude-flow memory usageSlow Task Execution
# Identify slow tasks
npx claude-flow task status --detailed
# Analyze coordination overhead
npx claude-flow bottleneck detect --time-range 1h
# Check agent utilization
npx claude-flow agent metricsPoor Cache Performance
# Analyze cache hit rates
npx claude-flow analysis performance-report --sections metrics
# Review cache strategy
npx claude-flow cache manage --action analyze
# Enable cache warming
npx claude-flow bottleneck detect --fixIntegration with Other Skills
- swarm-orchestration: Use performance data to optimize topology
- memory-management: Improve cache strategies based on analysis
- task-coordination: Adjust scheduling based on bottlenecks
- neural-training: Train patterns from performance data
Related Commands
npx claude-flow swarm monitor- Real-time monitoringnpx claude-flow token usage- Token optimization analysisnpx claude-flow cache manage- Cache optimizationnpx claude-flow agent metrics- Agent performance metricsnpx claude-flow task status- Task execution analysis
See Also
- Bottleneck Detection Guide
- Performance Report Guide
- Performance Bottlenecks Overview
- Swarm Monitoring Documentation
- Memory Management Documentation
---
Version: 1.0.0 Last Updated: 2025-10-19 Maintainer: Claude Flow Team
Related skills
How it compares
Pick performance-analysis over generic APM tools when bottlenecks are specific to Claude Flow swarm orchestration rather than standard web request paths.
FAQ
What does performance-analysis profile in Claude Flow?
performance-analysis profiles Claude Flow swarm operations across communication, processing, memory, and network layers. The version 1.0.0 skill detects bottlenecks and generates detailed reports with actionable optimization recommendations for multi-agent orchestration.
Which bottleneck types does performance-analysis detect?
performance-analysis detects performance bottlenecks across four layers: communication between agents, processing throughput, memory usage, and network latency. Results feed into consolidated profiling reports with tuning suggestions.
When should developers run performance-analysis?
Developers should run performance-analysis when Claude Flow swarms show latency, resource contention, or degraded throughput. The skill consolidates metrics collection, profiling, and optimization recommendations in one workflow.
Is Performance Analysis safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.