socrates-skill

왜 쓰나요

핵심 기능

Never gives direct answers — enforces discovery
Works on code, docs, PDFs, configs, papers
Five-step loop: read -> assess -> guide -> adapt -> confirm
Auto-detects user language
Activated by keyword — no per-message ceremony

라이브 데모

실제 사용 모습

socrates-skill.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: socrates-skill

Understand an unfamiliar codebase deeply

👤 Engineers onboarding to a new codebase ⏱ ~45 min intermediate

언제 쓸까: You inherited a codebase and want to learn it, not just skim.

흐름

Ask Socratic to guide you through the auth flow

Socratic: help me understand the authentication flow in this repo. Start from the first request.✓ 복사됨

→ Claude asks: 'Where does the request first hit your code? Which file?'
Answer iteratively

Answer honestly where you're unsure.✓ 복사됨

→ Questions adapt to your depth of understanding
Summarize

At the end, summarize the flow — Claude confirms or corrects via more questions.✓ 복사됨

→ You wrote the summary, not Claude

결과: You actually understand the flow, verified by your own summary.

함정

Getting frustrated and begging for the answer — That's the point — the skill enforces. Step away and come back if stuck.

함께 쓰기: filesystem

Work through a research paper with a Socratic guide

👤 Researchers, grad students ⏱ ~60 min intermediate

언제 쓸까: A paper is dense and you want to internalize the argument, not skim.

흐름

Point Claude at the PDF

Socrates — guide me through this paper's core argument. Start with the setup.✓ 복사됨

→ Opens with a gauge question
Iterate

Answer and ask for clarification when needed.✓ 복사됨

→ Progression from setup -> method -> results -> limits

결과: A clear mental model of the paper that survives your next conversation about it.

함께 쓰기: arxiv

Debug a tricky performance issue through guided questioning

👤 Engineers who want to reason about a bug, not just take a fix ⏱ ~45 min advanced

언제 쓸까: A non-obvious performance or concurrency bug you want to really understand.

흐름

Describe symptoms

Use socratic method to explore performance issues in this code. Here are the symptoms.✓ 복사됨

→ Claude asks what you've measured, not what you suspect
Follow the questioning

Run the measurements Claude suggests; report back.✓ 복사됨

→ Funnel narrows to the actual cause

결과: You found the root cause and can explain it.

함께 쓰기: chrome-devtools

조합

다른 MCP와 조합해 10배 효율

socrates-skill + filesystem

Claude reads source files silently before questioning

Socratic: walk me through the billing logic — read src/billing/ first.✓ 복사됨

socrates-skill + arxiv

Pair with arxiv to pull papers Claude will guide you through

Pull the RLHF paper from arxiv, then socratically teach me.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
socratic_guide	material + goal	Include 'socratic' / 'socrates' / 소크라테스 in your message	0

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Low per turn; high across a long session
금액: Free
팁: Use a mid-tier model — Opus is overkill for Socratic questioning

보안

권한, 시크릿, 파급범위

자격 증명 저장: None

데이터 외부 송신: None beyond the model call

문제 해결

자주 발생하는 오류와 해결

Claude gives direct answers anyway

Reinforce by saying 'stick to Socratic method — no direct answers'

Questions feel too basic

Tell it your starting level: 'assume I know X'

대안

socrates-skill 다른 것과 비교

대안	언제 쓰나	단점/장점
Regular chat	You just need the answer and will learn separately	No forced understanding