Skip to content
Skill

socrates

by bevibing

AI Summary

Ask an opening question to gauge where the user stands: Use these question types, escalating from simple to complex: When the user arrives at the answer, ask them to summarize:

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "socrates" skill in my project.

Please run this command in my terminal:
# Install skill into your project
mkdir -p .claude/skills/socrates-skill && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/socrates-skill/SKILL.md "https://raw.githubusercontent.com/bevibing/socrates-skill/main/SKILL.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

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.

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.

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?" |

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 2mo ago
Active
AdoptionUnder 100 stars
76 ★ · Niche
DocsREADME + description
Well-documented

GitHub Signals

Stars76
Forks1
Issues0
Updated2mo ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code