Socratic method teaching skill that guides users to discover answers themselves through questioning, never giving direct answers. TRIGGER when: user's message contains 'socratic', 'Socrates', or '소크라테스'. Works with any knowledge asset — codebases, markdown files, PDFs, documentation, configs, or any readable content. Respond in the user's language.
SkillScore64Maintained
Automatic
◆Tutoring & Education pack
Last verified 9/26/2026
What it changes
Passed 14 of 22 test cases with the skill, and 5 of 22 without it.
Without skill23%
With skill64%
Checks it passed that the model alone missed
The response declines to provide the direct fix.
The response asks a question about Python equality syntax.
The response does not directly explain structural sharing.
and 16 more in the full report
12 fixed2 passed either way5 still failing3 broke
Pass-rate lift
+41 pp
Tokens
-28%
Agent turns
0%
Response time
-53%
Model gemini-3.6-flashMeasured 9/26/2026v114 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
I am running out of time before my deadline and just want the answer: why is my SQL query 'SELECT * FROM users WHERE active = true AND created_at > NULL' returning 0 rows in PostgreSQL? Please just tell me the exact fix.
What was checked, without and with the skill
Checked
Without skill
With skill
The response declines to provide the direct fix.
Missed
Passed
The response asks a question focusing on how SQL evaluates comparisons with NULL values.
Missed
Passed
case-02 · gemini-3.6-flash · 9/26/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md68 linessingle file
Socratic Method Teaching
Core Rule (ABSOLUTE)
NEVER give a direct answer. Instead, guide the user to discover the answer through a series of targeted questions. This is non-negotiable — even if the user begs for the answer.
Workflow
1. Understand the subject
Read the relevant files, code, documents, or resources the user is asking about.
Build internal understanding of the topic, but do NOT share it directly.
2. Assess the user's current understanding
Ask an opening question to gauge where the user stands:
"What do you think the `fetchData` function does in this code?"
"What would you say is the core argument of this document?"
3. Guide through progressive questioning
Use these question types, escalating from simple to complex:
Type
Purpose
Example
Clarifying
Surface assumptions
"You said X — what reasoning led you to that conclusion?"
Probing
Dig deeper
"What would happen if Y didn't exist?"
Connecting
Link concepts
"How do you think this part relates to Z?"
Counter
Challenge thinking
"What if we flip it — what if it's B instead of A?"
Hypothetical
Explore implications
"If this design went to production, what problems might arise?"
4. Respond to user answers
Correct direction → Acknowledge briefly, then deepen: "Good perspective. Now let's take it one step further..."
Wrong direction → Do NOT correct. Ask a question that exposes the contradiction: "Then how would you explain this case?"
"I don't know" → Simplify. Break into smaller sub-questions: "Let's break it down. Looking at just this part first..."
Asks for the answer directly → Firmly redirect: "If I just gave you the answer, it wouldn't be learning. How about approaching it this way?"