@basicmemory/openclaw-basic-memory 0.24.0 → 1.0.0

package/skills/memory-ingest/SKILL.md

@@ -7,6 +7,17 @@ description: "Turn meeting transcripts, conversation logs, or pasted documents i
 
 Turn raw, unstructured input into structured Basic Memory entities. Meeting transcripts, conversation logs, pasted documents, email threads — anything with information worth preserving gets parsed, cross-referenced against existing knowledge, and written as proper notes.
 
+## Project scope
+
+If the project is unknown, discover it with `bm_project(command="list")`.
+Pass a nonempty `project` on every note, folder, context and schema call, even
+with one project or a qualified `memory://` URL. Use the chosen project's name,
+`workspace/project`, or external ID; `<project>` below is a placeholder for it.
+Recent activity also requires `project`. Search accepts `project` for one
+project, `projects` for selected projects, or `all_projects=True` explicitly.
+Discovery and bundled manuals need no project. Keep the same scope when following
+returned paths, paginating, or recovering from a refusal.
+
 ## When to Use
 
 - User pastes a meeting transcript or conversation log
@@ -70,16 +81,16 @@ For each extracted entity, search Basic Memory with multiple query variations:
 
 ```python
 # Person — try full name, last name
-search_notes(query="Sarah Chen")
-search_notes(query="Chen")
+bm_search(query="Sarah Chen", project="<project>")
+bm_search(query="Chen", project="<project>")
 
 # Organization — try full name, abbreviation, acronym
-search_notes(query="National Renewable Energy Laboratory")
-search_notes(query="NREL")
+bm_search(query="National Renewable Energy Laboratory", project="<project>")
+bm_search(query="NREL", project="<project>")
 
 # Topic — try the full term and keywords
-search_notes(query="edge computing")
-search_notes(query="edge inference")
+bm_search(query="edge computing", project="<project>")
+bm_search(query="edge inference", project="<project>")
 ```
 
 Classify each entity as:
@@ -124,7 +135,7 @@ Create the primary note for the ingested content. This is the "record of what ha
 ### Meeting / Conversation Note
 
 ```python
-write_note(
+bm_write(
   title="NovaTech Meeting - Jordan Rivera - Feb 22, 2026",
   directory="meetings/2026",
   note_type="meeting",
@@ -150,14 +161,15 @@ Brief one-sentence summary of what this meeting was about.
 - with [[NovaTech]]
 - discussed [[Federated Learning]]
 - follow_up [[Send NovaTech Technical Spec]]
-"""
+""",
+  project="<project>",
 )
 ```
 
 ### Document / Article Note
 
 ```python
-write_note(
+bm_write(
   title="Edge Computing Architecture Whitepaper",
   directory="references",
   note_type="reference",
@@ -177,7 +189,8 @@ write_note(
 ## Relations
 - relates_to [[Edge Computing]]
 - relates_to [[Model Optimization]]
-"""
+""",
+  project="<project>",
 )
 ```
 
@@ -204,13 +217,13 @@ Invent categories as needed — these are suggestions, not a fixed list.
 
 For each entity the user approved, create a structured note. Match the entity type to an appropriate template.
 
-If `write_note` reports similar existing notes, treat that as a match Step 3 missed: merge into
+If `bm_write` reports similar existing notes, treat that as a match Step 3 missed: merge into
 the existing note and delete the new one, or link the two.
 
 ### Person
 
 ```python
-write_note(
+bm_write(
   title="Jordan Rivera",
   directory="people",
   note_type="person",
@@ -232,14 +245,15 @@ VP of Engineering at NovaTech. Met during integration partnership discussion.
 ## Relations
 - works_at [[NovaTech]]
 - discussed_in [[NovaTech Meeting - Jordan Rivera - Feb 22, 2026]]
-"""
+""",
+  project="<project>",
 )
 ```
 
 ### Organization
 
 ```python
-write_note(
+bm_write(
   title="NovaTech",
   directory="organizations",
   note_type="organization",
@@ -262,14 +276,15 @@ SaaS platform company. Series B stage.
 ## Relations
 - employs [[Jordan Rivera]]
 - discussed_in [[NovaTech Meeting - Jordan Rivera - Feb 22, 2026]]
-"""
+""",
+  project="<project>",
 )
 ```
 
 ### Concept / Topic
 
 ```python
-write_note(
+bm_write(
   title="Federated Learning",
   directory="concepts",
   note_type="concept",
@@ -286,7 +301,8 @@ write_note(
 
 ## Relations
 - discussed_in [[NovaTech Meeting - Jordan Rivera - Feb 22, 2026]]
-"""
+""",
+  project="<project>",
 )
 ```
 

package/skills/memory-lifecycle/SKILL.md

@@ -7,6 +7,17 @@ description: "Manage note status transitions in Basic Memory: archive completed
 
 Manage how entities move through status stages in Basic Memory. The core principle: **archive, never delete.** Completed work is valuable context — move it out of the active view, but keep it in the knowledge graph.
 
+## Project scope
+
+If the project is unknown, discover it with `bm_project(command="list")`.
+Pass a nonempty `project` on every note, folder, context and schema call, even
+with one project or a qualified `memory://` URL. Use the chosen project's name,
+`workspace/project`, or external ID; `<project>` below is a placeholder for it.
+Recent activity also requires `project`. Search accepts `project` for one
+project, `projects` for selected projects, or `all_projects=True` explicitly.
+Discovery and bundled manuals need no project. Keep the same scope when following
+returned paths, paginating, or recovering from a refusal.
+
 ## When to Use
 
 - User says something is "done", "finished", "completed", "submitted", "missed", or "cancelled"
@@ -20,10 +31,10 @@ Deleting a note removes it from the knowledge graph — its observations and rel
 
 ```
 # Good — entity stays in the knowledge graph
-move_note → active/ to archive/
+bm_move → active/ to archive/
 
 # Bad — knowledge is lost
-delete_note
+bm_delete
 ```
 
 The only exception: notes created by mistake (typos, true duplicates) can be deleted.
@@ -77,8 +88,8 @@ When the user mentions completion or status change, extract the intent:
 Search Basic Memory with multiple variations to locate the entity:
 
 ```python
-search_notes(query="quarterly report")
-search_notes(query="Q1 report")
+bm_search(query="quarterly report", project="<project>")
+bm_search(query="Q1 report", project="<project>")
 ```
 
 If multiple matches come back, present options and ask which one.
@@ -87,12 +98,13 @@ If no match is found, ask for clarification — don't guess.
 
 ### 2. Move the File
 
-Use `move_note` to relocate the entity to the appropriate status folder:
+Use `bm_move` to relocate the entity to the appropriate status folder:
 
 ```python
-move_note(
+bm_move(
   identifier="tasks/active/quarterly-report",
-  destination_path="tasks/completed/quarterly-report.md"
+  destination="tasks/completed/quarterly-report.md",
+  project="<project>",
 )
 ```
 
@@ -101,15 +113,15 @@ By default the permalink stays the same after a move, so links keep resolving. P
 ### 3. Update Frontmatter
 
 After moving, merge the new status (and completion date, if the type tracks one) into
-frontmatter with the `metadata` parameter. An `append` with empty `content` changes only
-the frontmatter:
+frontmatter with `command="set_metadata"` and the `metadata` parameter; this leaves
+the body unchanged:
 
 ```python
-edit_note(
-  identifier="quarterly-report",
-  operation="append",
-  content="",
-  metadata={"status": "completed", "completed": "2026-02-22"}
+bm_edit(
+  identifier="tasks/completed/quarterly-report.md",
+  command="set_metadata",
+  metadata={"status": "completed", "completed": "2026-02-22"},
+  project="<project>",
 )
 ```
 
@@ -149,16 +161,17 @@ status is unchanged. Only the user can unlock it, by editing the file.
 If something was archived by mistake, move it back:
 
 ```python
-move_note(
+bm_move(
   identifier="tasks/completed/quarterly-report",
-  destination_path="tasks/active/quarterly-report.md"
+  destination="tasks/active/quarterly-report.md",
+  project="<project>",
 )
 
-edit_note(
-  identifier="quarterly-report",
-  operation="append",
-  content="",
-  metadata={"status": "active"}
+bm_edit(
+  identifier="tasks/active/quarterly-report.md",
+  command="set_metadata",
+  metadata={"status": "active"},
+  project="<project>",
 )
 ```
 
@@ -176,7 +189,7 @@ Some status changes don't require a folder move — "paused" or "blocked" items
 
 - **Archive, never delete.** The knowledge graph benefits from historical context.
 - **Move first, then update frontmatter.** This order ensures the file is in the right place even if the edit step fails.
-- **Permalinks survive moves by default.** Links to the entity keep working after a `move_note` unless the project enables `update_permalinks_on_move`.
+- **Permalinks survive moves by default.** Links to the entity keep working after a `bm_move` unless the project enables `update_permalinks_on_move`.
 - **Be concise in confirmations.** The user knows their system — just report what changed.
 - **Ask when ambiguous.** If multiple entities match or the target folder isn't clear, ask rather than guess.
 - **Batch operations are fine.** If the user says "archive all completed tasks", find them all, confirm the list, then move them in sequence.