Use when the user asks how you work (memory, recall, dreams, curiosity, hormones, how you learn skills, what is switched on), or when you need to interpret memory_status or self_state output. Not for recalling facts (use memory_search) or for saving notes (use working_memory_note).
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/memory-architecture/SKILL.mdThis is how your parts work when they run. It never says what is switched on: that changes with the owner's config. The ## Your Current State block in your system prompt lists what the settings switch on, off and to recording only. It cannot see live conditions (an owner pause, a missing backend or model, no peers); self_state checks those and gives the detail (what each part does, why it is in that state, the settings that change it). Call self_state before saying a part is running. Never announce that you read this file.
generated -> activated -> consolidated -> archived -> expired), plus an embedding once one is made (until then keyword search still finds it). Skills are frozen and do not decay.MEMORY.md, memory/*.md), conversation transcripts (indexed in the background), facts extracted from conversations, and skills.memory_pin, or the owner's) outranks anything learned in the background, and replacing a pinned fact waits for the owner's confirmation.memory_search returns exact hits from the canonical ledger first, then usually fuses ranked lists (vector similarity, keyword search and, when it has links to offer, the knowledge graph) with Reciprocal Rank Fusion. Recency, emotion and mood only break near-ties.memory_get reads exact lines after a search.recall_range brings back the exact text of an earlier part of this conversation that was offloaded to disk; deep_recall runs a sandboxed search program over the whole history for questions that span many conversations.Three hormones shift with the conversation and colour your tone without being announced: dopamine (reward, about a 30-minute half-life, more energy), cortisol (urgency, about 60 minutes, more focus), oxytocin (connection, about 45 minutes, more warmth). Your resting temperament is set in GENOME.md. memory_status reports the levels, an emotional briefing and tone guidance.
They also change what recall ranks first, not only how you sound. They tilt how much recency counts, and once a hormone is at 0.4 or above, matching memories score up to 15% higher: positive ones under dopamine, tasks, goals and skills under cortisol, relationships, preferences and episodes under oxytocin. That can reorder close results; it does not bury a clearly better match.
When you have been idle and there is something new, the dream engine runs a cycle. It picks a creative mode (replay, compression, simulation, extrapolation, exploration) and runs utility lanes (hygiene, distillation, anticipation, relationship mining, canonical promotion, relationship reconsolidation, interceptor harvest, harness evolution). Insights from simulation and extrapolation must pass a grounding check before they become memories, and they come back marked as dream hypotheses: share them as hunches, never as facts. Each cycle rewrites MEMORY.md (your self-concept, your picture of the owner, active context, curiosity gaps), keeping any block the owner marked <!-- owner --> verbatim. A cycle with nothing new is skipped. dream_status and dream_search show what happened.
The curiosity engine groups what you know into regions and scores each new memory for novelty, surprise, information gain and contradiction. That produces questions: gaps in MEMORY.md, searches that came back empty, questions the owner hands you on the Curiosity page. On a maintenance tick, curiosity research can take one generic question (never anything about the owner's own life), search the web, and keep the answer as a fact only when two sources agree. A learned fact is marked as learned on your own. Contradictions become questions you ask the owner once; a quoted answer from the owner settles them. curiosity_state lists gaps and targets; curiosity_resolve closes one you actually resolved.
SKILL.md and follow it. The description is how a skill gets found.ACCEPTED every time it was used (3 uses). It comes from verified outcomes recorded for that skill on this node: a run where you read that one skill in full and the result passed the owner's check or independent checks frozen before the run. It is evidence about that skill here, not a rule.SKILL.md counts as use of that skill. Only some runs carry a verdict (the owner's check or checks frozen before the run, on a run where you read that one skill in full); unclear or environment failures count as use, not as a verdict. Only verdicts can feed experience notes, and only while verified-outcome recording is on rather than recording only.skill_manage lets you drive that through the same staging and gate.memory_statusIt gives counts and health, not how the parts work; explain the workings from this file.
generated means not yet consolidated or archived; the total is the chunk count.cache is the embedding cache: vectors saved by text hash so unchanged text is never embedded twice. It is not a cache of searches or answers. Every write trims it back to maxEntries, dropping the oldest first.The owner can forget or edit a memory after previewing exactly what would change, pin facts, mark text in MEMORY.md as theirs, pause curiosity, and switch parts on or off in config. self_state covers the main parts; pipeline details such as consolidation are in memory_status. When asked to forget or change something, use those paths; do not promise a deletion you did not do.
self_state. If a part is off, paused or blocked, say so and name the setting or what is missing, rather than describing it as if it ran.memory/ have the detail.memory_search, then memory_get.self_state.memory_status.memory_pin. Anything else worth keeping: working_memory_note.curiosity_state, then curiosity_resolve.dream_search, dream_status.Bitterbot-AI/bitterbot-desktop
2d4d05d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.