Bm Orient

OrganizationPopular

basicmachines-co

bm-orient

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.

Overview

Publisher	basicmachines-co
Repository	`basic-memory`
Skill name	`bm-orient`
Stars	4K
Forks	283
Bundled files	Instructions only
License	AGPL-3.0
Links	Skill source Repository Homepage

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 Orient AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/basicmachines-co/basic-memory/tree/main/plugins/claude-code/skills/bm-orient

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

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-orient .claude/skills/bm-orient

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bm Orient 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 Orient 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 Orient 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.

Orient From Basic Memory

Use this before substantial work in a repo, before resuming an old thread, or when the user asks where things stand. The SessionStart hook already briefs the start of a session; this is the deliberate mid-session version with deeper reads.

Steps

Resolve config: read the basicMemory block with the same precedence the hooks use. 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 it per key. Use primaryProject, secondaryProjects, recallTimeframe, sessionProfile, repository, and placementConventions. If no config is present, continue against the default Basic Memory project and mention that setup has not been run. Scope queries to primaryProject by passing it as project, or as project_id if it's an external_id UUID.
Query the primary project with search_notes:
- active tasks: metadata_filters={"type": "task", "status": "active"}
- open decisions: metadata_filters={"type": "decision", "status": "open"}
- recent sessions: metadata_filters={"type": "session"}, after recallTimeframe
- recent coding sessions: metadata_filters={"type": "coding_session", "repository": "<configured repository>"}, after recallTimeframe, when sessionProfile is coding
Always query "type": "session"; include "type": "coding_session" for a coding profile only with the configured repository metadata filter. Never run an unscoped coding-session query; if the repository is missing, report that setup is incomplete. Merge and deduplicate the results, sort them newest first, and prefer the highest-signal checkpoint regardless of which producer wrote it. coding_session carries schema-required, queryable Git context; session covers general checkpoints and PreCompact captures. Do not query lifecycle trace: bm hook flush archives it locally rather than promoting it into the graph.
Query configured secondaryProjects read-only for open decisions. Do not write to shared projects during orientation.
Read the highest-signal hits before summarizing. Prefer notes that match the current repository, branch, Git SHA, pull request, named route, issue, or file path. For coding sessions, use structured metadata filters before text search.
Present a compact orientation:
- active work
- decisions that constrain the next move
- recent checkpoint cursor
- likely next action
- any missing setup or ambiguous project mapping

Keep the summary evidence-backed. Include permalinks for notes you rely on.

Frequently asked questions

What does the Bm Orient AI skill do?

Why use Bm Orient on TypingMind?

Because you install it once and use it with any model. Bm Orient 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 Orient 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-orient. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Bm Orient?

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 Orient?

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

Is the Bm Orient 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.

View all

Finishing A Development Branch

obra

CommunityPopular

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Receiving Code Review

obra

CommunityPopular

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative…

Requesting Code Review

obra

CommunityPopular

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Systematic Debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Orient From Basic Memory

Steps

Frequently asked questions

Related AI Skills

Set up your own AI workspace now