From legal-clinic
Routine client correspondence from templates — appointment confirmations, document requests, brief "we filed it" updates. Plain language, required elements, supervision routing. NOT substantive advice. Use when a student needs to send routine correspondence, an appointment confirmation, a document request letter, or a brief status note to a client.
How this skill is triggered — by the user, by Claude, or both
Slash command
/legal-clinic:client-letter [appointment | doc-request | update][appointment | doc-request | update]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Load `~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md` → plain-language standards, supervision style, clinic contact info.
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → plain-language standards, supervision style, clinic contact info.Scope: routine only. Substantive advice → /status client or a conversation with the professor.
/legal-clinic:client-letter appointment
/legal-clinic:client-letter doc-request
Clinics send a lot of routine correspondence: "your appointment is Tuesday at 2pm," "please bring your lease," "we filed your answer." This skill handles those from templates so students aren't typing the same letter every week.
Scope: routine only. Substantive advice, bad news, case strategy — those are /status client or a conversation, not a template letter.
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → plain-language standards, supervision style, clinic contact info.
Read the supervisor guide for this practice area at ~/.claude/plugins/config/claude-for-legal/legal-clinic/guides/<practice-area>.md. Check the pedagogy_posture setting:
guide (default): Produce the structure and the checklist (required elements, plain-language targets, sign-off per student practice rule). Ask the student to draft each section. Give feedback on their draft (register, reading level, required elements, what they missed). Offer to fill a section only when the student has tried once.assist: Produce the letter. Flag items for student review. The student edits and learns by reviewing.teach: Don't produce the letter. Ask the student to draft it. Give feedback. Ask leading questions when they're stuck. Only show a model paragraph after two attempts, and only the section they're stuck on. Track what they got right and wrong so the supervisor can see progress.If no guide exists, use guide. If the guide exists but doesn't set a posture, use guide.
Whatever the posture, the output always includes: "Pedagogy mode: [assist/guide/teach] — set by your supervisor's guide. This means I [description of what the student did vs what the skill did]."
No Brasil, o estagiário de Direito atua sob a Lei 8.906/1994 (Estatuto da OAB, art. 3º, §2º), praticando atos compatíveis com sua atividade acadêmica sob responsabilidade e em conjunto com advogado, e também deve observar o regulamento do Núcleo de Prática Jurídica (NPJ) da instituição — ou convênio com Defensoria Pública. A regra detalhada de assinatura/identificação em correspondência deve ser conferida no regulamento do NPJ ou convênio aplicável. The templates below use a generic form — conform the sign-off to your NPJ's rule (e regulamento do convênio, se houver) before sending. [verified: https://www.planalto.gov.br/ccivil_03/leis/l8906.htm]
Review label goes OUTSIDE the letter. The
[AI-ASSISTED DRAFT — requires review per plugin config supervision step]tag is a note to the student, not part of the letter body. Place it above the rendered template (or in a header the student deletes before sending), never inside the fenced letter content. If it ends up in the client-facing copy, the skill has failed.
Review label for the student (not for the client — strip before sending):
[AI-ASSISTED DRAFT — requires review per plugin config supervision step]
Dear [Client],
This confirms your appointment with [Clinic name]:
**Date:** [date]
**Time:** [time]
**Where:** [address / room / or "by phone at [number]"]
**With:** [student name]
**Please bring:** [documents needed — from case notes or leave as prompt
for student to fill]
If you need to reschedule, call us at [clinic phone] at least 24 hours before.
[Student name]
Estagiário(a) de Direito — [NPJ / Núcleo de Prática Jurídica]
Sob supervisão de [Advogado(a) Supervisor(a)], OAB/[UF] nº [número]
[Clinic name] | [phone] | [hours]
Review label for the student (not for the client — strip before sending):
[AI-ASSISTED DRAFT — requires review per plugin config supervision step]
Dear [Client],
To move your case forward, we need the following documents from you:
- [Document 1 — e.g., "Your lease agreement"]
- [Document 2 — e.g., "The notice you received from your landlord"]
- [Document 3]
**How to get them to us:** [drop off at clinic / email to [address] / bring
to next appointment]
**Please send by:** [date — if there's a deadline, say why: "We need these
by [date] so we can file your answer before the court deadline."]
If you don't have some of these or aren't sure what we mean, call us at
[clinic phone] and we can help.
[Student name]
Estagiário(a) de Direito — [NPJ / Núcleo de Prática Jurídica]
Sob supervisão de [Advogado(a) Supervisor(a)], OAB/[UF] nº [número]
[Clinic name] | [phone] | [hours]
For routine "we filed it" / "we're waiting" updates. (Fuller status updates → /status client.)
Review label for the student (not for the client — strip before sending):
[AI-ASSISTED DRAFT — requires review per plugin config supervision step]
Dear [Client],
Quick update: [one-line what happened — "We filed your answer with the court
on [date]" / "We sent the demand letter to your landlord on [date]"].
**What's next:** [one line — "We're waiting for their response" / "The court
will schedule a hearing and let us know the date"].
You don't need to do anything right now. We'll let you know when we do.
[Student name]
Estagiário(a) de Direito — [NPJ / Núcleo de Prática Jurídica]
Sob supervisão de [Advogado(a) Supervisor(a)], OAB/[UF] nº [número]
[Clinic name] | [phone] | [hours]
Sending a letter to a client is a consequential action. This plugin's gate is the supervision workflow described in ## Supervision style in ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md, reinforced by the Part 0 role check that confirms a licensed supervising attorney owns the clinic setup. That gate still holds: every letter clears review before it leaves the clinic.
Before sending any of the letters above, confirm:
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md (queue / flag / lighter-touch).[AI-ASSISTED DRAFT], any [VERIFY] or [FACT NEEDED] tags) have been removed from the client-facing copy.This is a student draft for supervising-attorney review, not a final letter. Sending it has legal consequences for the client and may constitute legal advice or communication on the client's behalf. A licensed supervising attorney reviews, edits, and signs off before the letter leaves the clinic. Do not send without supervisor approval.
Per ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md standards. Short sentences. No jargon. Reading level target enforced. If a template above includes a legal term the client might not know, explain it the first time: "We filed your 'answer' — that's the document that tells the court your side of the story."
Per ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md. Routine correspondence may or may not be a flag trigger depending on the supervision style the professor chose. If lighter-touch: these go out after student review without a queue step. If formal queue: even routine letters queue.
/status client or a conversation with the professor first./draft or /status court).npx claudepluginhub bossmann007/claude-legal-br --plugin legal-clinicGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.