namht-skillifylisted

# namht-skillify — create a new skill the right way Meta-skill: scaffold a new `namht-*` skill + command that matches this repo's standard, then wire and document it. Operate inside the `nam-claude-skill` repo (the toolkit source, e.g. `~/nam-claude-skill`). ## Steps 1. **Clarify** the new skill: name (kebab, will become `namht-<name>`), one-line purpose, when it should trigger, inputs, output, whether it needs the HTML renderer or the review checklist. 2. **Read [`docs/skill-anatomy.md`](../../docs/skill-anatomy.md) first** — it is the standard this step generates against: required sections in order, and the extra trailer (**Common rationalizations · Red flags · Verification**) that every high-stakes skill carries. A skill that edits code, or whose conclusions someone will act on, MUST have that trailer; `tests/consistency.test.sh` fails without it. 3. **Create `skills/namht-<name>/SKILL.md`** with frontmatter: - `name: namht-<name>` (MUST equal the folder name), `description: >-` a 1–3 sentence trigger description (when to use + key verbs/aliases). Body = the methodology, grounded in the KB where relevant, with a clear Output section and Rules. Reuse the house style: KB-first, dual-audience output, change-discipline if it edits code. 4. **Create `commands/<name>.md`** (UNPREFIXED filename) — thin entry: frontmatter `description` + `argument-hint`, body "Use the **namht-<name>** skill to … $ARGUMENTS". 5. **If it needs bundles** (HTML re