Token导航 LogoToken导航

Agent Skill · 研究检索

benchmarking(benchmarking 搜索)

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

benchmarking 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 59,000。

总安装 396周安装 17GitHub Stars 61下载 139核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:benchmarking(benchmarking 搜索)
来源仓库:https://github.com/melodic-software/claude-code-plugins
仓库路径:skills/benchmarking
安装命令:
npx skills add https://github.com/melodic-software/claude-code-plugins --skill benchmarking
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/melodic-software/claude-code-plugins --skill benchmarking

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息,适合快速定位候选结果。可根据关键词、任务场景或来源线索进行信息聚合与过滤。建议结合原始 README 和安装命令进一步核验具体用法。安装前需确认权限范围、维护状态及是否触发联网或文件操作。benchmarking 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/benchmarking

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/melodic-software/claude-code-plugins --skill b…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

benchmarking 怎么安装?

在终端执行 npx skills add https://github.com/melodic-software/claude-code-plugins --skill benchmarkin…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

benchmarking 支持哪些 AI 工具?

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

benchmarking 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

benchmarking 是免费的吗?

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

benchmarking 用的人多吗?

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

benchmarking 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
benchmarking

benchmarking 搜索 · 本页

39661只读MIT通过

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

SKILL.md 原文

Benchmarking

When to Use This Skill

Use this skill when:

  • Benchmarking tasks - Working on benchmarking and competitive analysis techniques. compares performance, processes, and practices against industry standards, competitors, and best-in-class organizations
  • Planning or design - Need guidance on Benchmarking approaches
  • Best practices - Want to follow established patterns and standards

Overview

Systematically compare performance, processes, and practices against internal units, competitors, industry standards, or best-in-class organizations. Identifies gaps and improvement opportunities.

What is Benchmarking?

Benchmarking is the process of measuring your organization's processes, products, or services against those of recognized leaders to identify gaps and improvement opportunities.

Benchmarking Purpose

GoalDescription
Identify GapsWhere do we fall short of leaders?
Set TargetsWhat level of performance is achievable?
Learn PracticesHow do leaders achieve superior results?
Drive ImprovementWhat changes will close the gaps?

Benchmarking vs Competitive Analysis

AspectBenchmarkingCompetitive Analysis
FocusProcesses and practicesProducts and market position
GoalImprove own performanceUnderstand competitors
ScopeCan include non-competitorsDirect competitors
OutcomeImprovement planCompetitive strategy

Types of Benchmarking

Internal Benchmarking

Compare across internal units, teams, or locations:

AdvantageDisadvantage
Easy data accessLimited to internal best
Common contextMay miss external innovations
Quick to implementPolitical sensitivities
Low costMay perpetuate mediocrity

When to Use: Multiple locations, varied performance, starting point

Competitive Benchmarking

Compare against direct competitors:

AdvantageDisadvantage
Relevant comparisonData hard to obtain
Direct market contextMay be biased/incomplete
Stakeholder understandingLegal considerations
Strategic relevanceCompetitors may not be best

When to Use: Market positioning, product comparison, pricing

Functional Benchmarking

Compare similar functions across different industries:

AdvantageDisadvantage
Best-in-class practicesContext differences
Innovative ideasMay not transfer directly
Less competitive sensitivityHarder to arrange
Broader perspectiveMore complex adaptation

When to Use: Process improvement, breakthrough thinking

Strategic Benchmarking

Compare strategies and business models:

AdvantageDisadvantage
Strategic insightsHigh-level, less actionable
Transformative potentialLonger time to implement
Industry-changing ideasHarder to measure
Vision-settingMay require significant change

When to Use: Strategy development, transformation, disruption

Benchmarking Process

Phase 1: Plan

Step 1: Define Scope
## Benchmarking Scope

**Subject:** [What to benchmark]
**Type:** [Internal/Competitive/Functional/Strategic]
**Objective:** [Why benchmarking]
**Owner:** [Who's leading]
**Timeline:** [Start to finish]

### Success Criteria

- [What constitutes a successful benchmark study]
- [How results will be used]
Step 2: Identify Metrics
## Key Performance Indicators

| Category | Metric | Current | Definition |
|----------|--------|---------|------------|
| Efficiency | [Metric 1] | [Value] | [How measured] |
| Quality | [Metric 2] | [Value] | [How measured] |
| Speed | [Metric 3] | [Value] | [How measured] |
| Cost | [Metric 4] | [Value] | [How measured] |
Step 3: Select Benchmarking Partners
CriteriaDescription
RelevantSimilar processes or challenges
Best-in-classSuperior performance in area
WillingOpen to sharing
AccessibleData or contact available

Phase 2: Collect

Step 1: Gather Internal Data
## Internal Performance Data

| Process/Area | Metric | Current Performance | Trend |
|--------------|--------|--------------------:|-------|
| [Process 1] | [Metric] | [Value] | [Up/Down/Stable] |
| [Process 2] | [Metric] | [Value] | [Up/Down/Stable] |
Step 2: Gather External Data
SourceTypeReliability
Industry reportsSecondaryMedium-High
Public filingsSecondaryHigh
SurveysPrimaryMedium
Site visitsPrimaryHigh
ConferencesSecondaryMedium
Published case studiesSecondaryMedium
Step 3: Normalize Data

Ensure comparability:

  • Common definitions
  • Same time periods
  • Equivalent scope
  • Currency/unit conversion
  • Size adjustments (per employee, per revenue)

Phase 3: Analyze

Step 1: Calculate Gaps
## Gap Analysis

| Metric | Our Performance | Benchmark | Gap | Gap % |
|--------|----------------:|----------:|----:|------:|
| [Metric 1] | 85% | 95% | -10% | -11% |
| [Metric 2] | 24h | 4h | +20h | +500% |
| [Metric 3] | $50 | $30 | +$20 | +67% |
Step 2: Identify Root Causes

For each significant gap:

  • Why does the gap exist?
  • What practices enable superior performance?
  • What barriers prevent us from closing the gap?
  • What resources would be required?
Step 3: Prioritize Gaps
quadrantChart
    title Gap Prioritization
    x-axis Low Impact --> High Impact
    y-axis Difficult to Close --> Easy to Close
    quadrant-1 Strategic Initiatives
    quadrant-2 Quick Wins
    quadrant-3 Low Priority
    quadrant-4 Major Projects
    "Gap A": [0.8, 0.7]
    "Gap B": [0.3, 0.8]
    "Gap C": [0.7, 0.3]
    "Gap D": [0.2, 0.3]

Phase 4: Adapt

Step 1: Develop Improvement Actions
## Improvement Plan

### Gap: [Metric] - [Our Value] vs [Benchmark Value]

**Root Cause:** [Why the gap exists]

**Best Practice:** [What benchmark leaders do differently]

**Adaptation:**
| Action | Owner | Timeline | Resources | Expected Impact |
|--------|-------|----------|-----------|-----------------|
| [Action 1] | [Name] | [Date] | [Cost] | [Target] |
| [Action 2] | [Name] | [Date] | [Cost] | [Target] |

**Success Metric:** [How we'll measure improvement]
Step 2: Set Targets
ApproachDescriptionWhen to Use
Match benchmarkAchieve same levelRealistic, proven possible
Exceed benchmarkSurpass best-in-classCompetitive advantage
IncrementalClose gap by X%Resource-constrained
BreakthroughLeapfrog to new levelTransformational
Step 3: Implement and Monitor
  • Execute improvement actions
  • Track progress against targets
  • Report on gap closure
  • Iterate and refine

Competitive Analysis Framework

Porter's Five Forces Context

ForceBenchmarking Focus
RivalryDirect competitor comparison
New EntrantsEmerging competitor practices
SubstitutesAlternative solution benchmarks
Supplier PowerSupply chain efficiency
Buyer PowerCustomer satisfaction metrics

Competitive Profile Matrix

## Competitive Profile Matrix

| Success Factor | Weight | Company A | Company B | Company C |
|----------------|-------:|----------:|----------:|----------:|
| | | Rating | Score | Rating | Score | Rating | Score |
| Product Quality | 0.20 | 4 | 0.80 | 3 | 0.60 | 5 | 1.00 |
| Price | 0.15 | 3 | 0.45 | 4 | 0.60 | 2 | 0.30 |
| Market Share | 0.15 | 4 | 0.60 | 2 | 0.30 | 5 | 0.75 |
| Customer Service | 0.20 | 3 | 0.60 | 4 | 0.80 | 3 | 0.60 |
| Innovation | 0.15 | 2 | 0.30 | 3 | 0.45 | 5 | 0.75 |
| Distribution | 0.15 | 4 | 0.60 | 3 | 0.45 | 4 | 0.60 |
| **Total** | **1.00** | | **3.35** | | **3.20** | | **4.00** |

Rating: 1=Major Weakness, 2=Minor Weakness, 3=Neutral, 4=Minor Strength, 5=Major Strength

SWOT Integration

Benchmarking informs SWOT:

SWOT ElementBenchmarking Input
StrengthsWhere we exceed benchmarks
WeaknessesWhere we fall short
OpportunitiesBest practices to adopt
ThreatsCompetitor advantages

Output Formats

Narrative Summary

## Benchmarking Summary

**Subject:** [What was benchmarked]
**Date:** [ISO date]
**Type:** [Internal/Competitive/Functional/Strategic]
**Analyst:** benchmarking-analyst

### Executive Summary

[2-3 sentence overview of key findings]

### Benchmarking Partners

| Partner | Type | Why Selected |
|---------|------|--------------|
| [Partner 1] | [Type] | [Reason] |
| [Partner 2] | [Type] | [Reason] |

### Key Findings

#### Gap 1: [Area]
- **Our Performance:** [Value]
- **Benchmark:** [Value]
- **Gap:** [Delta]
- **Root Cause:** [Why]
- **Best Practice:** [What leaders do]

#### Gap 2: [Area]
[Same structure]

### Recommendations

| Priority | Gap | Action | Impact | Effort |
|----------|-----|--------|--------|--------|
| 1 | [Gap] | [Action] | High | Medium |
| 2 | [Gap] | [Action] | Medium | Low |

### Next Steps

1. [Immediate action]
2. [Short-term action]
3. [Long-term initiative]

Structured Data (YAML)

benchmarking:
  version: "1.0"
  date: "2025-01-15"
  subject: "Customer Service Operations"
  type: "competitive"
  analyst: "benchmarking-analyst"

  partners:
    - name: "Company A"
      type: "direct_competitor"
      selection_reason: "Market leader"
    - name: "Industry Average"
      type: "industry_benchmark"
      source: "Gartner Report 2024"

  metrics:
    - name: "First Response Time"
      category: "speed"
      our_performance:
        value: 24
        unit: "hours"
      benchmark:
        value: 4
        unit: "hours"
        source: "Company A"
      gap:
        absolute: 20
        percentage: 500
      priority: "critical"

    - name: "Customer Satisfaction"
      category: "quality"
      our_performance:
        value: 78
        unit: "percent"
      benchmark:
        value: 92
        unit: "percent"
        source: "Industry Average"
      gap:
        absolute: -14
        percentage: -15
      priority: "high"

  findings:
    - gap: "First Response Time"
      root_cause: "Manual ticket routing, no AI triage"
      best_practice: "AI-powered auto-routing and chatbot first response"
      impact: "high"
      effort: "medium"

  recommendations:
    - priority: 1
      gap: "First Response Time"
      action: "Implement AI ticket triage"
      owner: "Support Director"
      timeline: "Q2 2025"
      expected_improvement: "80% reduction"
      investment: "$50,000"

  targets:
    - metric: "First Response Time"
      current: 24
      target: 4
      timeline: "6 months"
    - metric: "Customer Satisfaction"
      current: 78
      target: 90
      timeline: "12 months"

Comparison Table

## Competitive Comparison

| Dimension | Us | Competitor A | Competitor B | Industry Avg | Best-in-Class |
|-----------|---:|-------------:|-------------:|-------------:|--------------:|
| Response Time | 24h | 8h | 12h | 10h | 1h |
| Resolution Rate | 78% | 85% | 82% | 80% | 95% |
| Cost per Ticket | $45 | $35 | $40 | $38 | $20 |
| NPS Score | 32 | 45 | 38 | 35 | 72 |

**Legend:** Green = above average, Yellow = average, Red = below average

Gap Visualization

xychart-beta
    title "Performance vs Benchmark"
    x-axis ["Response Time", "Resolution", "Cost", "NPS"]
    y-axis "Performance (% of benchmark)" 0 --> 150
    bar [25, 82, 88, 44]
    line [100, 100, 100, 100]

Benchmarking Ethics

Do's

  • Use publicly available information
  • Get permission for site visits/interviews
  • Share appropriately if participating in consortium
  • Protect confidential information
  • Give credit to sources

Don'ts

  • Use deceptive practices to gather data
  • Violate NDAs or trade secrets
  • Misrepresent benchmarking data
  • Use competitive intelligence unethically
  • Ignore legal and antitrust considerations

Common Pitfalls

PitfallPrevention
Wrong metricsAlign with strategic objectives
Poor partnersSelect truly best-in-class
Apples to orangesNormalize data carefully
Data without actionFocus on actionable insights
One-time exerciseContinuous improvement cycle
Copying blindlyAdapt to your context

Integration

Upstream

  • swot-pestle-analysis - Strategic context
  • stakeholder-analysis - Who cares about benchmarks
  • Requirements - Performance requirements

Downstream

  • Gap analysis - Improvement priorities
  • prioritization - Resource allocation
  • Roadmap - Improvement initiatives

Related Skills

  • swot-pestle-analysis - Strategic environmental analysis
  • prioritization - Prioritizing improvement actions
  • decision-analysis - Evaluating improvement options
  • capability-mapping - Capability maturity benchmarking

Version History

  • v1.0.0 (2025-12-26): Initial release

平台分布

Antigravity

29.49%
按下载量换算41

Claude Code

21.77%
按下载量换算30

windsurf

17.04%
按下载量换算24

trae

11.92%
按下载量换算17

OpenCode

7.91%
按下载量换算11

Gemini CLI

3.18%
按下载量换算4

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills