Bm Share
- 127 installs
- 3.6k repo stars
- Updated August 5, 2026
- basicmachines-co/basic-memory
bm-share is a Claude skill that promotes a note from your personal Basic Memory project to a shared team project with attribution.
About
This skill copies a note from your personal Basic Memory project into a configured shared team project with attribution. A developer uses it to publish a decision or note to teammates when they say share this with the team. It is the only path that writes to a team workspace, keeps frontmatter, adds a shared_from field, and asks for confirmation before the visible write.
- Promotes a note from your personal Basic Memory project to a shared team project
- Adds attribution (shared_from frontmatter + a context observation) and confirms before writing
- The only path by which the plugin writes to a team workspace; auto-capture never does
Bm Share by the numbers
- 127 all-time installs (skills.sh)
- Ranked #1,259 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
bm-share capabilities & compatibility
- Capabilities
- bm remember · bm setup · bm status
- Use cases
- memory · documentation
- Runs
- Runs locally
- Pricing
- Free
What bm-share says it does
Promote a note from your personal Basic Memory project to a shared team project, with attribution.
This is the *only* path by which the plugin writes to a shared project
This write is visible to teammates, so show the user what you're about to do
npx skills add https://github.com/basicmachines-co/basic-memory --skill bm-shareAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 127 |
|---|---|
| repo stars | ★ 3.6k |
| Last updated | August 5, 2026 |
| Repository | basicmachines-co/basic-memory ↗ |
What it does
Publish a personal Basic Memory note to a configured shared team project with attribution and a confirmation gate.
Who is it for?
developers publishing a decision or note from their personal project to a team workspace
Skip if: notes containing secrets or credentials, or teams with no configured share target
When should I use this skill?
when the user says share this with the team, publish this decision, or runs bm-share
What you get
an attributed copy of the note in the team project with a shared_from link back to the source
- an attributed shared copy of the note in the team project
By the numbers
- 6-step share procedure
- default promoteFolder is shared
Files
Share to a team project
Copy a note from the personal/primary project into a configured team project so teammates can see it. This is the only path by which the plugin writes to a shared project — session checkpoints and /basic-memory:bm-remember always stay personal.
Steps
1. Resolve config. Read .claude/settings.json (+ .local) basicMemory:
teamProjects— a map of<project-ref>→{ "promoteFolder": "shared" }.
These are the allowed share targets. <project-ref> is a workspace-qualified name (e.g. my-team-2/notes) or an external_id UUID.
primaryProject— the source project notes are read from.
If teamProjects is empty, tell the user there's no share target configured and suggest adding one (or running /basic-memory:bm-setup), then stop. Don't invent a target.
2. Find the source note. From $ARGUMENTS (a title, permalink, or memory:// URL), read_note it from primaryProject. If $ARGUMENTS is empty (you were invoked from "share this"), use the note most clearly referenced in the conversation — confirm which one if there's any ambiguity. Capture its title, full content (including frontmatter), and source permalink.
3. Pick the target. If teamProjects has one entry, use it. If several, ask which team project to share to. Use that entry's promoteFolder (default shared).
4. Confirm before writing. This write is visible to teammates, so show the user what you're about to do — "Share '<title>' to <target>/<promoteFolder>?" — and wait for a yes. Never share silently.
5. Write the shared copy with write_note:
- Route to the target: if the team ref is an
external_idUUID, pass it as
project_id; otherwise pass the workspace-qualified name as project. (A bare UUID in project won't route — Basic Memory takes UUIDs only via project_id.)
directory= thepromoteFoldertitle= the source titlecontent= the source's content, with attribution added: keep its frontmatter
(so a shared decision stays type: decision and is findable in the team's structured recall), add a shared_from: <source permalink> frontmatter field, and add an observation - [context] Shared from <source permalink>. Don't overwrite an existing note at the target unless the user says so.
6. Confirm in one line: what was shared and the new team permalink, e.g. Shared → my-team-2/shared/<slug>.
Notes
- Sharing copies the note; the original stays in your project. Edits to one
don't propagate to the other.
- Don't share notes containing secrets, credentials, or anything the user wouldn't
want teammates to see — if in doubt, ask.
- Use whichever Basic Memory MCP server is connected; route to the team project by
the project (qualified name) or project_id (UUID) argument.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
Does sharing move the note?
No, sharing copies the note; the original stays in your project and edits to one do not propagate to the other.
Will bm-share write silently?
No, because the write is visible to teammates it shows what it will do and waits for a yes before writing.