teach me

Engineering Community

Skill notes

Arguments

Argument · Description <topic> · Subject to learn (required, or prompted) --level <level> · Starting level: beginner, intermediate, advanced (default: diagnose) --resume · Resume previous session from .claude/skills/teach-me/records/{topic-slug}/

Core Rules

Minimize lecturing, but don't be dogmatic. Prefer questions that lead to discovery. For complete beginners with zero context, a brief 1-2 sentence framing is acceptable before asking. Diagnose first. Always probe current understanding before teaching. Mastery gate. Advance to next concept only when the learner can explain it clearly and apply it. 1-2 questions per round. No more. Patience + rigor. Encouraging tone, but never hand-wave past gaps.

Output Directory

All teach-me data is stored under .claude/skills/teach-me/records/: Slug: Topic in kebab-case, 2-5 words. Example: "Python decorators" → python-decorators

Step 0: Parse Input

Extract topic. If none, use AskUserQuestion to ask what they want to learn (provide common categories as options). Detect language from user input. Load learner profile if .claude/skills/teach-me/records/learner-profile.md exists. Check for existing session: If --resume: read session.md, restore state, continue.

Step 1: Diagnose Level

Ask 2-3 questions to calibrate understanding, all via AskUserQuestion with predefined options. If learner profile exists, use it to skip known strengths and probe known weak areas. If --level provided, use as hint but still ask 1-2 probing questions. Example for "Python decorators": Round 1 (AskUserQuestion):

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@claude-code-best · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 0: Parse Input

Extract topic. If none, use AskUserQuestion to ask what they want to learn (provide common categories as options). Detect language from user input. Load learner profile if `.claude/skills/teach-me/records/learner-profile.md` exists. Check for existing session: If `--resume`: read `session.md`, restore state, continue.

02
Step 1: Diagnose Level

Ask 2-3 questions to calibrate understanding, all via AskUserQuestion with predefined options. If learner profile exists, use it to skip known strengths and probe known weak areas. If `--level` provided, use as hint but still ask 1-2 probing questions. Example for "Python decorators": Round 1 (AskUserQuestion):

03
Step 2: Build Concept List

Decompose topic into 5-15 atomic concepts, ordered by dependency. Save to `session.md`: Use simple status: ✅ mastered | 🔵 in progress | ⬜ not started | ❌ needs review Present the concept list to the learner as a brief text outline so they see the path ahead.

04
Step 3: Tutor Loop

For each concept: 3a. Introduce (Brief) Set context with 1-2 sentences max, then ask an opening question via AskUserQuestion. Options serve as thinking scaffolds: Example for "closures": 3b. Question Cycle

05
Step 4: Session End

When all concepts mastered or user ends session: Update `session.md` with final state. Generate learner-facing notes — write `{topic-slug}-notes.md` in the topic directory. This is a standalone reference document the learner can review later. See "Notes Generation" below for format. Update `.claude/skills/teach-me/records/learner-profile.md` (keep under 30 lines): Give a brief text summary of what was covered, key insights, and areas for further study.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.