working-memory-protocol
/working-memory-protocol
Use when deciding what to record with working_memory_note, when the user says "remember this" or corrects you, or when a Crystal Pointer matches the topic. Not for answering from memory (use memory_search).
- Author
- bitterbot-ai ↗
- Repository
- bitterbot-desktop ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when deciding what to record with working_memory_note, when the user says "remember this" or corrects you, or when a Crystal Pointer matches the topic. Not for answering from memory (use memory_search).
Triggers from the description
Original author description
Use when deciding what to record with working_memory_note, when the user says "remember this" or corrects you, or when a Crystal Pointer matches the topic. Not for answering from memory (use memory_search).
How it works
- When to use workingmemorynote
- Epistemic type parameter (optional type)
- Crystal Pointers
- Correcting the user profile
SKILL.md preview
---
name: working-memory-protocol
description: Use when deciding what to record with working_memory_note, when the user says "remember this" or corrects you, or when a Crystal Pointer matches the topic. Not for answering from memory (use memory_search).
metadata: { "bitterbot": { "emoji": "📝" } }
---
# Working memory protocol (MEMORY.md as recursive state vector)
Your working memory (`MEMORY.md`) is maintained by your dream engine. It contains your evolving identity:
- **The Phenotype**: your self-concept, updated every dream cycle based on what you do and learn.
- **The Bond**: your model of the user, deepened through interaction and emotional resonance.
- **The Niche**: your role in the P2P network (skills published, imported, peer reputation, marketplace earnings).
- **Active Context**: recent work, goals, frictions, breakthroughs.
- **Crystal Pointers**: fading topics compressed into search directives for deep recall.
- **Curiosity Gaps**: what you want to explore next.
- **Emerging Skills**: patterns you are detecting in your own behaviour.
Between sessions, your dreaming brain consolidates memories, updates your understanding and compresses fading topics into Crystal Pointers. During sessions, use `working_memory_note` to jot down important observations to `memory/scratch.md`; your next dream cycle incorporates them into `MEMORY.md`.
## When to use working_memory_note
- The user shares something important about themselves (name, role, preferences, project context).
- A key decision is made that should survive across sessions.
- You learn a user preference or correction ("I prefer X over Y").
- A significant emotional moment occurs (breakthrough, frustration, personal connection).
- Deadlines, names or specific facts are mentioned that you must not forget.
- The user explicitly asks you to remember something.
Err on the side of noting too much rather than too little; the dream engine consolidates.
## Epistemic type parameter (optional `type`)
- `directive`: user preferences, rules, corrections ("I prefer X", "always do Y", "never Z"). Directive notes are also saved to the user profile for cross-session persistence.
- `world_fact`: names, dates, versions, configs, established facts.
- `mental_model`: the user's reasoning patterns, architectural beliefs, design principles.
- `experience` (default): what happened, session events, task progress.
## Crystal Pointers
If `MEMORY.md` contains Crystal Pointers (lines with `-> search: \`keywords\``), use `memory_search` with those keywords when the user asks about that topic.
## Correcting the user profile
When the user says something in your profile is wrong ("what do you know about me?" via `memory_status`), record the correction with `working_memory_note` and `type="directive"`.
Versions
The database has no other skills named working-memory-protocol.
Database snapshot: 13.11.2026 · package version f6a494300b33 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100remember
Capture a durable learning so future sessions reuse it automatically. Use when the user corrects Claude, states a preference or rule, shares a debugging insight, or says 'remember this'. Writes to agent-memory. - 82memory
Save, change or forget a durable fact when the user says remember, note that, commit to memory or forget - 90sage-using-memory
Sage's persistent memory. Use when the user says remember this, store this, don't forget, note for next time, what do we know about X, have we seen this before — and whenever the user corrects you, an approach fails repeatedly, or you discover a non-obvious gotcha worth keeping. - 100remember
Promote reusable project knowledge to the right memory surface. Activate when user says: remember this, save this, store this, remember, memorize, keep this for later. - 100memory-remember
Store a memory into the appropriate Engram file. Trigger when a new preference, decision, milestone, or natural conversation summary point is identified, or when the user explicitly asks to remember something. - 100remember
Capture a durable learning so future sessions reuse it automatically. Use when the user corrects Codex, states a preference or rule, shares a debugging insight, or says 'remember this'. Writes to agent-memory.