技能 基准测试
- 作者仓库星标 498
- 作者仓库 agent-skills-standard
Skill Benchmark Skill
[!IMPORTANT] Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.
Instructions
When the user asks to perform this workflow, execute the following steps:
📊 Skill Benchmark Orchestrator
Goal: Quantify how much active skills improve implementation quality. Deliver a prioritized compliance delta and skill applicability report.
Step 1 — Project Context & Active Skills
Identify the tech stack and all active skills in AGENTS.md.
# 1. Total source files and lines changed
find src -name "*.ts" -o -name "*.tsx" | xargs wc -l 2>/dev/null | sort -rn | head -20
# 2. Check active skill registry
cat AGENTS.md | head -80Step 2 — Auto-Select a Legacy Trap
Pick the file automatically. Rank candidates by the severity of anti-patterns:
- 🔴 P0: Hardcoded secrets; Logic inside UI components.
- 🟠 P1: Wrong Router pattern; Global state for local concerns; Missing design tokens.
- 🟡 P2: Raw user-facing strings (i18n).
Step 3 — Build Eval-Driven Scorecard
Source your scorecard from evals/evals.json, not from hardcoded patterns.
Follow the Scorecard Rubric in <SKILLS>/common/common-skill-creator/references/benchmark.md when synced:
- Read
<SKILLS>/<category>/<skill>/evals/evals.json. - Generate columns for Failure Pattern and Success Pattern.
- Refactor the file, citing the exact skill rule for each change.
Step 4 — Benchmark Report & Compliance Delta
Output the scorecard and compliant score using the templates in <SKILLS>/common/common-skill-creator/references/benchmark.md when synced.
- Compliance Score Before vs After.
- Δ Delta: +Z% 🚀.
- Eval Alignment: How well does the skill teach what the eval tests?
Step 5 — Skill Applicability & Iteration
For every ❌ FAIL, identify the root cause using the Iteration Table in:
<SKILLS>/common/common-skill-creator/references/benchmark.md when synced.
- Signal not matching file? → Refine trigger.
- Rule too vague? → Add Anti-Pattern rule.
- Conflict? → Ensure P0 overrides P1.
Suggested .skillsrc Exclusions
Recommend any skills that are noisy or non-applicable for the project.
exclude:
- [skill-id] # reason- 流狐分类
- 工程开发
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @HoangNguyen0403 · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 需简单配置
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。Identify the tech stack and all active skills in AGENTS.md.
Pick the file automatically. Rank candidates by the severity of anti-patterns: 🔴 P0: Hardcoded secrets; Logic inside UI components. 🟠 P1: Wrong Router pattern; Global state for local concerns; Missing design tokens.
Source your scorecard from evals/evals.json, not from hardcoded patterns. Follow the Scorecard Rubric in <SKILLS>/common/common-skill-creator/references/benchmark.md when synced: Read <SKILLS>/<category>/<skill>/evals/evals.json.
Output the scorecard and compliant score using the templates in <SKILLS>/common/common-skill-creator/references/benchmark.md when synced. Compliance Score Before vs After. Δ Delta: +Z% 🚀.
For every ❌ FAIL, identify the root cause using the Iteration Table in: <SKILLS>/common/common-skill-creator/references/benchmark.md when synced. Signal not matching file? → Refine trigger.
# Skill Benchmark Skill
> [!IMPORTANT]
> Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.
## Instructions
When the user asks to perform this workflow, execute the following steps:
# 📊 Skill Benchmark Orchestrator
> **Goal**: Quantify how much active skills improve implementation quality. Deliver a prioritized compliance delta and skill applicability report.
---
## Step 1 — Project Context & Active Skills
Identify the tech stack and all active skills in `AGENTS.md`.
```bash
# 1. Total source files and lines changed
find src -name "*.ts" -o -name "*.tsx" | xargs wc -l 2>/dev/null | sort -rn | head -20
# 2. Check active skill registry
cat AGENTS.md | head -80
```
---
## Step 2 — Auto-Select a Legacy Trap
Pick the file automatically. Rank candidates by the severity of anti-patterns:
- 🔴 **P0**: Hardcoded secrets; Logic inside UI components.
- 🟠 **P1**: Wrong Router pattern; Global state for local concerns; Missing design tokens.
- 🟡 **P2**: Raw user-facing strings (i18n).
---
## Step 3 — Build Eval-Driven Scorecard
Source your scorecard from `evals/evals.json`, not from hardcoded patterns.
Follow the Scorecard Rubric in `<SKILLS>/common/common-skill-creator/references/benchmark.md` when synced:
1. Read `<SKILLS>/<category>/<skill>/evals/evals.json`.
2. Generate columns for **Failure Pattern** and **Success Pattern**.
3. Refactor the file, citing the exact skill rule for each change.
---
## Step 4 — Benchmark Report & Compliance Delta
Output the scorecard and compliant score using the templates in `<SKILLS>/common/common-skill-creator/references/benchmark.md` when synced.
- **Compliance Score Before vs After**.
- **Δ Delta: +Z%** 🚀.
…作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> Instructions → Step 1 — Project Context & Active Skills → Step 2 — Auto-Select a Legacy Trap → Step 3 — Build Eval-Driven Scorecard → Step 4 — Benchmark Report & Compliance Delta → Step 5 — Skill Applicability & Iteration
要点 -> Goal · P0 · P1 · P2 · Failure Pattern · Success Pattern · Compliance Score Before vs After · Δ Delta: +Z%
文件/命令 -> AGENTS.md · evals/evals.json · <SKILLS>/common/common-skill-creator/references/benchmark.md · <SKILLS>/<category>/<skill>/evals/evals.json · ❌ FAIL
内容 SHA-256 -> 7e3e4a28268c
方法与流程
适用与边界
原文中的明确线索
AGENTS.md、evals/evals.json、<SKILLS>/common/common-skill-creator/references/benchmark.md、<SKILLS>/<category>/<skill>/evals/evals.json、❌ FAIL