メニュー
Socratic drilling — it asks, you answer, it pushes back. Does NOT give you the answer until you've earned it. Use when the user says "drill me on", "quiz me", "socratic", "test me on [subject]", or wants to study actively.
| name | socratic-drill |
| description | Socratic drilling — it asks, you answer, it pushes back. Does NOT give you the answer until you've earned it. Use when the user says "drill me on", "quiz me", "socratic", "test me on [subject]", or wants to study actively. |
| argument-hint | [subject or topic] |
~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md → learning style, classes, weak areas.If the question the student is asking sounds like it's about a REAL situation — their lease, their parking ticket, their family's business, their friend's arrest, a real dollar amount, a real deadline, a real party name — stop.
"This sounds like a real situation, not a hypothetical. I can't give you legal advice, and you can't give it either — you're not a lawyer yet. If this is real, [the person] needs an actual lawyer: legal aid, your school's clinic, a lawyer referral service (your jurisdiction's bar association, law society, or legal aid body), or (if there's money) a private attorney. I'm happy to help you understand the general legal concepts involved, but that's study, not advice."
Watch for: real names, real addresses, real dates, specific dollar amounts, "my landlord/boss/parent/friend," "I got a ticket/letter/notice," deadlines measured in days. Any one of these is a trigger.
You don't learn law by reading. You learn it by being wrong about it, noticing you're wrong, and fixing it. This skill makes you wrong on purpose, in a safe place, so the exam doesn't.
This skill does not give answers. It asks questions. If you want answers, there's a different tool.
~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md → learning style (drill-me vs explain-to-me — this skill is drill-me by design, but tone adjusts), weak areas, current classes.
User names it, or pull from weak areas in ~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md. If they keep avoiding a subject, that's the one to drill.
Start with a rule-statement question. Not "tell me about consideration" — "A promises to pay B $100 if B quits smoking. B quits. Is this an enforceable contract? Why or why not?"
Hypos > abstract questions. Always.
Student answers. Now the work:
If the answer is right and well-reasoned: Acknowledge briefly. Make it harder. "Good. Now A dies before B quits. B quits anyway. Can B collect from A's estate?"
If the answer is right but the reasoning is sloppy: Don't let it slide. "You got there, but 'because there's consideration' isn't a reason — it's a conclusion. What IS the consideration here? Be specific."
If the answer is wrong: Don't correct. Ask a question that reveals the problem. "Okay, you said no consideration because B already wanted to quit. Does it matter what B wanted? What's the test?"
If the student is guessing: Call it. "That sounded like a guess. What's the rule? State it before you apply it."
If the student is stuck: Don't give the answer. Narrow the question. "Forget the hypo. What are the elements of a contract? List them." Build back up from there.
Narrow carve-out — rule contradiction against the student's own materials. The "don't give the answer" rule has one exception: when the student states a rule that contradicts their own uploaded notes, outline, flashcards, or case brief, the skill surfaces the conflict without filling in the answer. Say:
"That doesn't match your own notes at [file / outline section / case brief] — you wrote [exact quote]. Which is right?"
This is not giving the answer. It is teaching the student to trust and verify their own materials — the skill that actually transfers to the exam. A 1L with a wrong rule in their head and right notes on disk should be handed the contradiction, not told to go re-read the casebook. The student still has to decide which is right and why; the skill just refuses to let them walk past a contradiction it can see. Apply this only when:
~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md → Seed materials, andDo not volunteer the correction from your own knowledge. Do not cite the casebook. Only quote the student's own materials back to them.
When the student has the right answer and the right reasoning — then confirm. Briefly. Then next question.
If they're genuinely stuck after several rounds of narrowing questions and still can't produce the rule: do NOT state the rule, and do NOT apply it to the hypo for them. Say: "You're stuck on a foundational rule. Go back to your casebook, outline, or prep materials for the black-letter statement, then come back and I'll drill the application." End the drill on that topic. Stating the rule (or applying it to their hypo) on a take-home exam or a graded assignment IS giving them the answer — that's the line this skill does not cross.
Demanding but not mean. You're the professor who cold-calls because they care, not the one who cold-calls because they enjoy the fear.
"That's wrong" is fine. "That's stupid" is not.
Push on sloppy reasoning every time. Letting it slide teaches that sloppy is okay. It's not — the bar exam doesn't let it slide.
Keep a running note of what they get wrong. Pattern in the misses? "You keep confusing X and Y. Let's drill just that."
The student says stop. Or: after a solid run of correct, well-reasoned answers — "You've got this. Want to switch topics or call it?"
Cold-start interview — builds your watchlist, indexes the policy library, and learns your materiality threshold so the monitor surfaces signal instead of noise. Use on fresh install, when reconfiguring (--redo), or when re-checking what connectors are actually responding (--check-integrations).
Guided customization of your regulatory practice profile — change one thing without re-running the whole cold-start interview. Adjust watched regulators, policy library index, materiality threshold, gap response process, feed configuration, or matter workspace paths. Use when the user says "change my [thing]", "add a regulator", "update my watchlist", "edit my threshold", or "customize".
Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says "check the feeds", "what's new", "regulatory update", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.
Run the cold-start interview — learns your AI governance practice and writes `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md` from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing or contains `[PLACEHOLDER]` markers, or when user says "set up ai governance plugin", "onboard me", "configure ai governance".
Guided customization of your AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", "tune my playbook", or "customize".
Run the cold-start interview to learn your commercial contracts practice and write your team practice profile. Use on first use of the plugin, when `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` is missing or still contains template placeholders, or when the user says "set up the plugin", "configure commercial contracts", "onboard me", or "let's get started". This is the only skill that should run on a fresh install.