/socratic-quiz
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
$ npx -y skills add pchalasani/claude-code-tools --skill socratic-quiz --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/socratic-quiz
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
socratic-quiz.SKILL.mdname: 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.
Read more
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.
Practical productivity tools for Claude Code, Codex-CLI, and similar CLI coding agents.
Repo: pchalasani/claude-code-tools
Other skills on claude-code-tools.
- /recover-context
Extract full context of the last task from the most recent parent session
Open skill - /session-search
For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.
Open skill - /dynamic-workflow
Create, review, run, inspect, pause, resume, and cancel durable JavaScript workflows that coordinate multiple headless Codex agents. Use for dynamic fan-out and fan-in, per-item analysis, multi-stage agent pipelines, loops or branches driven by worker results, long background
Open skill - /add-pattern
Use this skill when you learn one or more design pattern(s) in the
Open skill - /patterns
Design patterns for the Langroid multi-agent LLM framework. Covers
Open skill - /msg
Inter-agent communication via the msg CLI. Use this when you need to send messages to other agent sessions, read incoming messages, or coordinate with other agents in tmux panes.
Open skill

