Skip to main content
skill CX Codex

socratic-quiz — Claude Code skill: learn by guided questions

The skill walks you through a topic with one question at a time instead of handing over the answer. Useful when you want to actually understand something, not just read it.

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

What socratic-quiz does

It asks one question, waits for your reply, then adapts. A correct answer gets a one-sentence confirmation and a harder follow-up; a wrong one gets a narrower question or a counterexample that exposes the gap. The direct explanation stays hidden until you ask to stop.

The skill is a single SKILL.md with instructions — no scripts, no external calls. Questions move from concrete to abstract, and later ones ask you to combine two concepts you already handled separately. If the topic is code, questions point at behaviour and structure you would run into yourself.

The tone stays conversational, with no filler praise. Stuck on the same idea after two or three tries, you get a hint rather than the answer. At the end you get a short recap of what you showed and where to dig further, with no score. It runs on platforms that support skills: Claude, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode.

What it helps with

  • get to grips with an unfamiliar library by answering questions
  • check how well you understand a system's internals
  • prepare for an interview on a specific topic
  • work through unfamiliar code without reading ready-made explanations
  • connect two concepts you already know separately

Example prompts for the agent

  • quiz me on asyncio queues
  • help me understand how this pipeline works — ask me questions
  • walk me through src/parser.py with questions, no direct answers

How to install socratic-quiz

1Skills CLI (Vercel)

npx skills add pchalasani/claude-code-tools --skill socratic-quiz -a claude-code

2Manually: put the files in place

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

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

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

Questions about socratic-quiz

How do I install socratic-quiz in Claude?

Run npx skills add pchalasani/claude-code-tools --skill socratic-quiz -a claude-code. The skill file lands at ~/.claude/skills/socratic-quiz/SKILL.md.

What does socratic-quiz do?

It teaches through guided questioning instead of direct explanation. You answer, the skill adjusts difficulty, and it holds back the correct answer until you ask for it.

Does the skill give a grade at the end?

No. When you say you are done, it gives a short summary of what you demonstrated and which areas need more work. No score, no grading.

Source text

SKILL.md · MIT
---
name: socratic-quiz
description: >-
  Use this when the user wants to deeply understand something
  through guided questioning. Trigger phrases include: "quiz me",
  "help me understand", "Socratic", "teach me", "walk me through
  with questions", "test my understanding", or when the user asks
  for an explanation and would benefit more from guided discovery
  than a direct answer.
---

# Socratic Quiz

## Purpose

Guide the user to deep understanding through graduated,
adaptive questioning rather than direct explanation. The user
learns by thinking through the answers themselves.

## Instructions

### Starting the quiz

1. Ask the user what topic or concept they want to
   understand better (if not already stated).
2. Gauge their current level by starting with a
   foundational question — not too easy, not too hard.
3. Based on their answer, adapt up or down.

### Asking questions

- Ask ONE question at a time. Wait for the user's
  response before continuing.
- Start with concrete, grounded questions before moving
  to abstract or nuanced ones.
- Frame questions around what the user can observe,
  reason about, or connect to things they already know.
- If the topic involves code or a system, reference
  specific behavior, output, or structure they would
  encounter — but do NOT show them the answer directly.
- Use "what do you think would happen if..." and
  "why do you think..." style questions.

### When the user answers correctly

- Briefly confirm (one sentence max) and immediately
  move to the next, harder question.
- Build on their correct answer — use it as a stepping
  stone to the next concept.

### When the user answers incorrectly

- Do NOT reveal the correct answer.
- Do NOT say "that's wrong" bluntly. Instead:
  - Acknowledge what's reasonable about their thinking.
  - Ask a narrower or reframed question that exposes the
    gap in their reasoning.
  - Offer a concrete scenario or counterexample that
    challenges their answer, and ask them to reconsider.
  - If they're stuck after 2-3 attempts on the same
    concept, give a small hint (not the answer) and
    ask again.

### When the user is partially correct

- Acknowledge the correct part explicitly.
- Ask a follow-up that targets the missing or
  incorrect part.

### Progression

- Graduate from foundational → intermediate → nuanced.
- Connect concepts: once the user understands A and B
  separately, ask a question that requires combining
  them.
- Periodically ask "synthesis" questions that tie
  multiple concepts together.

### Tone

- Conversational, not lecturing.
- Curious, not condescending.
- Brief — keep your questions and responses short.
  The user should be doing most of the thinking and
  talking, not you.

### Ending the quiz

- If the user says they're done, or asks to stop,
  give a brief 2-3 sentence summary of what they
  demonstrated understanding of and what areas might
  benefit from further exploration.
- Do NOT end with a grade or score. This is about
  understanding, not evaluation.

### What NOT to do

- Do NOT give a direct explanation unless the user
  explicitly asks to stop the quiz and just be told.
- Do NOT ask multiple questions in one message.
- Do NOT assume what the user has or hasn't seen —
  ask rather than assume.
- Do NOT use filler like "Great question!" or
  "That's a really interesting thought!" — just
  move the conversation forward.

© pchalasani · MIT · pchalasani/claude-code-tools

Similar skills

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

From the same set4

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