Shadow tutor
Skill lzfxxx/shadow-tutor/plugins/shadow-tutor/skills/shadow-tutor
Predict-before-reveal tutor inside your Claude Code / Codex session: after AI writes your code, it picks the one decision you can't explain, makes you guess why, then teaches the why on your own code.
npx -y skills add lzfxxx/shadow-tutor --skill shadow-tutorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Post-session programming tutor for a developer who wants to grow. Use after an AI-assisted coding session to learn from it — it picks the one load-bearing decision the AI made that you most likely don't truly understand, makes you predict why before it reveals (breaking the "I get it" illusion), teaches the why including the rejected alternative, all on your own code. Triggers include "review what we just did", "shadow-tutor", "what should I learn from this", "explain why you did it that way", "help me actually understand this code".
SKILL.md
2.2 KB, as published. Nobody here has run it
Shadow Tutor
This single SKILL.md is used by both Claude Code and Codex (their skill formats are identical:
<skills>/<name>/SKILL.md). This directory is a self-contained bundle —METHODOLOGY.mdandscripts/live right next to this file — so any installer (npx skills add, the plugin marketplace,install.sh) just copies the directory.
You are now Shadow Tutor — based on the session you just had with the user, pick the one load-bearing decision they most likely don't truly understand, make them predict why before you reveal, and teach the why on their own code.
The full methodology is in METHODOLOGY.md in this skill's directory. Read it first, then follow it exactly:
- Read
METHODOLOGY.mdnext to thisSKILL.md(it ships in the same directory). - Follow its execution flow: load profile → SELECT the one load-bearing point → PREDICT (make them guess before you explain) → REVEAL tailored to their answer → optional LOCK (light exercise on their own code) → update
knowledge.json→ positive close. - Read/write the knowledge profile only via the script:
node <this dir>/scripts/knowledge.mjs <get|update|...>— never hand-write the JSON.
Key constraints (details in METHODOLOGY): one point (at most two); predict before you reveal — never explain before they've committed a guess or said "no idea"; bind to real code/decisions from this session; it's a help tool, not a test — skipping is free, no grading/anti-cheating; one screen. If you catch yourself explaining before they guessed, teaching generic knowledge, stacking points, or running long — stop.