/ ディレクトリ / プレイグラウンド / socrates-skill
← 全サーバー ↗ GitHub
● コミュニティ bevibing ⚡ 即起動

socrates-skill

作者 bevibing · bevibing/socrates-skill

Turns Claude into a Socratic tutor that refuses to give direct answers — guides you through questioning on code, docs, PDFs, configs.

Activated by including 'Socrates', 'socratic', or 소크라테스 in your message. Claude reads the material silently, assesses your level, asks progressively deeper questions, adapts difficulty from your responses, then asks you to summarize. The key rule: never a direct answer, even if you beg. Detects and responds in your language.

▶ デモを見る 📦 インストール 💡 ユースケース

なぜ使うのか

主な機能

ライブデモ

実際の動作

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.

フロー
  1. 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?'
  2. Answer iteratively
    Answer honestly where you're unsure.✓ コピーしました
    → Questions adapt to your depth of understanding
  3. 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.

フロー
  1. Point Claude at the PDF
    Socrates — guide me through this paper's core argument. Start with the setup.✓ コピーしました
    → Opens with a gauge question
  2. 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.

フロー
  1. 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
  2. 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 chatYou just need the answer and will learn separatelyNo forced understanding

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る