$ loading_
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.
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "socratic-drill" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/law-student/skills/socratic-drill/SKILL.md 2. 保存为 ~/.claude/skills/socratic-drill/SKILL.md 3. 装好后重载技能，告诉我可以用了
~/.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?"
…
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.