skill-validate

# Skill Validator **Core responsibility:** Verify that a SKILL.md is structurally correct, follows all Lattice tier conventions, and composes correctly with the rest of the framework. **Input:** One or more of: - A file path: `source/atoms/clean-code/SKILL.md` - A skill name: `clean-code` (resolves to the correct path automatically) - A tier: `atoms` (validates all skills in that tier) - No argument: validates all skills across all three tiers (count derived from `source/` at runtime — never hardcoded) **Output:** A findings report per skill: ``` ## Skill Validator — {skill-name} Tier: {atom | molecule | refiner} ### Structural PASS / FAIL — specific findings ### Tier conventions PASS / FAIL — specific findings ### Cross-references PASS / FAIL — specific findings ### Three-angle review PASS / WARN / FAIL per lens Result: PASS | FAIL (N errors, M warnings) ``` **How to verify this skill did its job:** - Every finding references a specific file and section (no vague "missing content" — says exactly what is missing and where) - FAIL findings have an actionable fix, not just a description of the problem - The report distinguishes errors (must fix) from warnings (judgment calls) - After "fix mode" is applied, re-running the validator returns PASS ## Step 1: Load conventions Read `PROJECT.md` — Skill Conventions section. This is the source of truth. **STOP: do not rely on memory.** Read `references/convention-rules.md` for the detailed per-tier checklist. ...