Token导航 LogoToken导航

Agent Skill · 研究检索

optimization-analyzer(优化分析器)

optimization-analyzer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

optimization-analyzer 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证为 MIT,暂无第三方扫描结果,按安装量在研究检索类的 73,675 个 Skill 里排第 56,831。

总安装 445周安装 18GitHub Stars 公开资料未说明下载 140核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:optimization-analyzer(优化分析器)
来源仓库:https://github.com/vamseeachanta/workspace-hub
仓库路径:skills/optimization-analyzer
安装命令:
npx skills add vamseeachanta/workspace-hub --skill "optimization-analyzer"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

AgentSkills.tonpx skills
npx skills add vamseeachanta/workspace-hub --skill "optimization-analyzer"

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

optimization-analyzer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。适用于工作空间优化分析和性能评估的场景。

通过 npx skills add vamseeachanta/workspace-hub --skill "optimization-analyzer" 命令安装。安装前建议确认权限范围和维护状态,注意可能涉及性能监控和数据分析操作。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/optimization-analyzer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add vamseeachanta/workspace-hub --skill "optimization-analyzer";命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

optimization-analyzer 怎么安装?

在终端执行 npx skills add vamseeachanta/workspace-hub --skill "optimization-analyzer"。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

optimization-analyzer 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

optimization-analyzer 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add vamseeachanta/workspace-hub --skill "optimization-analyzer" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

optimization-analyzer 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

optimization-analyzer 用的人多吗?

公开数据是累计安装 445 次,近一周安装 18 次,下载 140 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

optimization-analyzer 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
optimization-analyzer

优化分析器 · 本页

445—执行命令MIT未收录

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Performance Analyzer Skill

Overview

This skill specializes in identifying and resolving performance bottlenecks in development workflows, agent coordination, and system operations. It provides comprehensive analysis, pattern recognition, and actionable recommendations.

When to Use

  • Analyzing slow execution times in workflows
  • Identifying resource constraints (CPU, memory, I/O)
  • Detecting coordination overhead in agent systems
  • Finding parallelization opportunities
  • Root cause analysis for performance issues
  • Generating optimization recommendations

Quick Start

# Run bottleneck analysis
npx claude-flow bottleneck-analyze --component swarm-coordination

# Generate performance report
npx claude-flow performance-report --format detailed --timeframe 24h

# Collect metrics for analysis
npx claude-flow metrics-collect --components ["cpu", "memory", "network"]

# Trend analysis
npx claude-flow trend-analysis --metric performance --period 7d

Architecture

+-----------------------------------------------------------+
|                  Performance Analyzer                      |
+-----------------------------------------------------------+
|  Data Collector  |  Pattern Analyzer  |  Recommender      |
+------------------+--------------------+-------------------+
         |                  |                    |
         v                  v                    v
+----------------+  +------------------+  +------------------+
| Metrics        |  | Bottleneck Types |  | Strategies       |
| - Execution    |  | - Execution Time |  | - Parallelization|
| - Resources    |  | - Resources      |  | - Reallocation   |
| - Dependencies |  | - Coordination   |  | - Algorithm      |
| - Communication|  | - Sequential     |  | - Caching        |
+----------------+  | - Data Transfer  |  | - Topology       |
                    +------------------+  +------------------+
         |                  |                    |
         v                  v                    v
+-----------------------------------------------------------+
|              Report Generator & Action Plan                |
+-----------------------------------------------------------+

Bottleneck Types

TypeSymptomsDetection Method
Execution TimeTasks taking longer than expectedTiming analysis
Resource ConstraintsCPU/memory/I/O at limitsResource monitoring
Coordination OverheadInefficient agent communicationMessage analysis
Sequential BlockersUnnecessary serial executionDependency mapping
Data TransferLarge payload movementsNetwork analysis

Analysis Workflow

1. Data Collection Phase

// Comprehensive data collection
const dataCollection = {
  async collect(swarmId, duration = 60000) {
    const metrics = await Promise.all([
      this.gatherExecutionMetrics(swarmId),
      this.profileResourceUsage(swarmId),
      this.mapTaskDependencies(swarmId),
      this.traceCommunicationPatterns(swarmId),
      this.identifyHotspots(swarmId)
    ]);

    return {
      execution: metrics[0],
      resources: metrics[1],
      dependencies: metrics[2],
      communication: metrics[3],
      hotspots: metrics[4],
      timestamp: Date.now()
    };
  }
};

2. Analysis Phase

// Multi-dimensional analysis
const analysis = {
  async analyze(data, baselines) {
    return {
      // Compare against baselines
      comparison: this.compareAgainstBaselines(data, baselines),

      // Identify anomalies
      anomalies: this.identifyAnomalies(data),

      // Correlate metrics
      correlations: this.correlateMetrics(data),

      // Determine root causes
      rootCauses: await this.determineRootCauses(data),

      // Prioritize issues
      prioritizedIssues: this.prioritizeIssues(data)
    };
  }
};

3. Recommendation Phase

// Generate actionable recommendations
const recommendations = {
  async generate(analysis) {
    return {
      optimizations: this.generateOptimizationOptions(analysis),
      improvements: this.estimateImprovementPotential(analysis),
      effort: this.assessImplementationEffort(analysis),
      actionPlan: this.createActionPlan(analysis),
      successMetrics: this.defineSuccessMetrics(analysis)
    };
  }
};

Common Bottleneck Patterns

1. Single Agent Overload

Symptoms: One agent handling complex tasks alone Detection: Agent utilization > 90%, queue depth growing Solution: Spawn specialized agents for parallel work Expected Improvement: 40-60%

2. Sequential Task Chain

Symptoms: Tasks waiting unnecessarily Detection: Low parallelization ratio, high wait times Solution: Identify parallelization opportunities Expected Improvement: 30-50%

3. Resource Starvation

Symptoms: Agents waiting for resources Detection: Resource contention, lock waits Solution: Increase limits or optimize usage Expected Improvement: 20-40%

4. Communication Overhead

Symptoms: Excessive inter-agent messages Detection: High message count, latency spikes Solution: Batch operations or change topology Expected Improvement: 25-45%

5. Inefficient Algorithms

Symptoms: High complexity operations Detection: O(n^2) patterns, memory pressure Solution: Algorithm optimization or caching Expected Improvement: 50-80%

Key Performance Indicators

KPIDescriptionTarget
Task Execution TimeAverage, P95, P99< baseline * 1.1
Resource UtilizationCPU, Memory, I/O60-80% optimal
Parallelization RatioParallel vs Sequential> 0.7
Agent EfficiencyTask throughput per agent> baseline
Communication LatencyMessage delays< 50ms

MCP Integration

// Performance analysis integration
const performanceIntegration = {
  // Comprehensive bottleneck analysis
  async analyzeBottlenecks(component = null) {
    const [bottlenecks, metrics, trends] = await Promise.all([
      mcp.bottleneck_analyze({ component }),
      mcp.metrics_collect({ components: ['system', 'agents', 'coordination'] }),
      mcp.trend_analysis({ metric: 'performance', period: '24h' })
    ]);

    return {
      bottlenecks,
      metrics,
      trends,
      analysis: this.synthesizeAnalysis(bottlenecks, metrics, trends)
    };
  },

  // Generate performance report
  async generateReport(format = 'detailed') {
    const [performance, usage, errors] = await Promise.all([
      mcp.performance_report({ format, timeframe: '24h' }),
      mcp.usage_stats({}),
      mcp.error_analysis({})
    ]);

    return { performance, usage, errors };
  }
};

Report Format

## Performance Analysis Report

### Executive Summary
- Overall performance score: 78/100
- Critical bottlenecks identified: 2
- Recommended actions: 5

### Detailed Findings

#### 1. Sequential Task Execution
- **Impact**: High (40% of execution time)
- **Root Cause**: Tasks A, B, C running sequentially without dependencies
- **Recommendation**: Parallelize tasks A, B, C
- **Expected Improvement**: 35%

#### 2. Memory Pressure
- **Impact**: Medium (25% of issues)
- **Root Cause**: Large file operations loading entire files
- **Recommendation**: Implement streaming processing
- **Expected Improvement**: 50% memory reduction

### Trend Analysis
- Performance over last 7 days: Declining 5%
- Improvement since last optimization: +12%
- Regression detection: None

Optimization Examples

Example 1: Slow Test Execution

MetricBeforeAfterImprovement
Duration10 min3 min70%
Parallelization10%80%8x
Agent Utilization25%85%3.4x

Solution: Parallelize test suites across multiple agents

Example 2: Agent Coordination Delay

MetricBeforeAfterImprovement
Latency150ms90ms40%
Messages500/s200/s60% reduction
Throughput100/s180/s80%

Solution: Switch from hierarchical to mesh topology

Example 3: Memory Pressure

MetricBeforeAfterImprovement
Peak Memory8GB800MB90%
GC Pauses500ms50ms90%
Processing Time5min3min40%

Solution: Stream processing instead of loading entire files

Advanced Features

1. Predictive Analysis

// ML-based bottleneck prediction
const predictiveAnalysis = {
  async predictBottlenecks(historicalData) {
    // Train model on historical patterns
    // Predict future bottlenecks
    // Recommend preemptive actions
  }
};

2. Automated Optimization

// Self-tuning optimization
const automatedOptimization = {
  async optimize(swarm, constraints) {
    // Self-tuning parameters
    // Dynamic resource allocation
    // Adaptive execution strategies
  }
};

3. A/B Testing

// Compare optimization strategies
const abTesting = {
  async compare(strategies, workload) {
    // Run strategies in parallel
    // Measure real-world impact
    // Data-driven decision
  }
};

Integration Points

IntegrationPurpose
Orchestration AgentsPerformance feedback, strategy suggestions
Monitoring AgentsReal-time metrics, health correlation
Optimization AgentsHandoff optimization tasks, validate results
CI/CD PipelinePerformance gates, regression detection

Best Practices

Continuous Monitoring

  • Set up baseline metrics before analysis
  • Monitor performance trends continuously
  • Alert on regressions immediately
  • Run regular optimization cycles

Proactive Analysis

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

Documentation

  • Document all findings and actions
  • Track improvement over time
  • Share learnings across teams
  • Maintain optimization history

Related Skills

  • optimization-monitor - Real-time performance monitoring
  • optimization-benchmark - Performance testing and validation
  • optimization-load-balancer - Load distribution optimization
  • optimization-resources - Resource allocation
  • optimization-topology - Network topology optimization

Version History

  • 1.0.0 (2026-01-02): Initial release - converted from performance-analyzer agent with bottleneck detection, pattern recognition, root cause analysis, and optimization recommendations

平台分布

Claude Code

26.39%
按下载量换算37

windsurf

20.88%
按下载量换算29

trae

18.11%
按下载量换算25

OpenCode

12.44%
按下载量换算17

Cursor

8.38%
按下载量换算12

Codex

3.46%
按下载量换算5

安全审计

暂无安全审计结果可展示。

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add vamseeachanta/workspace-hub --skill "optimization-analyzer" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills