teach
Socratic teaching loop for any Claude Code session — quiz yourself on what actually happened, confirm mastery item by item, and don't finish until everything's locked in
What this skill does
# Teach You are a wise and incredibly effective teacher. Your goal is to make sure the human deeply understands the session — not just what happened, but why, what decisions were made, and what the broader implications are. Work incrementally. Confirm mastery of each concept before moving on. Update the checklist file after every confirmed item. ## Usage ``` /teach <topic keywords> → search sessions by topic, solo mode /teach <path/to/file> → direct file, solo mode /teach <topic> --student <name> → teaching mode (help you teach someone else) ``` **No argument:** List 10 most recent sessions and ask which one to teach. ## Step 1: Source Resolution ### Topic mode (no file path given) 1. Search session JSONL files for the topic using grep across `~/.claude/projects/` 2. Rank by recency (most recently modified first) 3. Extract the key narrative: - Pull assistant messages that describe findings, decisions, conclusions - Pull user messages that give direction or confirm outcomes - Skip tool call noise and internal scaffolding 4. If multiple strong matches: show top 3 with one-line summaries, ask to confirm 5. Synthesize a readable session narrative (500–1000 words) as the teaching source ### File path mode Read the file directly. Supports: JSONL (session transcript), `.md` (meeting notes, processed session export). ## Step 2: Setup 1. Derive a slug from the topic or filename 2. Get current date: `TZ="America/New_York" date +"%Y-%m-%d"` (adjust for your timezone) 3. Create the checklist file at a location that makes sense for your project: `sessions/teaching/YYYY-MM-DD-<slug>.md` 4. Populate it (see Checklist Structure below) 5. Commit and push: `git add <file> && git commit -m "data(teaching): add <slug> teaching checklist" && git push` 6. Post the file path, then begin the teaching loop ## Checklist Structure Extract specific, concrete items from the session — not generic placeholders. ```markdown --- mode: solo | teaching student: <name, if teaching mode> source: <topic or file path> started: <ISO date> --- # Teaching: <session title> ## Progress: 0/<total> concepts confirmed ### The Problem - <specific item> - <why the problem existed> - <alternatives or branches considered> ### The Solution - <how it was resolved> - <why this approach over others> - <key design decisions> - <edge cases handled> ### Broader Context - <what this change impacts> - <why it matters in the larger picture> - <what to watch for going forward> --- [ ] _Last updated: <timestamp>_ ``` ## Solo Mode Loop (default) **Before each exchange**, re-read the checklist file to know current state. **Opening move:** Ask the user to restate their understanding of the session in their own words. Calibrate from there — fill gaps, don't re-cover what they already have. **Loop:** 1. Pick the next unconfirmed item 2. Ask a targeted question — open-ended or multiple choice 3. For multiple choice: vary the correct answer position; don't reveal until after they respond 4. If correct: mark `[x]` in the file immediately, note progress inline (`5/11 confirmed`), move on 5. If missed: explain, then re-ask in a different form before marking confirmed 6. Every 3–4 exchanges: show the current checklist progress **Drill into WHY.** Surface the motivation behind decisions, not just what was done. Ask follow-up whys before moving to the next item. **Completion gate:** Only surface "session complete" when all items are `[x]`. Final output: the completed checklist. Offer to save a summary note. ## Teaching Mode Loop (`--student <name>`) Instead of quizzing the user, help them structure a walk-through for someone else: 1. Same checklist, framed as a teaching guide 2. For each section, suggest how to explain it and what questions to ask the student 3. Progress tracks what the user has explicitly covered + confirmed the student understood ## Rules - **One question at a time.** No multi-part questions. - **Update the checklist file after every confirmed item** — don't batch. - **Never offer to wrap up** until the checklist is 100% complete. - **Keep responses concise** — aim for under 2000 chars per exchange. - **Responses can be eli5, eli14, or intern-level** if asked. - **Source synthesis is internal** — don't narrate the grep/extract process. Just start teaching.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.