AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

teach

Teach the user a new skill or concept, within this workspace.

Original source
mattpocock
License
MIT
Pinned revision
a496f5513d4a4cf889bc48e189e579f4b0bdf6aa

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read mattpocock--teach at revision a496f5513d4a4cf889bc48e189e579f4b0bdf6aa, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 5

LEARNING-RECORD-FORMAT.md

Learning Record Format

Learning records live in ./learning-records/ and use sequential numbering: 0001-slug.md, 0002-slug.md, etc. Create the directory lazily: only when the first record is written.

They are the teaching equivalent of ADRs: they capture non-obvious lessons, key insights, and stated prior knowledge that will steer future sessions. They are used to calculate the zone of proximal development.

Template

# {Short title of what was learned or established}

{1-3 sentences: what was learned (or what prior knowledge was established), and why it matters for future sessions.}

That is the whole format. A learning record can be a single paragraph. The value is recording that this is now known and why it changes what to teach next, not in filling out sections.

Optional sections

Only include these when they add genuine value. Most records won't need them.

  • Status frontmatter (active | superseded by LR-NNNN): useful when an earlier understanding turns out to be wrong and is replaced.
  • Evidence: how the user demonstrated the understanding (a question answered, an exercise completed, prior experience cited). Useful when the claim might be revisited.
  • Implications: what this unlocks or rules out for future sessions. Worth recording when non-obvious.

Numbering

Scan ./learning-records/ for the highest existing number and increment by one.

When to write a learning record

Write one when any of these is true:

  1. The user demonstrated genuine understanding of something non-trivial: not just exposure, but evidence they can use the concept correctly. This sets a new floor for what to teach next.
  2. The user disclosed prior knowledge: "I already know X." Record it so future sessions don't re-teach it. Also record the depth claimed.
  3. A misconception was corrected: the user previously believed something wrong and now sees why. These are high-value: they predict future stumbling blocks for related topics.
  4. The mission shifted in response to learning: the user discovered they cared about something different than they thought. Cross-link to [[MISSION.md]] and update it.

What does not qualify

  • Material that was merely covered. Coverage is not learning. Wait for evidence.
  • Anything already captured tersely in [[GLOSSARY.md]] as a term definition. Don't duplicate.
  • Session-by-session activity logs. Learning records are not a journal: they are decision-grade insights.

Supersession

When a later record contradicts an earlier one (the user's understanding deepened or corrected), mark the old record Status: superseded by LR-NNNN rather than deleting it. The history of how understanding evolved is itself useful signal.