skill-creator

Create and iteratively improve agent skills using a test-first eval workflow.

4|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/exiao/meta-skills --skill skill-creator-exiao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/exiao/meta-skills/tree/main/skill-creator
Command: npx skills add https://github.com/exiao/meta-skills --skill skill-creator-exiao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Most agent skills are written once and never measured, so they fail unpredictably in production. This Skill enforces a test-driven workflow for building skills: write failing baseline tests before drafting, run evals, benchmark results, and iterate until the skill measurably works. ## Core Features & Use Cases - Test-first skill creation: Requires 3+ pressure scenarios run without the skill (RED phase) before writing any SKILL.md content, proving the skill is actually needed. - Eval and benchmark loop: Spawns with-skill and baseline runs, grades outputs against assertions, aggregates pass rates and token usage with scripts, and renders an HTML eval viewer for human review. - Description optimization: Generates trigger eval queries and runs an optimization loop to tune the frontmatter description for reliable skill triggering. - Use Case: You want to build a skill that formats sales spreadsheets. This Skill walks you through capturing intent, writing failing baseline tests, drafting the SKILL.md, running benchmark evals, and refining until pass rates improve. ## Quick Start Ask the agent to help you create a new skill for your workflow and it will guide you through baseline testing, drafting, and evaluation.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I create a new agent skill with a test-first workflow?▼

Start with the RED phase: write 3 or more realistic pressure scenarios and run them without the skill to document baseline failures. Only after documenting those failures do you draft the SKILL.md, then run with-skill evals and iterate on the results.

How do I test whether an agent skill actually works?▼

Save realistic test prompts to evals/evals.json, spawn with-skill and baseline runs, grade outputs against assertions using the grader agent, then aggregate results with the aggregate_benchmark script. Review everything in the generated HTML eval viewer before judging output yourself.

Why does my skill trigger eval score 0.00 on every query?▼

A uniform 0.00 usually means the harness is broken, not the description. Common causes are writing the probe to .claude/commands instead of .claude/skills, or a timeout too short for agentic runs. Run a known-good skill as a control to confirm.

How do I optimize a skill description for better triggering?▼

Generate 20 realistic trigger eval queries mixing should-trigger and should-not-trigger cases, review them with the user via the HTML template, then run the run_loop script which iterates on the description and selects the best by held-out test score.

What are the limits on SKILL.md size and structure?▼

Keep SKILL.md under 500 lines and 20KB, treating those as ceilings not targets. Move detailed guidance into the references directory and index every new reference file in SKILL.md so it stays reachable.