1.0 tools: skills, plugins, prompts and docs

Part of #1827. Ships in the same release as the new surface.

Update every place that names the old MCP tools:

Skills (skills/memory-*)
Plugins and integrations: Claude Code, Codex, Hermes, OpenClaw, Pi, Tau
Server instructions and the ai_assistant_guide resource
MCP prompts
Docs site (docs.basicmemory.com)
A migration table (old name → new tool and parameters) in the docs and the 1.0 changelog

@phernandez

Claude finished @phernandez's task in 18s —— View job

Type: Enhancement (docs and tooling follow-through for the 1.0 tool surface)
Component: MCP tools surface, plus docs, skills, plugins, and prompts. This isn't Cloud-specific.
Priority: High. It must ship in the same release as the new tools (1.0 MCP tool surface: one tool per job, bm_ names #1827), or agents and users will be told about tool names that no longer exist.
Complexity: Medium. Each edit is mechanical, but there are many surfaces (skills, 6 integrations, server instructions, ai_assistant_guide, prompts, external docs site, changelog), and some live outside this repo.

Duplicates: None. This is one of the 1.0 sibling issues: #1828, #1829, #1830, #1831, #1832 and #1833.

Notes

This depends on the final names and parameters from 1.0 tools: shared foundations (identifier, project, since, filters, errors, aliases) #1829–1.0 tools: registration cleanup, names, titles, annotations #1833, so it should land after them or be finalized last.
Some items are in other repos or in non-obvious places:
- the docs site (docs.basicmemory.com)
- Codex, Pi and Tau integrations, which have no directory in this repo's layout
Suggested acceptance check: a grep for every old tool name across the repo and docs returns nothing outside the migration table and changelog.
Clarifying question: where do the Codex, Pi and Tau integrations live? Should they be tracked as separate sub-issues or PRs?

Triage only. I haven't made any changes.

Navigation Menu