Markdown memory

Skill kpab/claude-fable-5-skills/skills/markdown-memory

A file-based lesson memory that Claude Fable 5 reads and maintains across sessions. Use for any recurring agent (daily jobs, long projects, team assistants) where the same corrections keep being re-made, and when bootstrapping a new agent from past session history. Fable 5 benefits from recorded lessons noticeably more than prior models did.From its SKILL.md

Install

npx -y skills add kpab/claude-fable-5-skills --skill markdown-memory

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 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.

SKILL.md

1.8 KB, 314 tokens by cl100k_base, as published. Nobody here has run it

Markdown Memory

Fable 5 is unusually good at exploiting written records of its own past mistakes and confirmed approaches. A directory of Markdown files is enough — no database required. What matters is the maintenance discipline, because a memory full of stale or duplicate notes is worse than none.

Layout

memory/
  lessons/
    one-lesson-per-file.md
  INDEX.md   # one line per lesson, regenerated when lessons change

Lesson file format

Line 1: a one-sentence summary that makes sense without opening the file.
Body: what happened, what the correct approach is, and why it mattered — the why is what generalizes.
Record both corrections (things that went wrong) and confirmations (approaches validated under pressure).

Maintenance rules

One lesson per file. If a new event refines an existing lesson, update that file; never create a near-duplicate.
Don't record what the repo, docs, or chat history already state — memory is for what's not written down elsewhere.
Delete lessons proven wrong. A confidently wrong note does more damage than a missing one.
Read INDEX.md at session start; open full lesson files only when relevant.

Bootstrapping from history

To seed memory for an existing project, review past sessions (delegating chunks to subagents if history is large), extract recurring themes and corrections, and write them as lesson files in the format above. Then make reading INDEX.md part of the standing instructions.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most docs writing skills give in 314 tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

Use third-person for skill descriptionsin 54 of 1951, across 35 files
Start descriptions with Use whenin 43 of 1951, across 29 files
Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
Use active voicein 40 of 1951, across 36 files
Map file responsibilities before defining tasksin 36 of 1951, across 29 files
Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
Ask one question at a timein 35 of 1951
Offer execution options after saving the planin 33 of 1951, across 24 files
Include complete code in every stepin 33 of 1951, across 27 files
Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
Announce the skill usage at the startin 30 of 1951
Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

Create one file per lesson
Record corrections and validated approaches
Explain why the approach matters
Delete lessons proven wrong
Extract recurring themes from past sessions

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.