ChatGPT Claude Codex CLI Cohere Cursor DeepSeek Gemini GitHub Copilot GLM Grok Kimi Llama MiniMax Mistral OpenAI opencode Skill

explain-like-socrates

Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates.

LLM Mart · 0 points · 15 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download sickn33-agentic-awesome-skills-skills_explain-like-socrates-286166a.zip · 2 KB
Part of sickn33/agentic-awesome-skills — 427 skills
This skill couldn't be refreshed from GitHub on the last check — you're seeing the last imported snapshot.

Install

skills CLI npx skills add https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/explain-like-socrates
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install sickn33-agentic-awesome-skills@llmmart
Git git clone https://github.com/sickn33/agentic-awesome-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole sickn33/agentic-awesome-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Files (agentic-awesome-skills)
  • SKILL.md 4.4 KB
    ---
    name: explain-like-socrates
    description: >
      Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates.
    risk: safe
    source: original
    date_added: "2026-03-11"
    ---
    
    # 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.
    
    ## Limitations
    - Use this skill only when the task clearly matches the scope described above.
    - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
    - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related