Claude, Draft.
Uses Claude's draft skill to show that a Claude Skill is a plain-language instruction file producing consistent document structure, not evidence Claude learned legal writing.
Claude has a skill called draft, and it's tempting to read that as Claude having learned legal writing. It hasn't. A Claude Skill is a folder holding one file, SKILL.md, that Claude reads before it starts and then follows step by step, in the order written. Delete the folder and Claude forgets no drafting ability, because there was nothing learned to begin with.
What the draft skill actually is
Draft is a folder holding a single SKILL.md: instructions, in plain language, for turning a user's facts and requests into a formatted document. Claude reads that file top to bottom and works through it step by step in the order written, branching only where the file itself says to. Nothing about this involves Claude drawing on some internalized sense of legal style; it involves following a written structure.
Specification, not power
This makes a skill a specification rather than a new writing capability. The payoff is consistency: the same document structure comes out every time draft runs. The limit is scope: anything outside those written steps and Claude is working without guidance. Draft never taught Claude to write like a lawyer. It guarantees that every time the skill runs, Claude reads the same file and produces the same document structure, which is a different and more modest claim.
Why deleting the skill changes nothing about ability
Imagine deleting the skills folder. Claude doesn't forget how to draft, because it never learned drafting as a standalone skill in the first place. What disappears is one specific routine for structuring a particular kind of document. Losing a routine is not the same as losing a learned capability, and that distinction is the whole point of understanding what a skill is.
What watching the output does and doesn't prove
Watching Claude produce a clean, well-structured draft doesn't prove it understood the underlying matter. A file's structure can be followed precisely on facts that were never really grasped in any deep sense. Watching Claude produce a rough or oddly shaped draft doesn't prove the skill is broken either; it may simply be a case the file's structure doesn't fit well. Neither result is proof of comprehension or its absence, because the mechanism at work is structural compliance, not understanding.
Trying it yourself
Pick a document you write the same way every time. Ask Claude to write a SKILL.md for it, in plain language with ordered steps, then have it read the file back to you and walk through exactly what it will do before doing it. Running this against a real document you produce repeatedly shows the mechanism directly: the same structure, every time, bounded exactly by what the file says.
Key takeaways
- Claude's draft skill is one plain-language SKILL.md describing how to turn facts and requests into a formatted document.
- Claude follows the file's steps in a fixed order, branching only where the file explicitly says to.
- A skill is a specification for structure, not a new writing ability; deleting it loses a routine, not learned skill.
- The payoff is a consistent document structure on every run; the limit is anything the file never wrote down.
- A clean draft or a rough one proves nothing on its own about whether Claude understood the underlying matter.
Who this is for
Anyone drafting the same kind of document repeatedly who wants to understand what a Claude Skill actually contributes, and readers evaluating whether Skill-driven output reflects real understanding or just structural consistency.
Chapters
- 0:00The naive framing: "Claude learned legal writing"
- 0:10Sounds like a writing upgrade
- 0:18Broken, with a case — delete the folder, nothing is forgotten
- 0:27The anchor: one file — draft's single SKILL.md
- 0:41Read it, then follow it in order
- 0:49Spec, not power — the payoff and the limit
- 0:58The anchor returns — same file, every run
- 1:10Both directions — neither one is proof
- 1:24Carry-out
- 1:33Your turn
- 1:45Outro
Full transcript(auto-generated, with timestamps)
The naive framing: "Claude learned legal writing"
[0:00]You guess Claude learned legal writing from a skill called draft. It didn't. It was handed a file of instructions. Draft just names one such file. Let's see what's actually inside it. Here Claude
Sounds like a writing upgrade
[0:10]Has a draft skill, and it sounds like a writing upgrade, like it studied legal drafting and can now produce documents on instinct. But nothing in the model
Broken, with a case — delete the folder, nothing is forgotten
[0:19]Changes. Delete the skills folder and Claude doesn't forget how to draft. There was nothing to learn. It just stops following that one routine.
The anchor: one file — draft's single SKILL.md
[0:27]Here's what a skill actually is, one file. Draft, for instance, is a folder holding a single skill. MD, instructions for turning your facts and requests into a formatted document, written in plain language Claude reads before it starts. Claude reads that file top to bottom and
Read it, then follow it in order
[0:43]Works through it step by step, in the order it's written, no branching unless the file itself says branch. That makes
Spec, not power — the payoff and the limit
[0:49]A skill a specification, not a new power. The payoff, the same structure every draft. The limit, anything outside those written steps and Claude is off the map. So draft never taught Claude
The anchor returns — same file, every run
[1:00]How to write like a lawyer. It just guarantees that every time draft runs, Claude reads that same file and produces the same document structure. That's the whole trick. Watching Claude produce a
Both directions — neither one is proof
[1:11]Clean draft doesn't prove it understood the matter. A file can be followed to the letter on facts it never really grasped. And watching it produce a rough draft doesn't prove the skill is broken. It may just be a case the file structure doesn't fit. A skill doesn't teach
Carry-out
[1:25]Claude how to draft. It's a file of steps Claude reads before it starts. So every draft comes out with the same structure every time. Your turn. Paste
Your turn
[1:33]This into Claude. Pick one document I write the same way every time. Write me a skill MD for it, plain language, ordered steps. Then read it back to me and walk me through exactly what you'll do before you do it. Claude draft Liam
Outro
[1:46]In for bear.
