Write Best Practice Skill

Author a new grimoire SKILL.md that encodes a domain best practice and passes review-best-practice-skill.

Why This Is Best Practice

Adopted by: Structured authoring guides are standard in high-quality OSS knowledge projects — Wikipedia's Manual of Style, MDN Web Docs contributor guide, and all major package registries provide explicit authoring templates to maintain quality at scale. Impact: Defects caught at authoring time cost 5–10× less to fix than those caught at review — a principle established in software engineering (Boehm, Software Engineering Economics, 1981) that applies equally to knowledge contributions. Wikipedia's Manual of Style, applied at authoring time, contributes to Featured Articles achieving measurably higher quality benchmarks (citation density, edit stability) than non-featured articles — a direct effect of structured authoring criteria applied before submission. Why best: An explicit authoring guide — vs. ad-hoc contribution where authors discover requirements through reviewer rejection — eliminates the most common failure modes (vague "Adopted by", missing impact numbers, over-scoped skills) before a reviewer ever sees the file.