test-packaged-skills

Validates packaged composition skills structurally and runs live end-to-end dispatch tests.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/ensj/skill-eval-framework --skill test-packaged-skills-ensj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-packaged-skills
Source: https://github.com/ensj/skill-eval-framework/tree/main/.claude/skills/test-packaged-skills
Command: npx skills add https://github.com/ensj/skill-eval-framework --skill test-packaged-skills-ensj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Packaged composition skills (packaged/*/SKILL.md) can drift from what was actually measured during evaluation, and there is no guarantee their prose, steps, and quality bars still hold when executed. This Skill closes that gap by validating each packaged skill's structure cheaply and, when requested, executing it end-to-end exactly as it ships. ## Core Features & Use Cases - Structural validation: Runs node dist/e2e/cli.js --validate to check every packaged SKILL.md is well-formed, printing OK/FAIL per file with no agent spend. - Live dispatch E2E: Parses each packaged skill, writes per-case assertions files, and invokes the dispatch runner so one subagent executes each step on its declared _Model:_ model, honoring the tested == shipped == measured principle. - Scored verdicts: Scores each run against embedded assertions and the stamped quality bar, writes a per-case report.md, and reports an overall PASS/FAIL with failing cases. - Use Case: After editing a packaged composition skill, ask for a live E2E run to confirm the shipped artifact still passes its assertions and quality bar before releasing it. ## Quick Start Run the structural validation across all packaged skills and report which ones pass or fail.

Frequently Asked Questions about test-packaged-skills

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

FAQPage Schema
How do I test packaged skills end to end?▼

Ask for a live or full E2E run. The Skill parses each packaged SKILL.md, writes per-case assertions.yaml files, and invokes the dispatch runner so each step executes on its declared model, then reports a PASS/FAIL verdict per skill.

How do I validate packaged SKILL.md files without running agents?▼

Use structural mode, which is the default. It runs node dist/e2e/cli.js --validate, prints OK or FAIL for each packaged/*/SKILL.md, and exits non-zero if any file fails, with no agent spend.

What is the difference between dispatch mode and the inline runner?▼

Dispatch mode runs one subagent per step on each step's declared model and is the canonical execution matching what ships. The inline runner exists only to explicitly validate a single-model skill's inline opt-in and should be used only when asked.

Why does the packaged skill test fail before running anything?▼

The Skill requires running npm run build first from the skill-eval-framework root. The build emits dist/e2e/cli.js, dist/scorer/cli.js, and the patterns/test-packaged scripts that both structural and live modes depend on.

What happens when a scorer output is missing or malformed?▼

A tuple with missing or malformed scorer output counts as a failure rather than being scored zero. It is excluded from the quality mean, listed in the failures output, and forces the overall skill_pass verdict to false.