Token导航 LogoToken导航TokenDH.com
开发执行命令github未标认证来源可访问许可证需确认审计异常

evaluate-skill评估技能

Agent Skill

evaluate-skill 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

291

周安装

12

GitHub Stars

28

下载量

95
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/laurigates/claude-plugins --skill evaluate-skill

简介

evaluate-skill 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。

  • 它可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 当前顶部介绍为空,需参考原始 SKILL.md 进一步了解功能细节。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

/evaluate:skill

Evaluate a skill's effectiveness by running behavioral test cases and grading the results against assertions.

When to Use This Skill

Use this skill when...Use alternative when...
Want to test if a skill produces correct resultsNeed structural validation -> scripts/plugin-compliance-check.sh
Validating skill improvements before mergingWant to file feedback about a session -> /feedback:session
Benchmarking a skill against a baselineNeed to check skill freshness -> /health:audit
Creating eval cases for a new skillWant to review code quality -> /code-review

Context

  • Skill files:!bash ${CLAUDE_PLUGIN_ROOT}/scripts/inspect_eval.sh --plugin-dir $1

Parameters

Parse these from $ARGUMENTS:

ParameterDefaultDescription
<plugin/skill-name>requiredPath as plugin-name/skill-name
--create-evalsfalseGenerate eval cases if none exist
--runs N1Number of runs per eval case
--baselinefalseAlso run without skill for comparison

Execution

Step 1: Resolve skill path

Parse $ARGUMENTS to extract <plugin-name> and <skill-name>. The skill file lives at:

<plugin-name>/skills/<skill-name>/SKILL.md

Read the SKILL.md to confirm it exists and understand what the skill does.

Step 2: Run structural pre-check

Run the compliance check to confirm the skill passes basic structural validation:

bash scripts/plugin-compliance-check.sh <plugin-name>

If structural issues are found, report them and stop. Behavioral evaluation on a structurally broken skill is wasted effort.

Step 3: Load or create eval cases

Look for <plugin-name>/skills/<skill-name>/evals.json.

If the file exists: read and validate it against the evals.json schema (see evaluate-plugin/references/schemas.md).

If the file does not exist AND --create-evals is set: Analyze the SKILL.md and generate eval cases:

  1. Read the skill thoroughly — understand its purpose, parameters, execution steps, and expected behaviors.
  2. Generate 3-5 eval cases covering:

- Happy path: Standard usage that should work correctly - Edge case: Unusual but valid inputs - Boundary: Inputs that test the limits of the skill's scope

  1. For each eval case, write:

- id: Unique identifier (e.g., eval-001) - description: What this test validates - prompt: The user prompt to simulate - expectations: List of assertion strings the output should satisfy - tags: Categorization tags

  1. Write the generated cases to <plugin-name>/skills/<skill-name>/evals.json.

If the file does not exist AND --create-evals is NOT set: Report that no eval cases exist and suggest running with --create-evals.

Step 4: Run evaluations

For each eval case, for each run (up to --runs N):

  1. Scaffold the run directory and record the start time by running: bash ${CLAUDE_PLUGIN_ROOT}/scripts/prepare_run.sh \ --skill-dir <plugin-name>/skills/<skill-name> \ --eval-id <eval-id> --run <N> Parse RUN_DIR=, MANIFEST=, and STARTED_AT= from output.
  2. Spawn a Task subagent (subagent_type: general-purpose) that:

- Receives the skill content as context - Executes the eval prompt - Works in the repository as if it were a real user request

  1. Capture the subagent output.
  2. Record timing data (duration) and write to $RUN_DIR/timing.json.
  3. Write the transcript to $RUN_DIR/transcript.md.

Step 5: Run baseline (if --baseline)

If --baseline is set, repeat Step 4 but without loading the skill content. Pass --baseline to prepare_run.sh so results are written into a parallel baseline/ subdirectory. This creates a comparison point to measure skill effectiveness.

Use the same eval prompts and record results in the baseline/ subdirectory.

Step 6: Grade results

For each run, delegate grading to the eval-grader agent via Task:

Task subagent_type: eval-grader
Prompt: Grade this eval run against the assertions.
  Eval case: <eval case from evals.json>
  Transcript: <path to transcript.md>
  Output artifacts: <list of created/modified files>

The grader produces grading.json for each run.

Step 7: Aggregate and report

Compute aggregate statistics across all runs:

  • Mean pass rate (assertions passed / total assertions)
  • Standard deviation of pass rate
  • Mean duration

If --baseline was used, also compute:

  • Baseline mean pass rate
  • Delta (improvement from skill)

Write aggregated results to <plugin-name>/skills/<skill-name>/eval-results/benchmark.json.

Print a summary table:

## Evaluation Results: <plugin/skill-name>

| Metric | With Skill | Baseline | Delta |
|--------|-----------|----------|-------|
| Pass Rate | 85% | 42% | +43% |
| Duration | 14s | 12s | +2s |
| Runs | 3 | 3 | — |

### Per-Eval Breakdown

| Eval | Description | Pass Rate | Status |
|------|-------------|-----------|--------|
| eval-001 | Basic usage | 100% | PASS |
| eval-002 | Edge case | 67% | PARTIAL |
| eval-003 | Boundary | 100% | PASS |

Agentic Optimizations

ContextCommand
Inspect skill eval setupbash evaluate-plugin/scripts/inspect_eval.sh --plugin <plugin> --skill <skill>
Print evals JSONbash evaluate-plugin/scripts/inspect_eval.sh --plugin <plugin> --skill <skill> --print-evals
Prepare a run directorybash evaluate-plugin/scripts/prepare_run.sh --skill-dir <plugin>/skills/<skill> --eval-id <id> --run <N>
Aggregate resultsbash evaluate-plugin/scripts/aggregate_benchmark.sh <plugin>

Quick Reference

FlagDescription
--create-evalsGenerate eval cases from SKILL.md analysis
--runs NNumber of runs per eval case (default: 1)
--baselineRun without skill for comparison

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

40.67%
按下载量换算39

Claude

28.55%
按下载量换算27

Cursor

17.78%
按下载量换算17

Gemini CLI

10.53%
按下载量换算10

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/laurigates/claude-plugins --skill evaluate-skill 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills