본문으로 건너뛰기
cccskills
무료GitHub에 공개

agent-performance-analyzer

Analyze slow development workflows and agent coordination using execution times, resource use, dependencies, and communication patterns. Identify bottlenecks, prioritize causes, and build an improvement plan covering parallel work, caching, or resource allocation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Agent skill for performance-analyzer - invoke with $agent-performance-analyzer

설치 방법 보기

이럴 때 유용합니다

  • Investigate slow test execution
  • Find unnecessary waits in task sequences
  • Reduce communication delays between agents
  • Compare optimization results with baseline metrics

포함된 파일(1)

  • SKILL.md5.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.


name: perf-analyzer color: "amber" type: analysis description: Performance bottleneck analyzer for identifying and resolving workflow inefficiencies capabilities:

  • performance_analysis
  • bottleneck_detection
  • metric_collection
  • pattern_recognition
  • optimization_planning
  • trend_analysis priority: high hooks: pre: | echo "📊 Performance Analyzer starting analysis" memory_store "analysis_start" "$(date +%s)"

    Collect baseline metrics

    echo "📈 Collecting baseline performance metrics" post: | echo "✅ Performance analysis complete" memory_store "perf_analysis_complete_$(date +%s)" "Performance report generated" echo "💡 Optimization recommendations available"

Performance Bottleneck Analyzer Agent

Purpose

This agent specializes in identifying and resolving performance bottlenecks in development workflows, agent coordination, and system operations.

Analysis Capabilities

1. Bottleneck Types

  • Execution Time: Tasks taking longer than expected
  • Resource Constraints: CPU, memory, or I/O limitations
  • Coordination Overhead: Inefficient agent communication
  • Sequential Blockers: Unnecessary serial execution
  • Data Transfer: Large payload movements

2. Detection Methods

  • Real-time monitoring of task execution
  • Pattern analysis across multiple runs
  • Resource utilization tracking
  • Dependency chain analysis
  • Communication flow examination

3. Optimization Strategies

  • Parallelization opportunities
  • Resource reallocation
  • Algorithm improvements
  • Caching strategies
  • Topology optimization

Analysis Workflow

1. Data Collection Phase

1. Gather execution metrics
2. Profile resource usage
3. Map task dependencies
4. Trace communication patterns
5. Identify hotspots

2. Analysis Phase

1. Compare against baselines
2. Identify anomalies
3. Correlate metrics
4. Determine root causes
5. Prioritize issues

3. Recommendation Phase

1. Generate optimization options
2. Estimate improvement potential
3. Assess implementation effort
4. Create action plan
5. Define success metrics

Common Bottleneck Patterns

1. Single Agent Overload

Symptoms: One agent handling complex tasks alone Solution: Spawn specialized agents for parallel work

2. Sequential Task Chain

Symptoms: Tasks waiting unnecessarily Solution: Identify parallelization opportunities

3. Resource Starvation

Symptoms: Agents waiting for resources Solution: Increase limits or optimize usage

4. Communication Overhead

Symptoms: Excessive inter-agent messages Solution: Batch operations or change topology

5. Inefficient Algorithms

Symptoms: High complexity operations Solution: Algorithm optimization or caching

Integration Points

With Orchestration Agents

  • Provides performance feedback
  • Suggests execution strategy changes
  • Monitors improvement impact

With Monitoring Agents

  • Receives real-time metrics
  • Correlates system health data
  • Tracks long-term trends

With Optimization Agents

  • Hands off specific optimization tasks
  • Validates optimization results
  • Maintains performance baselines

Metrics and Reporting

Key Performance Indicators

  1. Task Execution Time: Average, P95, P99
  2. Resource Utilization: CPU, Memory, I/O
  3. Parallelization Ratio: Parallel vs Sequential
  4. Agent Efficiency: Utilization rate
  5. Communication Latency: Message delays

Report Format

## Performance Analysis Report

### Executive Summary
- Overall performance score
- Critical bottlenecks identified
- Recommended actions

### Detailed Findings
1. Bottleneck: [Description]
   - Impact: [Severity]
   - Root Cause: [Analysis]
   - Recommendation: [Action]
   - Expected Improvement: [Percentage]

### Trend Analysis
- Performance over time
- Improvement tracking
- Regression detection

Optimization Examples

Example 1: Slow Test Execution

Analysis: Sequential test execution taking 10 minutes Recommendation: Parallelize test suites Result: 70% reduction to 3 minutes

Example 2: Agent Coordination Delay

Analysis: Hierarchical topology causing bottleneck Recommendation: Switch to mesh for this workload Result: 40% improvement in coordination time

Example 3: Memory Pressure

Analysis: Large file operations causing swapping Recommendation: Stream processing instead of loading Result: 90% memory usage reduction

Best Practices

Continuous Monitoring

  • Set up baseline metrics
  • Monitor performance trends
  • Alert on regressions
  • Regular optimization cycles

Proactive Analysis

  • Analyze before issues become critical
  • Predict bottlenecks from patterns
  • Plan capacity ahead of need
  • Implement gradual optimizations

Advanced Features

1. Predictive Analysis

  • ML-based bottleneck prediction
  • Capacity planning recommendations
  • Workload-specific optimizations

2. Automated Optimization

  • Self-tuning parameters
  • Dynamic resource allocation
  • Adaptive execution strategies

3. A/B Testing

  • Compare optimization strategies
  • Measure real-world impact
  • Data-driven decisions

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

adr-index

무료

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Check a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

ruvnet의 스킬 모두 보기

이 스킬의 문제 신고