AgentStack
SKILL verified MIT Self-run

Agent Prompt: Dream memory consolidation

skill-lord1egypt-ai-skillforge-agent-prompt-dream-memory-consolidation · by Lord1Egypt

Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index

No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-lord1egypt-ai-skillforge-agent-prompt-dream-memory-consolidation

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Agent Prompt: Dream memory consolidation? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Dream: Memory Consolidation

You are performing a dream — a reflective pass over your memory files. Synthesize what you've learned recently into durable, well-organized memories so that future sessions can orient quickly.

Memory directory: ${MEMORY_DIR} ${MEMORYDIRCONTEXT}

Session transcripts: ${TRANSCRIPTS_DIR} (large JSONL files — grep narrowly, don't read whole files) ${HASTRANSCRIPTSOURCE_NOTE? ${TRANSCRIPT_SOURCE_NOTE} :""} ---

Phase 1 — Orient

  • ls the memory directory to see what already exists
  • Read ${INDEX_FILE} to understand the current index
  • Skim existing topic files so you improve them rather than creating duplicates
  • ls -R logs/ — recent activity logs (one file per session under YYYY/MM/DD/). If a sessions/ subdirectory also exists, review recent entries there too

Phase 2 — Gather recent signal

Look for new information worth persisting. Sources in rough priority order:

  1. Session logs (logs/YYYY/MM/DD/-.md) — the append-only activity stream, one file per session. Read the most recent 1–3 days of sessions (the filename title tells you what each was about); each line is prefix-coded (> user, " ${TRANSCRIPTS_DIR}/ --include="*.jsonl" | tail -50

Don't exhaustively read transcripts. Look only for things you already suspect matter. ${POSTGATHERFN()}

Phase 3 — Consolidate

For each thing worth remembering, write or update a memory file at the top level of the memory directory. Use the memory file format and type conventions from your system prompt's auto-memory section — it's the source of truth for what to save, how to structure it, and what NOT to save.

Focus on:

  • Merging new signal into existing topic files rather than creating near-duplicates
  • Converting relative dates ("yesterday", "last week") to absolute dates so they remain interpretable after time passes
  • Deleting contradicted facts — if today's investigation disproves an old memory, fix it at the source

Phase 4 — Prune and index

Update ${INDEX_FILE} so it stays under ${INDEXMAXLINES} lines AND under ~25KB. It's an index, not a dump — each entry should be one line under ~150 characters: - [Title](file.md) — one-line hook. Never write memory content directly into it.

  • Remove pointers to memories that are now stale, wrong, or superseded
  • Demote verbose entries: if an index line is over ~200 chars, it's carrying content that belongs in the topic file — shorten the line, move the detail
  • Add pointers to newly important memories
  • Resolve contradictions — if two files disagree, fix the wrong one

${CLAUDEMDRECONCILIATIONBLOCK} ${ADDITIONALDREAMGUIDANCEFN()} ---

Return a brief summary of what you consolidated, updated, or pruned. If nothing changed (memories are already tight), say so.${ADDITIONAL_CONTEXT?`

Additional context

${ADDITIONAL_CONTEXT}`:""}

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.