Skip to main content
skill CX Codex official · Anthropic

socratic-drill — Claude Code skill: quiz yourself without handed

The skill asks the question, waits for your answer, then pushes on the weak parts. It withholds the answer until you earn it.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add anthropics/claude-for-legal --skill socratic-drill -a claude-code
Open on GitHub

What socratic-drill does

socratic-drill turns a study session into an oral exam. You name a topic; the skill reads ~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md for your learning style, current classes and weak areas, then opens with a rule-statement question — usually a hypo rather than an abstract prompt. From there it works on whatever you say. A correct answer with solid reasoning gets a harder hypo. A correct answer with sloppy reasoning gets asked what the consideration actually is. A wrong answer gets a question that exposes the gap instead of a correction.

There is a real-matter check. Real names, addresses, dollar amounts, deadlines, or a phrase like “my landlord” stop the drill: the skill says this is not a hypothetical and that neither it nor a law student can give legal advice. One narrow exception to the no-answers rule: if you state a rule that contradicts your own uploaded notes, outline or case brief, the skill quotes your material back and asks which is right. It does not supply the correction from its own knowledge.

When several narrowing questions still leave you unable to state the rule, the skill does not state it and does not apply it to the hypo — it sends you back to your casebook and ends the topic. Tone is demanding without being unkind, and repeated misses get flagged so you can drill that one thing. The skill is built for active study, not for reading.

What it helps with

  • test yourself on a subject before an exam instead of rereading notes
  • catch reasoning that sounds right but states a conclusion
  • find the subjects you keep avoiding
  • check your rule statement against your own uploaded materials
  • practice applying a rule to hypotheticals

Example prompts for the agent

  • Drill me on consideration
  • Quiz me on the elements of a contract
  • Socratic drill on remedies for breach

How to install socratic-drill

1Skills CLI (Vercel)

npx skills add anthropics/claude-for-legal --skill socratic-drill -a claude-code

2Manually: put the files in place

~/.claude/skills/socratic-drill/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/socratic-drill/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about socratic-drill

How do I install socratic-drill in Claude Code?

Run npx skills add anthropics/claude-for-legal --skill socratic-drill -a claude-code. The skill lands at ~/.claude/skills/socratic-drill/SKILL.md.

What does socratic-drill do?

It questions you on a topic, works through your answer and presses on the weak spots. It holds back the answer until you reach the right reasoning yourself.

What does the skill need to work?

The file ~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md with your learning style, classes and weak areas. If you uploaded notes, outlines or flashcards, the skill can check your rule statement against them.

Source text

SKILL.md · Apache-2.0
---
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]"
---

# /socratic-drill

1. Load `~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md` → learning style, classes, weak areas.
2. Apply the workflow below.
3. Ask a question on the topic. Wait for answer.
4. Push back. Ask follow-ups. Don't give the answer.
5. Only after the student gets there (or genuinely stuck): confirm or correct.

---

## Real-matter check

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.

## Purpose

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.

## Load context

`~/.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.

## The drill

### Step 1: Pick the topic

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.

### Step 2: Ask

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.

### Step 3: Listen and push back

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:

1. The student has actually uploaded materials (notes, outlines, case briefs, flashcards) referenced in `~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md` → Seed materials, and
2. The stated rule and the uploaded rule disagree on a specific point — not a phrasing difference, not a level-of-detail difference, but a substantive contradiction.

Do not volunteer the correction from your own knowledge. Do not cite the casebook. Only quote the student's own materials back to them.

### Step 4: Only after they get there

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.

## Tone

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.

## Progress tracking

Keep a running note of what they get wrong. Pattern in the misses? "You keep confusing X and Y. Let's drill just that."

## When to stop

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?"

## What this skill does not do

- Give the answer before the student has tried. Ever.
- Let "pretty close" count. The bar exam doesn't.
- Lecture. This is Q&A, not a podcast.

© anthropics · Apache-2.0 · anthropics/claude-for-legal

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set118

claim-chart Builds and audits element-by-element proof charts for patent and civil claims with pin-cites for every cell. Identifies evidence gaps across causes of action and defenses. CX Codex +1 666installs chronology Turns matter documents into a dated timeline: events extracted, duplicates merged, significance tagged against the case theory. Reach for it before a statement of facts or witness prep. CX Codex +1 663installs demand-draft Turns a finished demand intake into a sendable letter, holding the draft back until privilege, FRE 408 and admission risk have been checked. CX Codex +1 653installs marketing-claims-review Splits marketing copy into individual claims and tells you which ones need substantiation, a rewrite, or the axe. CX Codex +1 650installs reg-gap-analysis Diffs new AI regulations against internal governance policies to find compliance gaps. It produces a prioritized remediation plan with deadlines and owners. CX Codex +1 646installs ip-clause-review Reviews intellectual property terms in contracts and outputs a risk-prioritized memo. It catches IP assignment gaps, license ambiguities, and warranty risks. CX Codex +1 645installs invention-intake Runs a first-pass triage on invention disclosures across novelty, §101, and bar dates. Helps legal teams decide whether to order a prior-art search. CX Codex +1 644installs case-brief Builds a case brief scaffold in your own format and, in drill-me mode, makes you state the holding before anything else. CX Codex +1 638installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor