Claude's "No Rewrite, Ever" Rule: Inside the Legal Writing Skill

A skill is a folder with one file, SKILL.md, that Claude reads before it works. The legal-writing skill has one hard rule, no rewriting, so it acts as a harsher reader of your memo rather than a ghostwriter for it.

1:50 video3 min readWatch on YouTube

Ask Claude for feedback on a legal memo and it is easy to hear that as a request to fix the memo. The legal-writing skill does not work that way. A skill is just a folder with one file, SKILL.md, that Claude reads before it starts working, and this one has a hard rule written into it: no rewriting, ever. The video walks through what the skill does instead.

The naive framing: "Claude, fix my legal memo"

The video starts from a common assumption. Someone pastes in a draft and asks for feedback, and it sounds like a fix-it request: hand over the memo, get back a better one. The skill is built to break that expectation. It is a feedback skill for law-student writing, and its job is to judge the draft, not to produce a replacement for it.

What happens when you ask for a rewrite anyway

The video shows the rule being tested with a case. Ask Claude to rewrite your draft and it refuses. It then offers three alternatives: structural feedback, one labeled example, or a drill on the underlying rule. The example is generic and marked as a model, not as your text, so there is nothing to copy straight into the memo. The sentence, as the video puts it, still has to come from you.

Reading the whole draft first

The running example is a first-year law student's negligence memo about a car crash. Before Claude says anything, it reads the entire draft from top to bottom. It also names what the document actually is: a memo, a brief, a paper, or an exam essay. That classification matters because the feedback depends on what kind of document it is.

Feedback runs top-down

Once it has read the draft, the feedback follows a fixed order. The first question is whether the structure is right. The second is whether the analysis connects the rule to the facts. Only after those does it move to clarity and citation. The video is explicit that the skill never does sentence-level polish before the structure is fixed, since polishing sentences in a badly organized memo is wasted effort. On the negligence memo, it might report that the structure runs backwards and flag one rule to double-check, but it still will not write the corrected paragraph.

Confident on form, not on law

The skill separates two kinds of confidence. On structure, Claude is confident, because good writing is good writing. On whether the negligence rule itself is stated correctly, it will not guess. Instead it flags the point as VERIFY and leaves the legal call to the human. The video draws a two-way lesson from this. A confident structural note does not prove the law inside the paragraph is right, and a VERIFY flag does not mean the structure is fine. Both can be broken in the same paragraph.

Why the rule exists

The purpose of the no-rewrite rule is to make Claude a harsher reader of your memo and never its ghostwriter. A student who receives a rewritten paragraph has not learned why the original was weak. Feedback that says what is weak and why leaves the learning, and the authorship, with the writer.

Key takeaways

  • A skill is a folder containing one file, SKILL.md, that Claude reads before it works.
  • The legal-writing skill's hard rule is no rewriting, ever; if asked, it refuses.
  • Instead of rewriting, it offers structural feedback, one labeled example, or a drill on the underlying rule.
  • It reads the whole draft first and names the document type: memo, brief, paper, or exam essay.
  • Feedback runs top-down: structure, then rule-to-fact analysis, then clarity and citation.
  • On legal substance it does not guess; it flags VERIFY and leaves the call to you.
  • A confident structural note does not prove the law is right, and a VERIFY flag does not prove the structure is sound.

Try it yourself

Take something you are actually drafting and paste this into Claude: "I'm drafting a memo. Read the legal-writing skill and give me structural feedback — organization, analysis depth, clarity, citation. Don't rewrite any of it: tell me what's weak and why, and flag anything you're not certain is legally correct." Then check the result: did it rewrite a single sentence, or did it only tell you what is weak?

Chapters

  1. 0:00The naive framing: "Claude, fix my legal memo" 0:10 Sounds like a fix-it request 0:16 No rewrite, ever — broken with a case 0:27 The anchor: a 1L's negligence memo, read whole first 0:38 Top-down, in that order 0:48 Confident on form, not on law 0:59 The anchor returns — still no rewrite 1:12 Both directions — not proof, either way 1:24 Carry-out 1:32 Your turn 1:47 Outro
Full transcript(auto-generated, with timestamps)

The naive framing: "Claude, fix my legal memo" 0:10 Sounds like a fix-it request 0:16 No rewrite, ever — broken with a case 0:27 The anchor: a 1L's negligence memo, read whole first 0:38 Top-down, in that order 0:48 Confident on form, not on law 0:59 The anchor returns — still no rewrite 1:12 Both directions — not proof, either way 1:24 Carry-out 1:32 Your turn 1:47 Outro

[0:00]Someone figures asking Claude for feedback means asking it to fix the memo. It won't. Legal writing's rule is no rewriting ever. Liam walks through what the skill actually does. Ask Claude for feedback on your memo and it's easy to hear that as a request to fix the memo for you. But legal writing's hard rule is no rewriting ever. Ask it to rewrite anyway and it refuses, then offers structural feedback, one labeled example, or a drill on the rule instead. First, it reads the whole draft top to bottom before saying anything say a 1L's arguing negligence in a car crash and names what it actually is, memo, brief, paper, or exam essay. Feedback then runs top down. Is the structure right? Does the analysis connect rule to fact? Then clarity and citation. Never sentence level polish before the structure is fixed. On structure, it's confident writing is writing, but on whether that negligence rule is actually stated right, it

Won't guess. It flags verify and leaves the legal call to you. So, on that same negligence memo, it might say the structure runs backwards and flag one rule to double-check, but it still won't write the fixed paragraph. One generic example labeled right yours, don't copy and it stops there. A confident structural note doesn't prove the rule inside is correct. That's exactly what the verify flag is for. And a verify flag doesn't mean the structure is fine, either. Both can be broken in the same paragraph. Legal writing's job is to make Claude a harsher reader of your memo, never its ghostwriter. The sentence still has to come from you. Your turn. Paste this into Claude, I'm drafting a memo. Read the legal writing skill and give me structural feedback, organization, analysis depth, clarity, citation, but don't rewrite any of it. Tell me what's weak and flag anything you're not certain is legally correct. Claude's legal writing, Liam in for Bear.

More from Claude

Humanitarians AI Lyrical Literacy Project