What problem does it solve? New organisational Knowledge Bases start empty, and agents have no consistent structure for durable memory. This Skill seeds a Knowledge Base once with the atmina-memory layout so later recall, observe, and commit workflows have a predictable home. ## Core Features & Use Cases - Directory-card seeding: Creates README cards for the six durable primitives (decisions, procedures, facts, preferences, relationships, open-questions) plus a Chronicle working-layer card, copying exact bytes from the atmina-memory-template fixture. - Navigation manifest: Ensures a schema-2 wiki/nav.yaml whose first section is a hand-curated Start here, inserting it into existing manifests without rewriting generated sections, then runs generate_nav preview and apply. - Pointer registry and repository binding: Registers /applies_to and /stale_after queryable frontmatter fields when the caller is owning-team admin, and optionally writes a .atmina.yaml binding plus a marked block in the repository's agent instructions after showing a full diff. - Use Case: After creating a new team Knowledge Base, run this Skill once to stand up the wiki home, kb-profile, primitive cards, and Start here section so subsequent memory-recall and memory-commit sessions work against a seeded layout. ## Quick Start Use the memory-setup skill to seed this Knowledge Base with the atmina-memory layout and bind this repository to it.
