$ loading_
Create and revise practice-area guides for student-facing clinic skill behavior.
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
Help me draft a practice-area guide for a legal clinic's family law work. Cover intake questions, pedagogy posture, review gates, cross-plugin checks, and local rules in order. Set the default pedagogy posture to guide and mark situations where students must get supervisor sign-off first.
A supervisor-facing draft guide for family law with defined questions, teaching posture, review gates, and local rules.
We already have an immigration guide. Please revise it by setting client communications to a sixth-grade reading level, adding common student mistakes and how the skill should catch them, and enforcing review gates for filing, sending documents to clients, and making legal judgments.
Updated immigration guide content highlighting the new reading level, mistake prevention, and mandatory review rules.
After finishing the guide, give me a test-run plan: explain how to use /legal-clinic:draft to preview what students will see under the current configuration, and list the five things I should inspect most closely.
A concise test plan to help the supervisor verify that student-facing behavior matches the teaching goals.
A supervising attorney can create separate guides for family law, immigration, and other practice areas to standardize intake, teaching posture, and review requirements. This lets each case type follow its own teaching and compliance rules.
When a clinic wants skills to shift from simply completing work to guiding student learning, this skill can configure assist, guide, or teach postures. It is suited for turning a supervisor’s teaching philosophy into plugin behavior.
A supervising attorney can define where students must stop and get sign-off, such as before filing, contacting a client, or making legal representations. Cross-plugin checks and local rules can also be added to reduce common student mistakes.
The README describes /build-guide as a configuration skill for supervising attorneys in a legal clinic. It loads existing plugin context, then walks through practice area, intake questions, pedagogy posture, review gates, cross-plugin checks, and local rules, writing the result to guides/<practice-area>.md. It emphasizes that students should not author guides, and suggests a test run with /legal-clinic:draft so the supervisor can preview student-facing behavior.
~/.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.
…
It is for the supervising attorney to write or revise practice-area guides. The docs explicitly say students do not author the guide and should use /legal-clinic:ramp instead.
It walks through key parts of a practice-area guide, including intake questions, pedagogy posture, review gates, cross-plugin checks, and local rules. The docs also mention common mistakes, reading-level targets, and when supervisor sign-off is required.
The docs say the guide is written to guides/<practice-area>.md under the plugin config directory, creating the guides folder if needed. Afterward, you can run /legal-clinic:draft to preview the student-facing behavior under the current configuration.
Safely uninstall hub-installed community skills with confirmation and audit logging.
Temporarily disable or re-enable an installed community skill without deleting files.
Get a concise briefing on one legal matter's status, changes, deadlines, and risks.
Manage matter workspaces to separate, switch, and archive client contexts.
Search watched skill registries, preview matches, and inspect SKILL.md before installing.
Draft DMCA notices, triage incoming claims, and prepare counter-notice drafts.
Capture key learnings into reusable repository skills and instructions.
Create or refine AI skills with scope, workflows, and tool integrations.
Create, refine, and troubleshoot AI skills, specs, invocation, and compatibility.
Run structured legal client intake and generate organized case summaries.
Create or update skills that extend Codex with knowledge, workflows, and tools.
Identify compliance risks and draft policies, procedures, and review guidance.