superstack-smithlisted

# superstack-smith The smith is a **gatekeeper, not a generator** — it exists to make a bad skill hard to add. The standing law is "no module without its trigger"; the smith is that law's door, mechanized. An idea that fails a gate parks in the queue with `revisit: <the evidence wanted>` — parking is a pass-through outcome, not a rejection. ## The admission gates, in order 1. **The evidence line — first, non-negotiable.** What recurring *moment*, observed *where* (sessions, logs, the user's own words, a hand-rolled workaround on disk). A hunch parks; observed recurrence proceeds. The strongest evidence is a workaround the user already built by hand — it proves demand *and* sketches the shape. 2. **The moment names its action class** — build / design / publish / resume / correction / broken-live / choosing / reporting-out — never a session size, never a topic. The taxonomy check runs here: **topics get review lenses or oracle rows; rules get lines in an existing skill; only moments get runners.** Check both cheaper homes before minting a skill. 3. **Collision check, mechanically.** Run it, don't recall it: ``` find skills ~/.claude/skills ~/.claude/plugins -name SKILL.md \ -exec grep -h '^description:' {} + 2>/dev/null ``` (`find` tolerates roots that don't exist on this machine — a shell glob does not: an unmatched glob aborts the whole command under zsh and returns a silent, empty "no collisions". Adjust roots as needed; follow symlinks to the real trees.