CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-skill

Scaffolds, diagnoses, and prunes agent skills. Modes: `scaffold` (default — runs the job once without a skill on a real input, records every correction, then writes a skill made of only those corrections), `diagnose` (retrospective failure analysis that emits a confidence-gated unified diff against any skill declaring a diagnostic surface), `prune` (deletes unused skills and trims or deletes those whose with/without-skill eval shows no lift over a same-length dummy). Triggers on "create a skill", "scaffold a skill", "new SKILL.md", "diagnose this skill", "why did the skill miss this", "prune my skills", "clean up my skills", "/create-skill".

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a dense, highly actionable orchestration document with gated phases, explicit validation and feedback loops, and disciplined on-demand loading — the conciseness and workflow quality of a top-tier skill. Its one real defect is bundle completeness: most of the rules/ and templates/ files it points to are not present, which undercuts the otherwise excellent progressive-disclosure design.

Suggestions

Ship the referenced rules/ and templates/ files with the bundle (or inline the few the workflow cannot run without, e.g. run-first.md Steps 1–2), since the Required Reading table and most in-body links currently point to files that are not present.

Fold 'Core Principles' into the phase sections that already operationalize it (Phases 1–3 carry the run-first and traceability rules) to reclaim tokens without losing guidance.

Trim the Diagnose section's prose describing the diagnostic-surface contract to a one-line pointer, since rules/diagnostic-surface.md and templates/diagnostic-surface.template.md are already linked there.

DimensionReasoningScore

Conciseness

The body assumes competence ('Detailed rules live in `rules/*.md` and templates in `templates/*.md`; load them on demand') with no basic-concept explanations, but 'Core Principles' restates rules already embedded in Phases 1–3 ('A skill is the list of what the agent got wrong') and the diagnose section inlines contract detail ('phase model, failure taxonomy, existing-guards table, source root, hard invariants') that its referenced file carries. This is the 4 anchor — efficient with minor instances that could be trimmed — rather than the every-token-earns-its-place 5.

4 / 5

Actionability

Guidance is fully executable: exact commands ('node ${CLAUDE_SKILL_DIR}/scripts/validate-skill.mjs <dir> [--portable]', 'claude -p "/skill-doctor"', 'bash scripts/sync-symlinks.sh'), concrete ledger paths ('.agent/{branch}/skill-run-<task-slug>.md'), expected output strings ('Self-check: FAIL — 1 failing', 'Verify: PASS — fresh run, 0 of <n> corrections recurred'), plus a ledger-routing table and wrong/right examples. Matches the copy-paste-ready 5 anchor; the minor deferral of procedure detail to referenced files is standard progressive disclosure, not a gap.

5 / 5

Workflow Clarity

All three workflows have a gated phase table ('The job ran on the real input with no skill and passes its definition of done… every correction is in the ledger'), explicit validation checkpoints (Phase 4 validate PASS, Phase 5 fresh-run verify), a concrete error-recovery loop ('A recurring correction means the line meant to prevent it is wrong or missing: fix that line and re-run once'), and per-mode Definition-of-Done checklists. Destructive prune operations are gated by 'the user's explicit yes per skill' with caller migration, so the destructive-op cap does not bind.

5 / 5

Progressive Disclosure

The in-body structure is excellent — one-level-deep links and a 'Required Reading by Phase' table with 'Load these on demand — do not preload them all' — and the files that do ship (references/run-first-rationale.md, references/lift-and-prune-rationale.md, scripts/validate-skill.mjs) all resolve. However, the majority of referenced paths (rules/run-first.md, rules/diagnose-mode.md, templates/SKILL.minimal.md, and 10+ other rules/ and templates/ files) are absent from the provided bundle, so most navigation pointers break. Not a 4 because the gap is not minor; not a 2 because the body's own signaling is clear and the core workflow remains usable inline.

3 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a model example: third-person voice, concrete per-mode mechanics, and an explicit eight-phrase trigger list that doubles as the 'when to use' guidance. It is dense but every clause carries capability information rather than padding.

DimensionReasoningScore

Specificity

All three modes are given concrete mechanics — 'runs the job once without a skill on a real input, records every correction, then writes a skill made of only those corrections', 'emits a confidence-gated unified diff', and 'trims or deletes those whose with/without-skill eval shows no lift over a same-length dummy' — which is comprehensive coverage of specific actions, not just the 1-2 actions of the 3-anchor or the minor gaps of the 4-anchor.

5 / 5

Completeness

Both questions are answered explicitly: 'what' is the three-mode capability breakdown with mechanics, and 'when' is the dedicated 'Triggers on …' clause with concrete trigger phrases — exactly the 5-anchor pattern ('what AND when with concrete trigger phrases'). The missing-'Use when' cap does not apply since explicit trigger guidance is present.

5 / 5

Trigger Term Quality

The explicit trigger list — "create a skill", "scaffold a skill", "new SKILL.md", "diagnose this skill", "why did the skill miss this", "prune my skills", "clean up my skills", "/create-skill" — covers natural phrasings a user would actually say, with synonyms across all three modes plus the slash command. Not a 4: synonym variations and the artifact name (SKILL.md) are present, matching the comprehensive 5 anchor.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear meta-niche (scaffolding, hardening, and pruning agent skills) with mode-specific trigger phrases, so overlap with ordinary task skills is minimal — the 5 anchor's 'clear niche with distinct triggers'. Not a 4: no closely related skill would naturally claim this trigger set.

5 / 5

Total

20

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 16 missing

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

12

/

16

Passed

Repository

mthines/agent-skills

Path

skills/authoring/create-skill/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.