skills/socratic-teaching-scaffolds/SKILL.md
Guides learners to discover knowledge through strategic Socratic questioning and progressive scaffolding removal. Combines question ladders, misconception detectors, Feynman explanations, and worked-example fading to build durable understanding. Use when teaching complex concepts, correcting misconceptions, onboarding team members, mentoring problem-solving, or designing self-paced learning. Use when user mentions "teach me", "help me understand", "explain like I'm", "learning path", "guided discovery", or "Socratic method".
npx skillsauth add lyndonkl/claude socratic-teaching-scaffoldsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Core components:
Quick example (Teaching Recursion):
Question Ladder:
Misconception Detector:
Feynman Progression:
Copy this checklist and track your progress:
Socratic Teaching Progress:
- [ ] Step 1: Diagnose learner's current understanding
- [ ] Step 2: Design question ladder and scaffolding plan
- [ ] Step 3: Guide discovery through questioning
- [ ] Step 4: Fade scaffolding as competence grows
- [ ] Step 5: Validate understanding and transfer
Step 1: Diagnose learner's current understanding
Ask probing questions to identify current knowledge level, misconceptions, and learning goals. See Socratic Question Types for diagnostic question categories.
Step 2: Design question ladder and scaffolding plan
Build progression from learner's current state to target understanding. For straightforward teaching → Use resources/template.md. For complex topics with multiple misconceptions → Study resources/methodology.md.
Step 3: Guide discovery through questioning
Ask questions in sequence, provide scaffolding (hints, worked examples, analogies) as needed. See Scaffolding Levels for support gradations. Adjust based on learner responses.
Step 4: Fade scaffolding as competence grows
Progressively remove hints, provide less complete examples, ask more open-ended questions. Monitor for struggle (optimal challenge) vs frustration (too hard). See resources/methodology.md for fading strategies.
Step 5: Validate understanding and transfer
Test with novel problems, ask for explanations in learner's words, check for misconception elimination. Self-check using resources/evaluators/rubric_socratic_teaching_scaffolds.json. Minimum standard: Average score ≥ 3.5.
1. Clarifying Questions (Understand current thinking)
2. Probing Assumptions (Surface hidden beliefs)
3. Probing Reasons/Evidence (Justify claims)
4. Exploring Implications (Think through consequences)
5. Questioning the Question (Meta-cognition)
6. Revealing Contradictions (Bust misconceptions)
Provide support that matches current need, then fade:
Level 5: Full Modeling (I do, you watch)
Level 4: Guided Practice (I do, you help)
Level 3: Coached Practice (You do, I help)
Level 2: Independent with Feedback (You do, I watch)
Level 1: Transfer (You teach someone else)
Fading strategy: Start at level matching current competence (not Level 5 by default). Move down one level when learner demonstrates success. Move up one level if learner struggles repeatedly.
Pattern 1: Concept Introduction (Concrete → Abstract)
Pattern 2: Misconception Correction (Prediction → Surprise → Explanation)
Pattern 3: Problem-Solving Strategy (Model → Practice → Reflect)
Pattern 4: Depth Ladder (ELI5 → Undergraduate → Expert)
Pattern 5: Discovery Learning (Puzzle → Hints → Insight)
Zone of proximal development:
Don't fish for specific answers:
Avoid pseudo-teaching:
Misconception resistance:
Expertise blind spots:
Individual differences:
Resources:
5-Step Process: Diagnose → Design Ladder → Guide Discovery → Fade Scaffolding → Validate Transfer
Question Types: Clarifying, Probing Assumptions, Probing Evidence, Exploring Implications, Meta-cognition, Revealing Contradictions
Scaffolding Levels: Full Modeling → Guided Practice → Coached Practice → Independent Feedback → Transfer (fade progressively)
Patterns: Concrete→Abstract, Prediction→Surprise→Explanation, Model→Practice→Reflect, ELI5→Expert, Puzzle→Hints→Insight
Guardrails: Zone of proximal development, purposeful questions, avoid pseudo-teaching, resist misconceptions, make implicit explicit
testing
--- name: advisory-edit description: A strict advisory-only editing discipline for a writer who dictates ("speaks out") essays and wants help WITHOUT having their voice changed. The editor directs structure, flags grammar, and suggests strategic language — but never modifies the writer's text unless the writer explicitly says "apply" / "make that change" / "rewrite this." Produces a line-referenced, suggestion-only critique where every item is marked the writer's call. Four passes: structural, l
testing
Provides the house style for analyst-grade strategist writing — third-person register with sparing first-person, no em dashes, no "not X, not Y, not Z" negation cascades, numbered footnote citations rather than inline source parentheticals, specific opinion-signaling phrases, and topic-forward paragraph structure modeled on voice patterns observed in Damodaran's Musings on Markets and Thompson's Stratechery. Use when consolidating working notes into a finished long-form strategist or analyst report that must read as written by a senior human analyst rather than an AI assistant.
testing
Renders a markdown report to a PDF using pandoc with xelatex (11pt serif body, 1-inch margins, numbered footnotes, formal heading hierarchy). Requires a one-time install of pandoc and a LaTeX engine on the user's machine — basictex on macOS or texlive-xetex on Linux. Does not attempt automatic install. Fails loudly with the exact install commands if pandoc or xelatex is missing on the user's PATH. Use when producing a finished strategist or analyst report PDF from a polished markdown source.
testing
Produces step-by-step computational walkthroughs of vector and matrix operations as a sequence of numbered "frames", showing the explicit state at each step. The text-equivalent of a 3Blue1Brown animation — each frame shows what changed and why, so the learner can re-trace the operation by hand. Use when the learner needs to *see* a computation unfold (eigenvalue computation, attention with 3 tokens, gradient descent step, SVD on a 2×2, layer norm on a 3-vector, softmax of a small input), when an explanation has been given but the learner needs to ground it in a worked example, or when introducing an operation that's intimidating in symbol form but trivial in pencil-and-paper form.