memory-observe

Writes working-layer notes and session notes to an Atmina Knowledge Base chronicle.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/latentminds-ai/atmina-plugins --skill memory-observe-latentminds-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-observe
Source: https://github.com/latentminds-ai/atmina-plugins/tree/main/plugins/atmina-codex/.agents/skills/memory-observe
Command: npx skills add https://github.com/latentminds-ai/atmina-plugins --skill memory-observe-latentminds-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agents lose working context between sessions and often dump mid-task findings, briefs, or transcripts into durable wiki pages where they get mistaken for organisational truth. This Skill keeps candidate notes in a separate working layer so durable memory stays clean. ## Core Features & Use Cases - Working-layer writes only: Appends mid-task candidate notes to dated files under chronicle/ (org scope) or journal/ (personal scope), never touching wiki/, _consolidated/, _sources/, or _staged/. - Session notes on consent: At task end, offers a compact session note (task, gathered sources, decisions, locators) and writes it only after the user says yes; an empty session is a successful no-op. - Safe write recipe: Uses list_files to confirm paths, write_file with create/append modes, and overwrite with if_match sha256 conflict handling for compacting notes. - Use Case: During a renewal-preparation task, an agent appends candidate findings to chronicle/2026-08-27-renewal-task.md, then at task end compacts them into a single index-style session note referencing the wiki paths and CRM records it read. ## Quick Start Ask the agent to record today's working notes and end-of-task session note in the Atmina Knowledge Base working layer using the memory-observe skill.

Frequently Asked Questions about memory-observe

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

FAQPage Schema
How do I write working notes to an Atmina Knowledge Base?

Use list_files with the chronicle/ or journal/ prefix to confirm the dated path, then call write_file in create mode for a new note or append mode for mid-task candidates. At task end, compact the file into a session note using overwrite with an if_match sha256.

What is the difference between chronicle and wiki paths in Atmina?

Chronicle (or journal at personal scope) is the working layer for candidate notes and session indexes, while wiki/ holds durable organisational truth. This skill never writes wiki/, _consolidated/, _sources/, or _staged/ paths.

Does memory-observe write a session note automatically at task end?

No. The skill offers the session note first and writes only after the user says yes. Mid-task candidate appends need no offer, and if nothing notable happened the correct outcome is a no-op with no file created.

What happens on a write conflict when overwriting a session note?

A conflict response means another writer changed the file between read and write. Re-read the file, re-compose the compact note against the new content, and retry overwrite with the fresh sha256 in if_match; never retry the same bytes.

When should gathering sources not become a durable memory write?

Selecting sources or finishing a gather is at most a working-layer Observe note, never a Commit. Typed evidence blocks are stripped from working-layer notes, and the note path serves only as provenance for a later durable write.