domains / agent-tooling / skill-evaluation / eval

eval

Skill card

combined

The two copies describe fundamentally different evaluation methodologies. The first (dzhng/skills) is a qualitative, agent-driven process: it uses fresh, context-free subagents to run a skill blind on golden cases, then uses a separate judge agent to grade the artifact against a 'bar' and 'smells' to drive iterative skill edits. The second (LeoYeAI/openclaw-master-skills) is a quantitative, CLI-based framework: it uses a command-line tool (`eval-skills`) to run benchmarks, score results with specific scorers (e.g., `exact`), and generate reports for CI/CD gates. They do not overlap in procedure; one is a manual/agent workflow for improvement, the other is an automated testing framework for quality assurance.

Repositories

RepositoryPath
dzhng/skillsskills/authoring/eval-skills/SKILL.md
LeoYeAI/openclaw-master-skillsskills/eval-skills/SKILL.md

Other copies

RoleRepositoryPath
peerdzhng/skillsskills/authoring/eval-skills/SKILL.md
peerLeoYeAI/openclaw-master-skillsskills/eval-skills/SKILL.md

Combined skill

# Eval Skills

This skill covers two complementary approaches to evaluating AI agent skills: a qualitative improvement loop and a quantitative testing framework.

## Approach 1: Qualitative Improvement Loop (Agent-Driven)
Use this when you want to test, improve, or harden a specific skill based on its judgment quality.

1. **Validate Inputs**: Ensure you have the target `SKILL.md`, at least one golden case (concrete input), and a clear 'bar' (outcome + smells) for each case.
2. **Blind Run**: Spawn a fresh, context-free subagent for each case. Give it only the input and the instruction to use the target skill. Isolate the run (e.g., sandbox dir) and sweep the live checkout afterward.
3. **Grade**: Use a separate judge agent to grade the artifact against the bar and the skill's first principles. The judge must cite specific evidence.
4. **Account for Nondeterminism**: Re-run borderline cases 2-3 times to establish a pass rate.
5. **Diagnose & Revise**: Determine if failures are skill defects or bad cases. Fix skill defects using authoring principles (e.g., sharpen completion criteria).

## Approach 2: Quantitative Testing Framework (CLI-Based)
Use this for pre-production quality gates, CI/CD enforcement, or comparing candidate skills on benchmarks.

1. **Find/Scaffold**: Use `eval-skills find` to search for skills or `eval-skills create` to generate a skeleton with starter tests.
2. **Evaluate**: Run `eval-skills eval` with specific skills, benchmarks, and scorer types (e.g., `exact`). Configure concurrency, timeouts, and retries.
3. **Select/Report**: Use `eval-skills select` to rank skills based on reports. Generate human-readable reports (JSON, Markdown, HTML) for analysis.
4. **CI/CD Integration**: Use `--exit-on-fail` and `--min-completion` to block merges that degrade skill quality.