agentleFS
Sign inStart free
imMamdouhaboammarimMamdouhaboammar/matts-skills-into-chatgpt/skills/teach/SKILL.md

teach

Skill8 starsChanged 2 months agoMITView on GitHub

Teach a technical concept interactively using the workspace as an active learning lab with durable learning records. Use when the user asks to understand a codebase concept, learn a language feature, explore design patterns, or practice coding skills — even if they say \"explain how this works to me\". Do NOT use for silent autonomous code generation.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 161 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Mission-Grounded Curriculum: Every lesson, quiz, and exercise must directly anchor to MISSION.md (the learner's explicit real-world …

    line 14
  2. Very specific:

    Primary-Source Grounding: Never rely purely on model memory.

    line 18
  3. Very specific:

    Action: Check MISSION.md and existing ./learning-records/.

    line 42
  4. Distinctive:

    Key Point: Ensure claims and code patterns conform to modern best practices.

    line 48
  5. Very specific:

    Action: After the user interacts with the lesson, capture the key concepts mastered and areas for next practice in …

    line 60

“Common” is measured: kept by at least 6 in 10 of the 161 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Teach

Transform the current workspace into an interactive, stateful learning laboratory producing structured HTML lessons, reference materials, primary source bibliographies, and progressive learning records.

Core Invariants

  1. Mission-Grounded Curriculum: Every lesson, quiz, and exercise must directly anchor to MISSION.md (the learner's explicit real-world objective).
  2. Desirable Difficulty & Retrieval: Target long-term storage strength through effortful retrieval, spaced practice, and interleaved exercises over fleeting in-the-moment fluency.
  3. Beautiful HTML Artifacts: Lessons are rendered as self-contained, publication-grade HTML documents in ./lessons/000X-<name>.html styled via shared assets (./assets/style.css).
  4. Durable Learning Records: Capture key insights, non-obvious breakthroughs, and mental model shifts in ./learning-records/000X-<name>.md to maintain the Zone of Proximal Development (ZPD).
  5. Primary-Source Grounding: Never rely purely on model memory; cite and link verified primary sources in RESOURCES.md and inline lesson annotations.

Architecture & Map of Content (MOC)

[ Learner Request / Mission ] ──► [ Assess ZPD via Learning Records ] ──► [ Build HTML Lesson & Quizzes ] ──► [ Record Progress in Learning Records ]
ComponentResponsibilityFile Location / Template
Mission AnchorCore motivation and real-world goalMISSION.md (MISSION-FORMAT.md)
Lesson ArtifactsInteractive HTML lesson modules./lessons/000X-<slug>.html
Reference SheetsCheat sheets, syntax summaries, and glossaries./reference/*.html
Learning RecordsMilestone reflections and conceptual breakthroughs./learning-records/000X-<slug>.md
Shared AssetsTypography, styles, and interactive quiz widgets./assets/*
Primary SourcesVetted documentation and book referencesRESOURCES.md (RESOURCES-FORMAT.md)

Step-by-Step Procedure (TWI)

Step 1: Establish Mission and Assess Zone of Proximal Development

  • Action: Check MISSION.md and existing ./learning-records/. If uninitialized, grill the user to define their motivation and starting baseline.
  • Key Point: Frame teaching around what the user needs to do rather than abstract theory.
  • Why: Learning is significantly faster and more durable when grounded in immediate application.

Step 2: Source Primary References

  • Action: Identify and record the top primary source documentation or authoritative articles in RESOURCES.md.
  • Key Point: Ensure claims and code patterns conform to modern best practices.
  • Why: Citing primary sources builds user trust and teaches research habits.

Step 3: Author Interactive HTML Lesson

  • Action: Generate ./lessons/000X-<slug>.html linking to ./assets/style.css.
  • Key Point: Include interactive self-check questions, code snippets, and direct links to reference sheets.
  • Inline Checklist:
    • Standalone HTML opens cleanly in browser
    • Quiz answers formatted with balanced word/character counts
    • Follow-up discussion prompts included

Step 4: Record Breakthroughs in Learning Records

  • Action: After the user interacts with the lesson, capture the key concepts mastered and areas for next practice in ./learning-records/000X-<slug>.md.
  • Why: Keeps learning state synchronized across different sessions.

Anti-Rationalization Guardrails

Tempting RationalizationBinding RuleEngineering Rationale
"Dump a 2000-word explanation directly into chat."Package learning into modular HTML lessons and reference files.Chat text scrolls away; structured files provide a lasting personal library.
"Give easy multiple-choice questions with obvious answers."Enforce balanced, high-friction retrieval practice.Obvious answers create false fluency without building long-term memory.
"Teach without checking MISSION.md."Mandatory mission alignment for every lesson.Disconnected theory causes learner disengagement and rapid forgetting.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free