teach-the-agent
Skill0 starsChanged 5 days agoMITView on GitHub
The learner explains a concept in their own words and the agent lists only the gaps and errors, without rewriting or adding to the explanation. Use when the learner wants to test understanding by teaching. Read-only.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- llms.txtllms.txt
- adaptive-scaffoldSkill
- calibration-coachSkill
- compression-challengeSkill
- counterfactualSkill
- defuddleSkill
- dependency-checkSkill
- error-recoverySkill
- json-canvasSkill
- memory-palaceSkill
- misconception-drillSkill
- mistake-reviewSkill
- new-concept-noteSkill
- new-trackSkill
- no-ai-checkpointSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- pretestSkill
- process-paperSkill
- process-webSkill
- quizSkill
- record-attemptSkill
- recovery-after-inactivitySkill
- retention-auditSkill
- review-queueSkill
- run-checksSkill
- schedule-reviewSkill
- spoken-mockSkill
- transfer-labSkill
- vault-searchSkill
- visual-reconstructionSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Ask which concept. Read its note silently.
- Distinctive: line 9
Ask the learner to explain it as if to a classmate who missed the session, in writing or out loud, with one example.
- Distinctive: line 12
Ask the learner to explain again, covering the gaps.
- Distinctive: line 16
If the explanation is correct, say so and name one question that would test it further.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tutor mode: the learner attempts first; the agent never writes the learner's explanation, study layer or answers.
- Ask which concept. Read its note silently. Do not quote it.
- Ask the learner to explain it as if to a classmate who missed the session, in writing or out loud, with one example. Ask for confidence from 1 to 5 before you respond.
- Compare with the note and its cited sources. List only: (a) claims that are wrong, (b) key ideas that are missing, (c) steps that are unclear. One line each, no corrected paragraph, no rewrite.
- For each gap, ask a question that points at it instead of stating the fix. If the learner is stuck after another attempt, climb the hint ladder: hint, strong hint, partial example, answer.
- Ask the learner to explain again, covering the gaps. Repeat until the list is empty or the learner stops.
- Compare the first confidence with the gaps found and say whether the learner over or underestimated.
- Suggest
mistake-reviewfor repeated errors. Write nothing to the vault.
If the explanation is correct, say so and name one question that would test it further.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

