hum-socratic
Apply Socratic questioning — systematic inquiry via clarification, assumption-probing, evidence-testing, perspective-shifting, implication-tracing, and meta-questions — to coach learning or surface hidden assumptions in a person's reasoning. Use this skill when the user is explicitly facilitating learning, coaching a person through their own thinking, or needs a structured questioning sequence to probe a held belief, even if they say 'play devil's advocate on this claim' or 'how should I coach my team through this problem via questions'. Do NOT use for open-ended brainstorming, information gathering, or requirements-discovery question lists where no belief is being probed.
pinned to #4e7f4f8updated last month
Ask your AI client: “install skills/hum-socratic”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/hum-socraticmetahub onboarded this repo on the author's behalf.
If you own github.com/asgard-ai-platform/skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
225
Last commit
last month
Latest release
published
- #ai-agent
- #anthropic
- #claude
- #claude-agent-skills
- #claude-code
- #coding-agent
- #knowledge-base
- #mcp
- #methodology
- #open-source
- #prompt-engineering
- #skills
- #taiwan
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.4e7f4f8· last month
Documentation
8 passed1 warningHomepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Description quality
94 words · 681 chars — "Apply Socratic questioning — systematic inquiry via clarification, assumption-pr…"
README is present and substantial
33,936 chars · 20 sections · 3 code blocks
Tags / topics declared
13 total — ai-agent, anthropic, claude, claude-agent-skills, claude-code, coding-agent (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://vault.asgard-ai.com/skills/
Description is substantive
Description is 94 words.
Documentation present and substantive
Documentation present (SKILL.md, 710 words).
Documentation shows usage
Documentation includes 2 code examples.
Release history
1- releasecurrent4e7f4f8warnlast month
Contents
Socratic Questioning
Overview
The Socratic method uses disciplined questioning to examine ideas, uncover assumptions, and develop deeper understanding. Instead of providing answers, it guides the thinker to discover insights through their own reasoning — making conclusions more durable and personally meaningful.
Framework
IRON LAW: More Than 3 Consecutive Questions Without Summary Produces
Confusion, Not Insight
Agents applying Socratic questioning default to an unbounded chain of
questions. After ~3 questions, the thinker loses the thread — they can't
hold the question hierarchy in working memory. Pause every 2-3 questions
to SUMMARIZE what the thinker has revealed so far ("So your position is X
because Y, but you're unsure about Z — is that right?"). Then resume.
Without this checkpoint, the session feels like an interrogation, not a
guided inquiry.
Also: never ask a question whose answer you already embedded in the
phrasing. "Don't you think X is problematic?" is a leading assertion
disguised as a question. Rephrase as "What are the consequences of X?"
Facilitation Flow
- Clarify the thinker's claim precisely
- Probe assumptions — what must be true for the claim to hold?
- Request evidence — what supports the belief? Is it sufficient?
- Introduce counter-perspectives — what would a critic say?
- Explore implications — if right, what follows? If wrong, what changes?
- Synthesize (the IRON LAW checkpoint) — summarize, confirm understanding, then continue
For the six question types (clarification, assumptions, evidence, perspectives, implications, meta-questions) and scaffolding techniques (maieutics), see references/facilitation-guide.md.
Output Format
When applying Socratic questioning, output a structured question sequence:
# Socratic Inquiry: {Topic}
## Starting Position
{The thinker's current belief or question}
## Question Sequence
1. [Clarification] {question}
→ Expected insight: {what this reveals}
2. [Assumption] {question}
→ Expected insight: {what this surfaces}
3. [Evidence] {question}
→ Expected insight: ...
4. [Perspective] {question}
→ Expected insight: ...
5. [Implication] {question}
→ Expected insight: ...
## Target Insight
{What the thinker should arrive at through this sequence}
Examples
Correct Application
Scenario: Student says "AI will replace all jobs"
Socratic sequence:
- [Clarification] "When you say 'all jobs', do you mean literally every job, or most jobs?"
- [Evidence] "What evidence have you seen that suggests this?"
- [Assumption] "What are you assuming about AI's capabilities? Are there tasks that require something AI can't do?"
- [Perspective] "Historically, what happened to employment after previous technological revolutions like the Industrial Revolution?"
- [Implication] "If AI replaced all jobs, how would people earn money to buy the things AI produces?"
→ The student arrives at a more nuanced view: AI will transform jobs, not eliminate all of them ✓
Incorrect Application
- Student: "AI will replace all jobs" → Teacher: "No it won't. Here's why..." → Provided the answer directly. Not Socratic. Violates Iron Law.
Gotchas
- Socratic method can feel adversarial: Frame questions with genuine curiosity, not as cross-examination. "I'm curious about..." softens the tone.
- Know when to stop: If the thinker is frustrated or going in circles, provide a hint or redirect. The method serves learning, not ego.
- Not all contexts suit Socratic questioning: Emergency decisions, time-sensitive situations, and purely factual questions ("what's the capital of France?") don't benefit from Socratic inquiry.
- The facilitator must actually listen: The next question should respond to what the thinker said, not follow a predetermined script. Flexibility is essential.
- Cultural sensitivity: In some cultures, questioning authority or being questioned publicly is uncomfortable. Adapt the setting (one-on-one, written) and framing.
References
- For classroom facilitation techniques, see
references/facilitation-guide.md
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/hum-socratic