SKILL/TREE

Plain-English client update email writer for lawyers

Paste your case notes and the milestone — get a Rule 1.4-compliant client update with progress, next steps, client action with bolded deadline, and high-risk language flagged inline.

$3.99
Works in Claude (Pro/Max/Team) or ChatGPT (Plus/Team) · paid AI plan required
Both Claude + ChatGPT packages included — you can't pick the wrong one.
Updated
01Drafts the full email — subject line, opening, progress, next steps, client action, closing — under 300 words by default
02Translates legalese automatically: 'motion to dismiss' becomes 'the other side is asking the court to throw out the case before it starts'
03Flags high-risk language before you send: outcome promises, deadline representations, waivers, settlement pressure, malpractice-adjacent apologies
04Adverse-development coaching note for bad news — verdict, dismissal, RFE denial — tells you to call first and frame email as 'As we discussed'
05Tone calibration per practice area: warm for family law, formal-direct for transactional, very-clear for immigration with language differences
06Covers litigation, transactional, family, estate planning, immigration, criminal defense — knows the milestones in each

What it does

Client communication is the #1 reason for bar complaints — and lawyers underdo it because writing client updates from scratch eats hours. This skill turns your case notes into a plain-English, MRPC-compliant client update email in under a minute. Paste the milestone (complaint filed, answer received, RFE received, settlement offer, verdict, closing scheduled) and any raw notes. The skill drafts the full email using the canonical structure: specific subject line, 1-2 sentence opening with the status, progress bullets in past tense, next steps with concrete timeline, bolded client action with a deadline (or omitted entirely if no action needed — never the clichéd 'no action required on your end at this time'), warm-but-professional closing. It translates legalese automatically using the bundled plain-English glossary ('motion to dismiss' → 'the other side is asking the court to throw out the case before it starts'; 'RFE' → 'a Request for Evidence — this is not a denial'), calibrates tone based on practice area and client signal, and scans every draft for high-risk language patterns: outcome promises ('we expect to win'), deadline representations that create malpractice exposure if wrong, waiver language, settlement pressure, apologies that admit fault. Five bundled references do the work: a milestone reference covering complaint-through-verdict for litigation plus the analog milestones for transactional, family, estate, and immigration; a plain-English glossary translating 80+ legal terms; a tone calibration guide with formal-vs-warm and reassuring-vs-direct axes plus practice-area defaults; an ethics-and-risk reference covering Rule 1.4 and 1.6 with the high-risk language patterns; and a settlement communication guide with templates for offer received, demand sent, negotiation in progress, and disbursement statement. For adverse developments, the skill produces the email PLUS a coaching note telling you to call before sending — bar discipline data shows clients are far less likely to complain when bad news is delivered personally. Will never put settlement recommendations in writing, never make outcome promises, and never draft fault-admitting language without flagging it as malpractice exposure first.

Frequently asked

How do I write a client update email about an adverse ruling without creating malpractice exposure?
Two rules: never apologize in writing in a way that admits fault, and never promise an outcome on appeal. The skill drafts the email under those constraints, leads with the facts (not 'unfortunately'), states the verdict accurately, and explains appeal options exist without predicting them. Plus it triggers the adverse-development coaching note telling you to call the client first — bar complaint data shows personal delivery prevents the complaint that cold-email delivery often triggers.
What's the right way to communicate a settlement offer to a client without pressuring them?
Communicate the offer (Rule 1.4 requires it), state authority belongs to the client (Rule 1.2), and request a call — never include your recommendation in the email itself. The skill uses the bundled settlement-comms template: 'The other side has made a settlement offer of [amount]. Settlement decisions belong entirely to you — my job is to make sure you have everything you need to make an informed choice. Are you available for a call this week?' Recommendations belong on a privileged call, documented in a file note.
How do I explain a USCIS RFE to a client without making them panic?
Open with what an RFE is in plain English: 'A Request for Evidence — USCIS is asking for more information before deciding your case. This is not a denial.' List the document categories USCIS requested in bullets, state the response deadline (typically 87 days), and end with a meeting CTA to gather documents. The skill drafts immigration emails with extra clarity given language differences and high anxiety — short sentences, no jargon, no ambiguity.
Does it know the milestones for transactional, family law, and estate planning, or only litigation?
All five major practice areas. Litigation milestones from complaint filed through verdict received. Transactional from LOI through closing complete. Family law from petition through final decree with appropriate emotional acknowledgment. Estate planning from intake through documents executed. Immigration from petition through approval or denial. Each milestone has a default tone calibration (formal-direct for transactional clients who want speed, warm for family law where one human acknowledgment earns more trust than a perfectly written legal update).
Will it flag if I'm about to send something that violates Model Rules or creates malpractice exposure?
Yes. Every draft is scanned for high-risk language patterns: outcome promises ('we expect to win,' 'you should recover $X'), deadline representations the attorney hasn't triple-checked, waiver language that may constitute a binding agreement, settlement authority pressure, and admissions or apologies that look like evidence of malpractice. Each flagged sentence gets an inline attorney warning so you decide whether to keep, cut, or escalate to malpractice carrier counsel before sending.

Install — no Terminal required

After checkout you land on a page with a one-click download and a pre-built install prompt. Pick the AI you already pay for — both packages are included, so you can't pick wrong.

What you'll see the second your payment clears
Your license key
ST-XXXX-XXXX-XXXX · permanent
Pre-built install prompt⧉ Copy
ChatGPT package (ZIP)⬇ Download

No setup work before you buy — copy, paste, done.

Have Claude Pro, Max, or Team?
Copy the prompt, paste into Claude

Copy the pre-built install prompt from the success page, paste it into any Claude Code chat, and Claude installs the skill itself — about 10 seconds. Using the app instead? Drop the downloaded folder into a Claude Project's knowledge and ask Claude to use it.

Have ChatGPT Plus or Team?
Build a Custom GPT — ~2 minutes
  1. Click Download ChatGPT package (included with every purchase).
  2. Unzip it — inside is a SETUP.md and a knowledge/ folder.
  3. Go to chatgpt.com → your profile → My GPTs Create a GPTConfigure.
  4. Paste the Name, Description, and Instructions from SETUP.md into the matching fields.
  5. Under Knowledge, upload every file in the knowledge/ folder.
  6. Click Create/Save, open your GPT, and describe your task in plain English.

A paid plan on either platform is required — Claude (Pro, Max, or Team) or ChatGPT (Plus or Team). Comfortable with Terminal? A one-line npx skilltree-network install path is available too.

More in Professional Services

View all Professional Services skills →