socratic-tutor · nicknisi — Claude Code skill: what it does, how to install
The socratic-tutor skill turns a code review into a guided understanding check, asking about the problem, solution, edge cases, and downstream impact.
MIT ★ 114 updated 2026-08-11
/plugin marketplace add nicknisi/claude-plugins
/plugin install essentials@nicknisiWhat socratic-tutor does
socratic-tutor helps users take ownership of a completed change, diff, pull request, or session. It begins by asking for a restatement in the user’s own words, then works through a visible checklist covering the problem, the solution, and the wider context. The questions focus on reasons, alternatives, design choices, and edge cases.
The skill quizzes rather than delivering one long lecture. It can use real code, walk through a diff, or drive a debugger when that makes the idea clearer. Users can request eli5, eli14, or elii for a different teaching depth. A written explanation is handled by the separate explain-diff skill.
The session does not end until the user has demonstrated understanding of every checklist item. In Claude Code, the skill is installed through the essentials plugin.
What it helps with
- review a completed diff with guided questions
- explain why a code change was made
- compare the alternatives behind a solution
- test understanding of edge cases
- trace downstream effects of a change
Example prompts for the agent
- Run
/essentials:socratic-tutorand quiz me on the work from this session. - Walk me through the diff, asking about the problem before the solution.
- Use
eli14and keep testing me until I can explain the design choices and edge cases.
How to install socratic-tutor
1Plugin marketplace
/plugin marketplace add nicknisi/claude-plugins/plugin install essentials@nicknisiThis installs the whole essentials plugin with all its skills
2Skills CLI (Vercel)
npx skills add nicknisi/claude-plugins --skill socratic-tutor -a claude-code3Manually: put the files in place
~/.claude/skills/socratic-tutor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/socratic-tutor/
1Skills CLI (Vercel)
npx skills add nicknisi/claude-plugins --skill socratic-tutor -a codex2Manually: put the files in place
.agents/skills/socratic-tutor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nicknisi/claude-plugins --skill socratic-tutor -a cursor2Manually: put the files in place
.cursor/skills/socratic-tutor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nicknisi/claude-plugins plugins/essentials/skills/socratic-tutor2Manually: put the files in place
.github/skills/socratic-tutor/SKILL.md1Skills CLI (Vercel)
npx skills add nicknisi/claude-plugins --skill socratic-tutor -a gemini-cli2Platform CLI
gemini skills install https://github.com/nicknisi/claude-plugins --path plugins/essentials/skills/socratic-tutorManually: put the files in place
.devin/skills/socratic-tutor/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about socratic-tutor
How do I install socratic-tutor in Claude Code?
Add the marketplace with /plugin marketplace add nicknisi/claude-plugins, then install the plugin with /plugin install essentials@nicknisi.
What does socratic-tutor do?
It runs an interactive quiz about a code change, covering the problem, solution, design decisions, edge cases, and impact. It moves forward as the user demonstrates understanding.
Can I choose how deeply it explains a topic?
Yes. Ask for eli5, eli14, or elii to set the requested teaching level.
Source text
SKILL.md · MIT
--- name: socratic-tutor description: >- Socratic tutor that drills the user until they deeply understand a change — the problem, the solution, the design decisions, the edge cases, and what it impacts. Use after completing or reviewing work (a diff, PR, or session) when the user wants to truly own it, not just skim it — or when the user says /socratic-tutor, "teach me what we just did", "quiz me on this", "drill me on this", or "make sure I understand this". Interactive: restates first, quizzes as it goes, and does not stop until the user demonstrates mastery. For a written explainer to read or share instead of a live quiz, use explain-diff. argument-hint: Optional — which change or area to focus on (defaults to this session's work) --- # Socratic Tutor Act as a wise, effective teacher. The goal is for the user to _deeply_ understand a change — not skim it. Teach incrementally and confirm mastery of each stage before moving to the next. Understanding must hold at both the high level (motivation, why it matters) and the low level (business logic, edge cases). This session is not finished until the user has demonstrably mastered every item on the checklist below. ## Gauge where they are first Before teaching anything, ask the user to restate their current understanding in their own words. This surfaces the real gaps and prevents lecturing on things they already know. Fill in from there. Let the user steer. They may ask questions or request a level: **eli5** (explain like they're five), **eli14**, or **elii** (explain like they're an intern). Match the depth they ask for. ## Keep a running checklist Maintain a markdown checklist of what the user must understand, and keep it visible — render it back to the user as items are added and checked off, so they can see how much ground is left. Check an item off only after they have _demonstrated_ it — not merely heard it explained. Organize it into three buckets: 1. **The problem** — what it was, why it existed, and the different branches or alternative approaches that were on the table. 2. **The solution** — what was done, why it was resolved _this_ way, the design decisions behind it, and the edge cases it handles (or doesn't). 3. **The broader context** — why this matters, and what the change will impact downstream. ## Drill the whys Make sure they understand _why_ — then ask the next why, and the one beneath that. Understanding the problem deeply is the priority; do not let the user jump to the solution before the problem is solid. Cover _what_ and _how_ as well, but _why_ is the spine of the session. ## Quiz, don't lecture Use `AskUserQuestion` to quiz with open-ended or multiple-choice questions. Quiz at each stage as it's taught — do not save one big quiz for the end. Two rules for fair quizzing: - **Vary the position of the correct answer** between questions so it isn't always the same slot. - **Never reveal the answer until after the user submits.** ## Use the code Show the actual code, walk the diff, or drive the debugger when it makes a concept concrete. A real line of code or a live variable beats an abstract explanation. ## Stop condition Keep going until every checklist item is confirmed mastered. The session ends when — and only when — the user has shown they understand the problem, the solution, and why it all matters.
© Nick Nisi · MIT · nicknisi/claude-plugins
Similar skills
All skills for Agent setup: memory, context, orchestration →socratic-tutor by other authors comes first.