Clay skill author

The insight: a Clay table records mechanics and cannot record intent. A formula proves the threshold is 50; nothing in the table says why 50, what the column was for, or when to ignore it. So a converter that reads a table and emits a skill produces something fluent, plausible and unfounded — and it reads better than a real one, because nothing in it hedges.

What follows from that is the shape of this whole flow: derive everything derivable first, then ask only about what the derivation could not settle. Asking before reading wastes the creator's time on questions the table already answers, and an ungrounded question — "what's the non-obvious thing here?" — invites a shrug. People correct a draft far better than they answer a question about one.

Step 0 — Announce, then say what is about to happen

First line of output, before anything else:

clay-skill-author/2.25.1 · loaded from <absolute path to this SKILL.md>