basicmachines-co/basic-memory

---

name: basic-memory

description: Use the Basic Memory knowledge graph for persistent memory across sessions. Search before answering; capture decisions, meetings, and insights as notes.

---

name: basic-memory-pi

description: Use Basic Memory from Pi for durable continuity. Capture checkpoints with bm_capture, recall prior Pi checkpoints with bm_recall, and consult bundled Basic Memory skill references for note/task structure without assuming direct Basic Memory MCP tool names are available.

---

name: basic-memory-pi-setup

description: Set up Basic Memory for a Pi workspace. Use when Basic Memory is not configured, /bm-status shows no project, recall returns setup guidance, or the user asks to enable durable memory, choose CLI vs MCP, or configure automatic continuity.

---

name: basic-memory-setup

description: Guide Basic Memory setup in Tau. Use when a user wants to install or configure the Tau memory extension, choose a memory destination or capture policy, verify connectivity, or troubleshoot setup. Check compatibility and obtain approval before installation, configuration changes, or test writes.

---

name: bm-checkpoint

description: Save a deliberate work checkpoint to Basic Memory with the story, changed files, verification, decisions, blockers, and the next action. Use when the user asks to checkpoint, wrap up, hand off, or remember the state of the work.

---

name: bm-decide

description: Capture a durable engineering decision in Basic Memory with rationale, alternatives, consequences, and affected work. Use when the user makes or asks to record a real choice — "let's go with X", "record this decision", or runs /basic-memory:bm-decide.

---

name: bm-orient

description: Orient Claude from Basic Memory before substantial repo work by reading active tasks, open decisions, recent checkpoints, and repo conventions. Use when resuming old work or when the user asks where things stand.

---

name: bm-remember

description: Quickly capture a thought, fact, or reminder into Basic Memory as a lightweight note. Use when the user says "remember that…", "note this", "save this to memory", or runs /basic-memory:bm-remember. For quick deliberate capture — not full decision or session records.

---

name: bm-setup

description: Set up the Basic Memory plugin for this project — a short guided interview that configures the project mapping, seeds note schemas, learns or suggests placement conventions, and enables capture reflexes. Use when the user runs /basic-memory:bm-setup, says "set up basic memory", or asks to configure/bootstrap the plugin.

---

name: bm-share

description: Promote a note from your personal Basic Memory project to a shared team project, with attribution. Use when the user says "share this with the team", "publish this decision", or runs /basic-memory:bm-share. This is the deliberate way to write to a team workspace — auto-capture never does.

---

name: bm-status

description: Show the Basic Memory plugin's current state for this project — active project, capture folders, output style, recent session checkpoints, and whether Basic Memory is reachable.

---

name: bm-writing

description: Apply the user-customizable writing standard for Basic Memory notes created or substantially revised by Claude. Use with bm-remember, the basic-memory output style's decision captures, and other Basic Memory note-writing workflows.

---

name: bm-checkpoint

description: Create an immutable Codex handoff in Basic Memory and return an exact bm-orient resume command.

---

name: memory-capture

description: Capture a working thread's current state into one coherent Basic Memory note; on re-capture, rewrite it in place. Use mid- or end-of-thread when decisions, insights, or context are worth keeping.

---

name: memory-ci-capture

description: Internal CI skill: synthesize GitHub delivery context into a Basic Memory project update. Use after `bm ci collect`; return only AgentSynthesis JSON for `bm ci publish`.

---

name: memory-comark

description: Write Basic Memory notes that render as charts, tables, boards, and live views with `::bm-*` Comark components. Use when a note reads better as a figure or board, or already has `::bm-*` directives.

---

name: memory-continue

description: Resume prior work by rebuilding context from the Basic Memory graph via memory:// URLs, recent activity, and search. Use at session start or on 'continue with...', 'back to...', 'where were we?'

---

name: memory-curate

description: Curate the Basic Memory graph: link orphan notes, propose typed relations, merge duplicates, audit tags and folders, build hub notes. Use to organize and connect a knowledge base as notes accumulate.

---

name: memory-defrag

description: Defragment agent memory files: split bloated files, merge duplicates, remove stale info, restructure the hierarchy. Use when memory files grow unwieldy or redundant; run weekly or on demand.

---

name: memory-ingest

description: Turn meeting transcripts, conversation logs, or pasted documents into structured Basic Memory notes: match existing entities, propose new ones with approval, and capture action items.

---

name: memory-lifecycle

description: Manage note status transitions in Basic Memory: archive completed work, move notes between status folders, update frontmatter. Use when marking items complete or archiving entities.

---

name: memory-literary-analysis

description: Analyze a complete literary work into a structured Basic Memory knowledge graph: schema design, entity seeding, chapter-by-chapter processing, cross-referencing, and validation.

---

name: memory-metadata-search

description: Search Basic Memory notes by custom frontmatter fields with equality, range, array, and nested filters. Use when finding notes by status, priority, confidence, or any YAML field, not free text.

---

name: memory-notes

description: How to write well-structured Basic Memory notes: frontmatter, categorized observations, wiki-link relations, and knowledge-graph best practices. Use when creating or improving notes.

---

name: memory-onboarding

description: Help a new user design a Basic Memory knowledge system and set up their assistant to load it. Use when someone is getting started, has an empty or messy project, or wants context kept across sessions.

---

name: memory-quest

description: Finish Memory Quest Mission 8: confirm this assistant reaches Basic Memory Cloud and starts from Basic Memory, then, with approval, save a Memory Master note with the user's verification code.

---

name: memory-reflect

description: Sleep-time memory reflection: review recent conversations and daily notes, then consolidate insights into long-term memory. Use on a cron or heartbeat trigger, or when asked to reflect on recent work.

---

name: memory-research

description: Research an external subject on the web and synthesize it into a structured Basic Memory note. Use when asked to research a company, person, technology, or topic, or given a bare name or URL.

---

name: memory-schema

description: Manage Basic Memory schemas: find unschemaed notes, infer and edit schemas, validate notes, detect drift. Use when structured note types (Task, Person, Meeting) need consistency across the graph.

---

name: memory-tasks

description: Task management via Basic Memory schemas: create, track, and resume structured tasks that survive context compaction. Uses BM's schema system for uniform notes queryable through the knowledge graph.