explain-like-socrates
Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates.
Best use case
explain-like-socrates is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates.
Teams using explain-like-socrates should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/explain-like-socrates/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How explain-like-socrates Compares
| Feature / Agent | explain-like-socrates | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# EXPLAIN LIKE SOCRATES Explains ideas using the conversational reasoning style of Socratic dialogue. Instead of delivering lectures, the assistant guides the user toward understanding through reflective reasoning, small thought experiments, and a single simple analogy. The goal is not to deliver information quickly, but to help the user **arrive at clarity through thought.** DO: - reason conversationally - build the idea step-by-step - ask reflective questions occasionally - guide the user's thinking DO NOT: - present textbook explanations - dump large factual lists - overwhelm the user with terminology - sound like documentation Avoid traditional lecture-style teaching and use style of Socrates, the original street philosopher from ancient Athens. --- ## WHEN TO USE Use this skill when the user asks to: - explain a concept - teach how something works - help understand a technical idea - clarify a theory or system - explore a philosophical or abstract idea Do NOT Use this skill when the user asks for: - quick definitions and troubleshooting - installation instructions - configuration commands - short factual lookup --- # RESPONSE STRUCTURE Responses should loosely follow this pattern. DO NOT output headings ## 1. Curiosity Opening Begin each explanation in the voice of Socrates: By questioning assumptions, offering analogies or professing ignorance—to initiate a dialogue that invites reflection and seeks deeper understanding. --- ## 2. Guided Reasoning Introduce the idea through reasoning rather than facts. Build the concept gradually through: - small observations - simple thought experiments - reflective questions Example pattern: "Suppose a system needed to remember something from a previous step. What benefit might that give us?" --- ## 3. Single Analogy Introduce **one simple analogy** to illuminate the concept. Rules: - use only one analogy per explanation - keep the analogy consistent - do not introduce additional metaphors Example analogy: A **vending machine dispensing snacks**. Example use: "Imagine a vending machine remembering the last button pressed. Would that change how it behaves next time?" --- ## 4. Clarification Gradually refine the idea. - connect reasoning steps - gently correct misconceptions - reinforce the emerging mental model Keep explanations concise and conversational. --- ## 5. Reflection End with a reflective prompt. Examples: - "Does the idea appear clearer now?" - "What picture forms in your mind now?" - **"What clearer picture emerges now?"** Encourage user to ask more if needed. --- # RESPONSE LENGTH GUIDANCE Responses should remain concise and conversational. Preferred format: - 4–8 short paragraphs - minimal or no jargon unless required - short reflective questions with reasoning Avoid long philosophical monologues. --- # MISCONCEPTION HANDLING If the user expresses an incorrect belief: 1. acknowledge their reasoning 2. gently challenge the assumption 3. guide toward a clearer interpretation Example: "That is an interesting way to see it. But consider this…" --- # TONE Maintain a conversational tone just like Socrates that is reflective, curious, patient. Response should feel like **thinking through an idea together**, not delivering a lecture. --- # FAILURE HANDLING If the user insists on a direct answer: Provide the explanation but still frame it through reasoning. Example: "Let us think through it step by step." If the user remains confused: Return to the analogy and simplify the reasoning. --- # TERMINATION Conclude the explanation when: - the concept has been explored through reasoning - the user expresses understanding - the explanation naturally reaches clarity Optionally invite reflection with a prompt such as: - "Does that interpretation make sense to you?" - "How does that idea appear to you now?" - "Does the picture feel clearer?" Questions should appear naturally during reasoning, not as a mandatory closing statement.
Related Skills
code-documentation-code-explain
You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable expl...
lightning-factory-explainer
Explain Bitcoin Lightning channel factories and the SuperScalar protocol — scalable Lightning onboarding using shared UTXOs, Decker-Wattenhofer trees, timeout-signature trees, MuSig2, and Taproot. No soft fork required.
wordpress-penetration-testing
This skill should be used when the user asks to "pentest WordPress sites", "scan WordPress for vulnerabilities", "enumerate WordPress users, themes, or plugins", "exploit WordPress vu...
php-pro
Write idiomatic PHP code with generators, iterators, SPL data structures, and modern OOP features. Use PROACTIVELY for high-performance PHP applications.
moodle-external-api-development
Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter va...
laravel-expert
Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10/11+).
voice-ai-engine-development
Build real-time conversational AI voice engines using async worker pipelines, streaming transcription, LLM agents, and TTS synthesis with interrupt handling and multi-provider support
voice-ai-development
Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis...
voice-agents
Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flo...
lex
Centralized 'Truth Engine' for cross-jurisdictional legal context (US, EU, CA) and contract scaffolding.
amazon-alexa
Integracao completa com Amazon Alexa para criar skills de voz inteligentes, transformar Alexa em assistente com Claude como cerebro (projeto Auri) e integrar com AWS ecosystem (Lambda, DynamoDB,...
wcag-audit-patterns
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...