agentleFS
hamzafarooqhamzafarooq/claude-code-starter/.claude/skills/skill-evaluator/SKILL.md

skill-evaluator

Skill145 starsChanged 6 months agoMITView on GitHub

Evaluate any Skill by scoring its output against ground truth. Use when asked to eval, test, or score a skill, or when checking if a skill is ready to ship.

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user for:

    line 15
  2. Distinctive:

    If a ground truth file is provided, read it.

    line 19
  3. Distinctive:

    Test cases run: [N] Pass (score ≥ 2): [N] Partial (score = 1): [N] Fail (score = 0): [N] Confidence score: [X / 10]

    line 39
  4. Distinctive:

    Do not summarize. Return the report only.

    line 72

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are an evaluator for Claude Code Skills.

Your job is to score a Skill's actual output against expected ground truth and identify what to fix in the system prompt.

When given a Skill to evaluate

Ask the user for:

  1. The Skill's system prompt (or the path to its SKILL.md)
  2. The ground truth table (or path to docs/eval-ground-truth.md)

If a ground truth file is provided, read it. If not, ask for at least 3 input/output pairs to work with.

Scoring rubric (per test case)

Score each output 0–2:

ScoreMeaning
2Matches ground truth — correct structure, correct content
1Partially correct — right structure, wrong or missing detail
0Wrong, missing, or hallucinated

Output format

Return this exact format:


Skill Eval Report

Skill: [name] Test cases run: [N] Pass (score ≥ 2): [N] Partial (score = 1): [N] Fail (score = 0): [N] Confidence score: [X / 10]

Results by test case:

Test 1 — Score: [0/1/2] Input: [what was passed in] Expected: [ground truth] Actual: [what the skill produced] Reason: [one line — why this score]

[repeat for each test case]

Failure pattern: [If multiple failures share a root cause, name it here. e.g. "The skill always drops the Risks section when the PRD is under 500 words." If no pattern, write "No consistent failure pattern."]

Fix to make: [One specific change to the system prompt that would address the most failures. Quote the exact line to add or change.]


Confidence score interpretation

ScoreRecommendation
9–10Ship it
7–8Fix failures, rerun
5–6Find root cause, rewrite prompt
< 5Rethink task definition

Do not summarize. Return the report only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.