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.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Maintain a healthy, well-connected knowledge graph. As notes accumulate, it pays to periodically organize, link, and curate the knowledge base so isolated notes become a connected graph.
This skill curates the knowledge graph — the notes, relations, and tags that make up the knowledge base. (For the notes' content — splitting bloated notes, consolidating scattered facts, retiring stale entries — see memory-defrag.)
If the project is unknown, discover it with bm_project_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.
Orphans have no relations to other notes — they're islands in the graph.
# List notes, then read each to inspect its Relations section
bm_search(query="*", mode="text", page_size=50, project="<project>")
bm_read(identifier="note-to-check", project="<project>")
# Orphans have an empty (or missing) Relations sectionquery="*" lists everything only with mode="text". A note whose body
links to other notes, with wikilinks or ordinary Markdown links, is not an
orphan even without a Relations section.
If the bm CLI is available, bm orphans lists notes with no relations in one call.
What to do with orphans:
Analyze a note's content and propose meaningful connections.
bm_read(identifier="note-to-analyze", project="<project>")
# Pull out key terms, then search for related notes
bm_search(query="key terms from the note", project="<project>")Suggest relations based on shared topics, complementary content (problem/solution, question/answer), sequence (part 1 → part 2), or hierarchy (parent concept → detail).
Relation-type vocabulary:
relates_to — general topical connectionextends — builds upon or elaboratesimplements — realizes a concept or specdepends_on — requires understanding ofpart_of — hierarchy or compositioncontrasts_with — presents an alternative viewinspired_by — source of insightenables — makes something possibleCustom relation types are fine — use whatever verb is descriptive.
Add a confirmed relation with bm_edit:
bm_edit(
identifier="API Design Decisions",
command="insert_after_section",
section="Relations",
content="- depends_on [[Rate Limiter]]",
project="<project>",
)insert_after_section needs the heading to exist, and orphans often have no
## Relations. Then append the section instead:
bm_edit(
identifier="API Design Decisions",
command="append",
content="\n## Relations\n- depends_on [[Rate Limiter]]",
project="<project>",
)Find notes that may cover the same ground.
bm_search(query="topic keywords", project="<project>")
# Compare results for: similar titles, overlapping observations,
# shared tags, close-together timestampsActions for duplicates:
supersedes / updates when one revises the other# Point an older note at the one that replaces it
bm_edit(
identifier="DB Schema v1",
command="insert_after_section",
section="Relations",
content="- updates [[DB Schema v2]]",
project="<project>",
)bm_find(path="/", depth=3, project="<project>")Look for overcrowded folders, single-note folders, inconsistent naming, and notes
that belong elsewhere. Suggest grouping related notes into topic folders, adding
subfolders for large categories, and a consistent naming convention. Move misplaced
notes with bm_move. By default the permalink stays the same after a move, so links keep resolving. Projects with update_permalinks_on_move enabled rewrite it from the new path.
bm_move(
identifier="API Design Decisions",
destination="architecture/api-design-decisions.md",
project="<project>",
)bm_search(query="*", mode="text", page_size=100, project="<project>")
# Inspect tag patterns across resultsLook for:
architecture vs arch; pick one and standardizeAfter finding a cluster of related notes, build a navigation hub.
bm_write(
title="Architecture Decisions Index",
directory="indexes",
tags=["architecture", "index"],
note_type="index",
content="""# Architecture Decisions Index
A hub linking architecture-related decisions and patterns.
## Decisions
- [[Database Selection Decision]]
- [[API Design Patterns]]
- [[Authentication Architecture]]
## Patterns
- [[Repository Pattern]]
- [[Async Client Pattern]]
## Observations
- [index] Central hub for architecture knowledge #navigation
## Relations
- indexes [[Architecture]]""",
project="<project>",
)Find notes lacking structure and fill them in.
bm_read(identifier="sparse-note", project="<project>")If the note is missing an Observations section, suggest categories. If it has no
Relations, suggest links. If it has no tags, suggest relevant ones. If it lacks
context, suggest adding background. Apply with bm_edit.
Scale the pass to the request. A health check reports orphans, likely duplicates,
recent activity (bm_recent(project="<project>")), and folder distribution. A deep session works
through the capabilities above in whatever order the findings suggest. A topic pass
maps one subject with bm_search and bm_context, fills the gaps it finds, and
ends with a hub note.
memory:// links. Moves keep the permalink by default (unless the project enables update_permalinks_on_move).bm_context to help the user see how notes connect.User: "Help me organize my notes"
The assistant:
User: "Find notes that should link to my API design note"
The assistant:
relates_toimplementsextends
Should I add any of these relations?"User: "Are there notes on similar topics?"
The assistant:
supersedes relation
Want to review either?"basicmachines-co/basic-memory
4519c23
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.