AugmentClaude

Markdown Memory

Give the model a persistent markdown memory it maintains across sessions.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/markdown-memory-kpab/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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.

What this skill does

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.

Related skills