$ loading_
Help a clinic supervisor author a practice-area guide that configures how student-facing skills behave — intake questions, pedagogy posture (assist / guide / teach), review gates, cross-plugin checks, and local rules. Use when a supervising attorney wants to build or revise a per-practice-area guide, tune how the clinic skills behave for their clinic type, or set their teaching philosophy as plugin configuration.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "build-guide" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/legal-clinic/skills/build-guide/SKILL.md 2. Save it as ~/.claude/skills/build-guide/SKILL.md 3. Reload skills and tell me it's ready
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → role (must be Supervising attorney), practice areas, jurisdiction./legal-clinic:ramp).~/.claude/plugins/config/claude-for-legal/legal-clinic/guides/<practice-area>.md. Create the guides/ directory if needed./legal-clinic:draft under the configured posture so the supervisor sees what a student sees./legal-clinic:build-guide
Multiple guides are fine — one per practice area. Re-run this command to revise. Edit the guide file directly for quick changes.
The supervisor guide is the dial that turns student-facing skills from "get the work done" into "teach the student to do the work." Every student-facing skill in this plugin reads the guide before producing output: intake asks the questions the supervisor wants asked, drafting skills pick a pedagogy posture (assist / guide / teach), review gates route to the supervisor on the items the supervisor cares about, and cross-plugin checks wrap other-plugin skills in a supervision layer.
This skill helps a supervisor author that guide in 5-10 minutes per practice area. The guide is plain markdown at a well-known path — edit it by hand anytime.
Audience: the supervising attorney. Not students. Students run /legal-clinic:ramp and then the student-facing skills; they don't author guides.
Every output from this skill is a supervisor-facing configuration artifact, not student work product. Do NOT prepend [AI-ASSISTED DRAFT — requires student analysis and attorney review] to the output of this skill — that label is for student outputs. The guide file this skill writes is a supervisor configuration document; it sits next to CLAUDE.md in the plugin config directory, not in a matter workspace.
Offer this as a checklist the supervisor can skip through or use as the table of contents for the interview:
Walk through the checklist at the start of the interview so the supervisor knows what's coming and can flag which items they already have strong views on versus which they want to think through. Skip any item the supervisor waves off; note it in the guide as "not specified — skill uses defaults."
This is a supervisor skill. Read ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → ## Who's using this → Role. If the role is not "Supervising attorney," say:
This skill is for supervisors — it configures how the student-facing skills behave. If you're the supervisor, make sure your practice profile role is set to "Supervising attorney" in
/legal-clinic:cold-start-interview. If you're a student, this isn't the right skill for you — run/legal-clinic:rampto onboard, or ask your supervisor to author a guide for your clinic.
Stop if the role is not supervising attorney.
…
Review and approve (or reject) pending playbook update proposals from the playbook-monitor agent and apply approved changes to the practice profile. Use when the playbook-monitor agent has surfaced proposals, when the user says "review playbook proposals", "what playbook updates are pending", or wants to step through deviation-driven playbook changes.
Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.
Drafts board or committee meeting minutes in your house format. Auto-detects upcoming board and committee meetings from your calendar, asks for the agenda and any slides or pre-read materials, and produces a complete draft in the format learned from your seed minutes. Also handles written consents in lieu of meetings. Trigger: "board minutes", "draft minutes", "upcoming board meeting", "committee minutes", "written consent", or calendar detection of an upcoming board or committee event.
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.
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".
Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.