Memory

Persist user preferences and notes in prompt-include memory markdown files.

5|Updated May 6, 2026
One-click install
npx skills add https://github.com/binary16labs/prime-silo --skill memory-binary16labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Memory
Source: https://github.com/binary16labs/prime-silo/tree/main/app/L0/_all/mod/_core/memory/ext/skills/memory
Command: npx skills add https://github.com/binary16labs/prime-silo --skill memory-binary16labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of forgetting important user preferences, stable instructions, and evolving context by turning meaningful chat outcomes into persistent prompt-include memory files.

Core Features & Use Cases

  • Stable behavior memory: Store long-lived preferences and standing instructions in behavior.system.include.md so the system prompt stays consistent over time.
  • Rolling, transferable context: Keep frequently updated notes in memories.transient.include.md and topic-focused *.transient.include.md files to carry useful facts forward.
  • Operational update discipline: Encourage incremental and focused file mutations after meaningful progress so memory stays concise, current, and non-duplicative.

Quick Start

Update your durable behavior and future context by telling the assistant what you want to remember, then instruct it to write the change into the appropriate file under ~/memory/.

Frequently Asked Questions about Memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist user preferences and context across multiple AI assistant conversations?

You can persist context across conversations by writing preferences and notes into `*.system.include.md` and `*.transient.include.md` files. The assistant maps these markdown files to system-prompt instructions, carrying stable behavior and rolling context forward.

What is the best way to maintain long-lived instructions in a system prompt over time?

Maintaining long-lived instructions involves storing them in `behavior.system.include.md` under the `~/memory/` directory. This ensures standing preferences are consistently applied to the system prompt across all future longitudinal interactions.

How do I update persistent memory files without creating duplicate context?

Update memory files by making incremental and focused mutations to the correct `~/memory/...include.md` paths after meaningful progress. This operational discipline keeps file content concise, current, and non-duplicative.

When should I use transient context files versus stable behavior memory files?

Use `behavior.system.include.md` for stable, long-lived preferences and instructions, and use `*.transient.include.md` files for frequently updated, rolling, or topic-focused facts that carry useful context forward temporarily.

Can I use markdown files to manage evolving project context for longitudinal assistant interactions?

Yes, you can manage evolving project context by instructing the assistant to write updates into topic-focused `*.transient.include.md` memory files. This carries useful facts forward across longitudinal interactions.

Does context persistence with prompt-include files require any external dependencies?

No, context persistence with prompt-include markdown files requires no external dependencies. It solely relies on mapping `*.system.include.md` and `*.transient.include.md` paths to system-prompt instructions.