Claude, Form Generation.
Liam breaks down why a Claude Skill named form-generation is a specification, a checklist of fields read from one file, rather than any new drafting ability, and what that distinction means in practice.
Seeing Claude fill out a legal form using something called a form-generation skill looks like a drafting upgrade, as if Claude gained the ability to compose forms from scratch. Liam explains why that read is wrong, and what a "skill" named form-generation actually consists of: a fixed checklist, not new talent.
What changes when the skill folder is deleted
The clearest way to see what a skill is not comes from removing it. Delete the skills folder and Claude can still write a sentence, still draft language, still respond to a request. What it loses is the one fixed checklist of fields for that particular form. Nothing about Claude's underlying drafting ability changes, because that ability was never stored in the skill folder to begin with. The skill only ever held instructions, not capability.
A skill is one file: SKILL.md
A skill folder holds a single file, SKILL.md, containing plain-language instructions for which fields a form needs and where the relevant facts should go. Claude reads that file top to bottom before it starts and fills each field in the order the file lists, with no branching unless the file itself calls for one. The file is the entire mechanism. There is no separate reasoning layer beyond following that list in sequence.
Specification, not drafting power
This makes a skill a specification rather than a source of drafting power. The payoff is consistency: the same field layout comes out every time the skill runs, on every form it covers. The limit is just as concrete: any field the file never listed is a field Claude has no instructions for, and the skill does nothing to help there. A form-generation skill never taught Claude how to draft a legal document from nothing; it guarantees that every run reads the same checklist and fills the same fields in the same order.
Why watching one run does not prove understanding
Watching Claude produce a clean, correctly filled form does not prove it understood the underlying request. It may simply have followed the checklist correctly on a case that happens to fit the checklist's assumptions. The reverse is equally true: watching Claude leave a field wrong or empty does not prove the skill is broken. It may be a case the checklist was never written to cover in the first place. Neither a clean run nor a flawed run is, by itself, evidence about the skill's quality or about Claude's comprehension of the request.
What this means for using skills on real forms
Because a skill is a specification, its usefulness depends entirely on how complete and accurate that specification is for the form or document type it targets. Someone wanting the same consistency for a form they fill out repeatedly can write their own SKILL.md: a plain-language list of fields, in order, describing exactly what each one needs. Claude then reads that list before acting, the same way it does with any other skill, and every run comes out with the same structure.
Key takeaways
- A Claude Skill folder like form-generation is a specification, a checklist of fields, not a source of new drafting ability.
- Deleting the skill folder does not remove any drafting capability; Claude can still write, it just stops following that specific fixed checklist.
- The skill consists of one file, SKILL.md, read top to bottom, with fields filled in the listed order and no branching unless instructed.
- The payoff is consistent field layout across every run; the limit is any field the file never documented.
- A clean form fill does not prove understanding, and a flawed one does not prove the skill is broken; both depend on whether the checklist covers that case.
Who this is for
This is for anyone using or building Claude Skills for repetitive form-filling or document-drafting tasks who wants a clear picture of what a skill actually guarantees before relying on it.
Chapters
- 0:00The naive framing: "Claude designed the form"
- 0:12Sounds like a drafting upgrade
- 0:22Broken, with a case — delete the folder, nothing is forgotten
- 0:32The anchor: one file — form-generation's single SKILL.md
- 0:46Read it, then fill it in order
- 0:54Spec, not power — the payoff and the limit
- 1:05The anchor returns — same file, every run
- 1:18Both directions — neither one is proof
- 1:35Carry-out
- 1:46Your turn
Full transcript(auto-generated, with timestamps)
The naive framing: "Claude designed the form"
[0:00]You guess Claude designed the legal form itself using a skill called form generation. It didn't. It was handed a file of instructions. Form generation just names one such file. Let's see what's actually inside it. Here, Claude
Sounds like a drafting upgrade
[0:12]Has a form generation skill and it sounds like a drafting upgrade, like it can compose any legal form from a blank page. But nothing about drafting changes. Delete the skills folder and
Broken, with a case — delete the folder, nothing is forgotten
[0:23]Claude can still write a sentence. It just stops following that one fixed checklist of fields for this particular form. Here's what a skill actually is. One file form generation, for instance,
The anchor: one file — form-generation's single SKILL.md
[0:34]Is a folder holding a single skill. MD, instructions for which fields a form needs and where the case facts go, written in plain language Claude reads before it starts. Claude reads that file top to bottom and fills each field in
Read it, then fill it in order
[0:47]The order it's listed. No branching unless the file itself says branch. That makes a skill a specification, not drafting talent. The payoff, the same
Spec, not power — the payoff and the limit
[0:56]Field layout, every form, the limit, any field, the file never listed, and Claude has no instructions for it. So, form generation never taught Claude how to draft a legal document from nothing. It
The anchor returns — same file, every run
[1:07]Just guarantees that every time it runs, Claude reads that same checklist and fills the same fields in the same order. That's the whole trick. Watching Claude fill out a clean form doesn't prove it
Both directions — neither one is proof
[1:18]Understood the underlying request. It may have just followed the checklist on a case it never really parsed. And watching it leave a field wrong or empty doesn't prove the skill is broken. It may be a case that checklist doesn't cover. A skill doesn't teach Claude to draft a legal document from nothing. It's a checklist of fields Claude reads
Carry-out
[1:36]Before it starts. So every form comes out with the same structure every time. Your turn. Paste this into Claude. Pick one form or document I fill out the same way every time. Write me a skill. MD for
Your turn
[1:48]It. Plain language. the fields in order. Then read it back to me and walk me through exactly what you'll do before you do it. Claude form generation. Lay them in for bear.
