$ loading_
Structural feedback on a legal writing draft (memo, brief, paper, exam essay) — organization, analysis depth, clarity, citation form. NEVER rewrites the draft. Use when the user says "feedback on my memo", "read my draft", or "critique my brief".
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "legal-writing" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/law-student/skills/legal-writing/SKILL.md 2. 保存为 ~/.claude/skills/legal-writing/SKILL.md 3. 装好后重载技能，告诉我可以用了
~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md → class, writing skill level, past feedback patterns.[VERIFY] on any substantive rule call I'm unsure about.~/.claude/plugins/config/claude-for-legal/law-student/writing-feedback/[student]/tracker.md for pattern detection.Writing is how lawyers think on paper. You don't get better at it by having someone else write it for you. This skill reads your draft, tells you what's weak and why, and points at what to change — without writing it for you.
Hard rule: no rewriting. Ever. Structural feedback is the product. Labeled example phrasings are permitted in small doses to illustrate a move (one or two per session, maximum) with an explicit "write yours, don't copy" label. If feedback ever drifts into "here's what your paragraph should say," the skill has failed its purpose.
A student who uses Claude to write their memo is a student who didn't learn to write memos. On the exam — or at the firm — that student is slower, less confident, and more wrong than the one who struggled through their own drafts. The point of law school writing practice is the struggle. This skill preserves it.
Example phrasings are permitted sparingly because seeing structural moves (not content) is genuinely pedagogical — the 1L who has never read a well-structured analysis paragraph can't invent one from scratch. Showing the move once, labeled, is different from writing the analysis.
[VERIFY] on anything I'm not certain about. Don't silently trust my substantive calls.[VERIFY] on edge cases. Check the Bluebook itself for anything non-routine.~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md → class, assignment type (if known), writing skill level, graded-essay feedback historyDon't react to the first problem you see. Read top to bottom, twice if short. Form a holistic read before giving feedback — otherwise the critique becomes a list of small fixes that miss the structural issue.
Name the type explicitly in feedback. A brief that reads like a memo isn't a good brief.
Feedback organized top-down — structure first, then paragraph-level, then sentence-level. Don't skip to sentence-level polish if the structure is broken.
# Writing Feedback — [assignment / date]
**Type:** [memo / brief / paper / exam essay]
**Length:** [N words] [if target known: vs. target N]
…
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity compliance", "filing deadlines", "annual reports due", "entity tracker", "what filings are due", "entity health", or "good standing".
Tabular review — one row per document, one column per data point, every cell cited to source. Built for M&A diligence ("review these 200 target contracts for change-of-control, assignment, and MAC clauses") but works for any batch review that needs a spreadsheet out the other end. Use when user says "tabular review", "review grid", "build a grid", "extract these fields from these contracts", "review these documents for X, Y, Z", "give me a spreadsheet of", "batch review", or points at a folder of documents and asks to compare them.
Draft a unanimous written consent of the board or a committee in house format, with precedent search from the consents repository. Handles multi-resolution consents, director conflict flags, state-law notice requirements, and signatory tracking, with a built-in scope warning for major one-off actions. Use when user says "written consent", "unanimous consent", "board consent", "consent in lieu", "UWC", or describes an action needing board approval without a meeting.
Kick off international expansion planning for a new country — gathers intake, runs EOR vs. entity framing, drafts cross-functional questions, surfaces country-specific flags, and creates a persistent tracker. Use when someone says "we're hiring in [country]", "expansion to [country]", or "first hire in [country]".
Update the status of an in-progress international expansion project — recalculates what is now unblocked, flags anything overdue, and surfaces the next priorities. Use when work has happened since the last session and the expansion tracker needs to reflect the current state.
Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says "brief the deal team", "what's the state of diligence", "summarize findings for [audience]", "deal update", or on the briefing cadence.