Skip to main content
skill CX Codex

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

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add nicknisi/claude-plugins
/plugin install essentials@nicknisi
Open on GitHub

What 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-tutor and quiz me on the work from this session.
  • Walk me through the diff, asking about the problem before the solution.
  • Use eli14 and 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@nicknisi

This installs the whole essentials plugin with all its skills

2Skills CLI (Vercel)

npx skills add nicknisi/claude-plugins --skill socratic-tutor -a claude-code

3Manually: put the files in place

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

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

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.

socratic-tutor janestreet socratic-tutor — a skill for Claude Code that teaches through questions and checks of the learner’s answers. It starts when someone asks to learn a topic, take a quiz, or build mastery. CX Codex +1 ★ 10,568repo stars tutor-setup bevibing tutor-setup — a skill for Claude Code, Codex, Cursor and other agents that converts PDFs, text files and web pages into an Obsidian StudyVault. CX Codex +1 2,200installs socratic-questor tronghieu socratic-questor is a skill that guides learning through questions, helping explore concepts, test understanding, or discuss a document. CX Codex +1 ★ 117repo stars claude-docs-course costiash claude-docs-course builds a self-contained interactive HTML tutorial from official Claude docs. Useful for mastering API patterns, SDKs, and hooks through visuals and quizzes. CX Codex +1 ★ 58repo stars learn rohitg00 learn is a Claude Code skill that teaches the AI Engineering from Scratch course in the terminal, section by section, quizzes at the end, and records progress. CX Codex +1 5,200installs exam-tutor ZeKaiNie exam-tutor is a Claude Code skill that teaches a current chapter and explains formulas and flagged questions. It activates when asked to study a chapter, derive a formula, or work through a key question. CX Codex +1 ★ 399repo stars thinking-socratic tjboudreaux thinking-socratic surfaces unstated assumptions and undefined terms before coding begins. Helps the agent ask decisive questions instead of guessing requirements. CX Codex +1 730installs

From the same set18

The whole set →
image-gen image-gen is a Claude Code skill that generates or edits images with Gemini or OpenAI. It handles illustrations, diagrams, and graphics with readable labels. CX Codex +1 ★ 114repo stars handoff Turns a working session into a short handoff file, so a fresh agent can pick up unfinished work without rebuilding the context. CX Codex +1 ★ 114repo stars squad-review squad-review runs six specialist code reviews on a branch diff, then tests every reported issue with an adversarial verifier. CX Codex +1 ★ 114repo stars thermo-nuclear-code-quality-review thermo-nuclear-code-quality-review conducts a ruthless maintainability audit on feature branches. Flags tangled logic, oversized files, and opportunities to cut structural bloat. CX Codex ★ 114repo stars explain-diff The explain-diff skill turns a diff, PR, branch, or commit into an HTML guide with system context, diagrams, a code walkthrough, and a quiz. Use it to understand a change or teach it to someone else. CX Codex +1 ★ 114repo stars code-simplifier code-simplifier refactors complex functions, cuts redundancy, and removes AI slop without touching public APIs or changing runtime behavior. CX Codex ★ 114repo stars git-committer The git-committer subagent reviews repository changes, runs available checks, and creates commits with semantic messages. Use it to hand off the commit workflow to Claude Code. CX Codex ★ 114repo stars tighten-prose tighten-prose strips the habits readers spot as machine-written — word clusters, inflated importance, phantom citations — and rewrites the flagged passages while keeping the author's voice. CX Codex +1 ★ 114repo stars

Project sponsors

Companies that keep this analytics open