write-a-skill

Skill authoring loop: gather requirements, draft against the SKILL.md contract, review with the user, refine. One concern per skill; one skill per directory. Apply the skill-creator:skill-creator methodology (three-level progressive disclosure, pushy descriptions, evals.json).

Scope disambiguation

• write-a-skill — authors one SKILL.md for one capability inside an existing skills tree.
• Repo onboarding — onboards a whole repository, scaffolds AGENTS.md and project conventions.
• skill-creator:skill-creator — the upstream methodology this skill applies; consult it for the canonical contract.

Authoring loop

1. Gather requirements — surface decisions before drafting:

   • Capability boundary: what task does the skill cover, what does it explicitly not cover?
   • Trigger phrases: which user phrases or contexts should load it?
   • Determinism: any operation deterministic enough to live in a script rather than re-generated prose?
   • Bundled references: docs, schemas, or examples to include?
   • Static guarantee context: language family (Rust, TypeScript, Python, Kotlin, Go, OCaml, …) — affects testing-charter scope.

2. Draft the SKILL.md — write to the contract below. Keep body terse and decision-oriented.