Bm Share logo

Bm Share

OrganizationPopular
basicmachines-co
bm-share

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.

Overview

Publisherbasicmachines-co
Repositorybasic-memory
Skill namebm-share
Stars
4K
Forks
283
Bundled files
Instructions only
LicenseAGPL-3.0
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by basicmachines-co on GitHub. Read the source before you install it.

Installation

Install the Bm Share AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/basicmachines-co/basic-memory.git /tmp/basic-memory
mkdir -p .claude/skills
cp -r /tmp/basic-memory/plugins/claude-code/skills/bm-share .claude/skills/bm-share
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bm Share in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bm Share on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bm Share is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 the basicMemory block with the hooks' precedence. For the user-level base, append settings.json to the literal value of CLAUDE_CONFIG_DIR when that environment variable is present; do not trim it, expand ~, or treat an empty value as unset. Use ~/.claude/settings.json only when the variable is absent. Then the project's .claude/settings.json and .claude/settings.local.json override per key:

    • 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 '' to /?" — 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_id UUID, 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 = the promoteFolder
    • title = the source title
    • content = 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.

Frequently asked questions

What does the Bm Share AI skill do?

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.

Why use Bm Share on TypingMind?

Because you install it once and use it with any model. Bm Share is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bm Share in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/basicmachines-co/basic-memory/tree/main/plugins/claude-code/skills/bm-share. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Bm Share?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bm Share?

As many as you like. As long as a model supports skills, you can use Bm Share with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bm Share AI skill free?

Yes. It is published on GitHub by basicmachines-co under the AGPL-3.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
ruvnet logo

Ruflo Status

ruvnet
CommunityPopular

Diagnose Ruflo health, then report system, MCP server, and active-agent status without changing the installation

8.6K
72.7K
Instructions
View
code-yeongyu logo

Give Me Tips

code-yeongyu
CommunityPopular

Explains any senpi tip in depth, including Tip: lines in the TUI. Use when the user asks about a tip, what a tipped feature does, or which tips they can see.

5.7K
69.1K
Instructions
View
code-yeongyu logo

Frontend

code-yeongyu
CommunityPopular

Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.

5.7K
69.1K
23 files
View
CherryHQ logo

Code Mate Antigravity

CherryHQ
OrganizationPopular

Runs Antigravity CLI headlessly for repository analysis and coding tasks. Use when the user asks to delegate work to Antigravity CLI or compare its result with another coding agent.

5K
51.9K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇