agentleFS
Sign inStart free
LearnPromptLearnPrompt/cc-harness-skills/skills/dream-memory/SKILL.md

dream-memory

Skill236 starsChanged 8 months agoMITView on GitHub

Consolidate recent logs, sessions, and existing memory files into durable topic memories, normalize dates, prune stale entries, and keep MEMORY.md short enough for prompt use.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. matthewwong525/WongStack★ 7same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

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
  1. Distinctive:

    Use this skill when you want a deliberate memory-consolidation pass instead of storing more raw notes.

    line 8
  2. Distinctive:

    Remove stale or contradicted memory.

    line 41
  3. Distinctive:

    Prefer topic merges over new file creation.

    line 47
  4. Distinctive:

    Do not store code-state facts that can drift.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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

Dream Memory

Use this skill when you want a deliberate memory-consolidation pass instead of storing more raw notes.

This bundle is intentionally portable. It borrows the workflow shape from Claude Code's dream system, but it does not depend on Claude Code internals.

Use It For

  • nightly or manual memory cleanup
  • merging overlapping memory notes
  • normalizing relative dates into absolute dates
  • pruning stale or contradicted memories
  • keeping MEMORY.md small and index-like

Avoid It For

  • saving a single new memory from the current turn
  • persisting code facts that should be re-read from source
  • replacing plans, task boards, or issue trackers

Quick Start

Inspect a memory directory before running the consolidation prompt:

python3 {baseDir}/scripts/dream_memory.py --memory-root /path/to/memory --transcripts-dir /path/to/transcripts

Then use the portable prompt in references/prompt-template.md.

Workflow

  1. Inspect MEMORY.md, topic files, and recent logs or transcripts.
  2. Identify durable facts worth keeping.
  3. Merge into topic files instead of creating near-duplicates.
  4. Remove stale or contradicted memory.
  5. Rewrite MEMORY.md as a concise index.

Rules

  • MEMORY.md is an index, not a content dump.
  • Prefer topic merges over new file creation.
  • Convert relative dates to absolute dates.
  • Do not store code-state facts that can drift.

Supporting Files

  • Prompt template: references/prompt-template.md
  • Source notes: references/source-notes.md
  • Helper script: python3 {baseDir}/scripts/dream_memory.py ...

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