skill-evaluation

Evaluates agent skills with realistic prompts, shared rubrics, and blinded candidate comparison.

2|Updated May 14, 2026
One-click install
npx skills add https://github.com/AnthonyPoschen/agent-skills --skill skill-evaluation-anthonyposchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-evaluation
Source: https://github.com/AnthonyPoschen/agent-skills/tree/main/skills/skill-evaluation
Command: npx skills add https://github.com/AnthonyPoschen/agent-skills --skill skill-evaluation-anthonyposchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It is hard to know whether a new or changed agent skill actually improves agent behaviour, since convincing instructions and self-reported compliance are not evidence. This Skill provides a structured evaluation workflow that produces real evidence about triggering accuracy and task outcomes. ## Core Features & Use Cases - Triggering Evaluation: Test a skill description against realistic prompts that should and should not trigger it, recording expected versus actual results. - Blinded Candidate Comparison: Run the new skill, old skill, or a no-skill baseline on identical tasks, hide candidate identities, and judge artifacts against a shared rubric. - Rubric and Decision Guidance: Write short observable rubrics and reach a clear decision to keep, revise, remove, or gather more evidence. - Use Case: After rewriting a technical-writing skill, run both versions on three real documentation tasks, blind the outputs, score them against a rubric covering factual accuracy and clarity, and decide whether the change ships. ## Quick Start Use the skill-evaluation skill to compare my new skill version against the old one on three realistic tasks with a shared rubric and blinded review.

Frequently Asked Questions about skill-evaluation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether an agent skill actually works?▼

Evaluate an agent skill by running candidates on the same realistic tasks with identical inputs and constraints, then judging the produced artifacts against a short shared rubric. Hide candidate identities before review so you judge the work, not the skill's claims.

How do I test if a skill triggers at the right time?▼

Test triggering separately by writing a small set of realistic prompts, including some that should trigger the skill and some that should not. For each prompt, record whether it should trigger, whether it did, and why the result was correct or incorrect.

What makes a good rubric for comparing skill outputs?▼

A good rubric is short, task-specific, and uses observable criteria such as factual correctness, scope control, and verification evidence. Avoid rubrics that reward a candidate for repeating the skill's own instructions or rely on word counts for subjective work.

When should I skip running a full skill evaluation?▼

Skip evaluation for small wording changes unless the change carries meaningful uncertainty or risk. Reserve full evaluations for new public skills, meaningful changes to existing skills, or skills that trigger at the wrong time or produce poor work.

Why should candidate identities be hidden during skill review?▼

Blinding prevents bias toward the new or preferred skill when judging artifacts. Reading the actual work and its verification evidence, rather than an agent's summary of intent, keeps the comparison grounded in observable outcomes.