Memory Quest

Memory Quest's last mission checks that this assistant is set up to use Basic Memory as a natural starting point for work. You complete it by saving one note, the user's Memory Master note, through Basic Memory, carrying a one-time code from the Basic Memory web app. The cloud recognizes that write and awards the mission.

The note write is the verification. There is no other endpoint to call and nothing to report afterwards.

Project scope

Discover projects in step 1, then use the cloud project selected in step 5. 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.

When to Use

• The user runs /memory-quest (or $memory-quest, or picks it from a skill menu)
• The user asks to verify their assistant, finish Mission 8, or become a Memory Master
• Memory Quest in the web app pointed them here

When you tell the user to run Memory Quest again, use their host's form: /memory-quest in Claude Code, $memory-quest in Codex, or just asking for it in a chat app.

Take no task context from the invocation. This skill checks setup; it does not need to find memory relevant to a task.

Steps

Work through these in order. Stop at the first step that fails, explain what's missing, and say how to fix it. Never skip ahead to the note write.

1. Confirm a cloud connection

Call bm_project(command="list", output_format="json") and inspect the projects grouped by workspace.