Deliberately search, add to, or curate your long-term memory with the `memory` tool — beyond the automatic recall/capture every turn already does. Use when asked who someone is or what they're working on, when you learn a durable fact worth keeping now, or when your notebook holds stale or wrong entries you should clean up.
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Critical
Do not install without reviewing
Everything here goes through the typed memory tool. Memory is NOT a file: writing
memory/MEMORY.md with files action write or shell commands lands on your computer's disk and is
silently lost — the tool is the one real path.
Every turn already auto-recalls a bounded selection from your notebooks into "## What you remember" and auto-extracts facts after you reply. This skill is for what the automatic path misses:
action: "search") — what you remember is bigger than what auto-recall
injects. Search spans every notebook this conversation may read (personal, channel,
org); when more than one is in reach, each hit is tagged with the notebook it came
from. Matching is substring-based (all terms must match), so prefer distinctive terms
(a name, a project) over sentences.
An empty result means those terms found no match, not that nothing is recorded. Try fewer terms or alternate wording before concluding a fact is absent.action: "read", scope: "channel:…") — use the exact
scope ID from a search result to load that authorized notebook. search accepts
scope too, to narrow a query. Omit it to search all authorized notebooks or read
the current notebook. Access comes from this turn's sharing policy; naming a
scope never grants access. Other notebooks are read-only.action: "add", facts: [{text}, …]) — when the user corrects you or tells you
something they'll expect you to know later, persist it immediately instead of hoping
post-turn extraction catches it. Write self-contained facts (who/what, with enough
context to be useful cold). Duplicates are dropped; added in the reply is the count
actually new.action: "edit" with facts: [{id, text}, …], action: "delete" with
ids) — search or read to get each fact's #id, then fix facts that changed and delete
stale, duplicate, or wrong ones. A call naming any id that isn't in this conversation's
notebook changes nothing and lists the bad ids. Curation is for quality — merging
duplicates, deleting disproven facts — not for deleting things the user asked you to
remember.The notebook you write is this conversation's own (your personal one in a DM, the channel's in a channel). Other authorized notebooks can be searched/read, not rewritten here.
The org-admin write path uses the self-API instead, called with
$AGENT_API_URL and $AGENT_API_TOKEN (both already in your environment on every turn —
if they are unset, this instance has no self-API; say so rather than pretending).
When the chatting user is an org admin, the self-API additionally accepts the org-wide notebook as a target:
curl -sS --fail-with-body -X POST "$AGENT_API_URL/v1/memory/facts" \
-H "x-agent-capability: $AGENT_API_TOKEN" \
-H "content-type: application/json" \
-d '{"scope":"org","facts":["..."]}'(?scope=org on GET /v1/memory/self; "scope":"org" in the body of PATCH /v1/memory/facts
with {"facts":[{"id","text"}]} or DELETE /v1/memory/facts with {"ids":[…]} to curate.)
Those writes land in the notebook every conversation in the org recalls, so confirm the
wording with the admin before writing and keep personal facts out of it. A 403 org memory writes require an org admin means the user isn't one — say so rather than
retrying (GET $AGENT_API_URL/v1/admin/whoami answers it definitively).
A member who runs their own gbrain can make it their personal memory, on a turn they sent (triggered turns are refused). Call the self-API as them:
GET $AGENT_API_URL/v1/memory/brain returns what they have connected and principalId,
the id their gbrain must link to their gbrain member. On their gbrain they also need a
confidential client-credentials client that may attest an actor.PUT $AGENT_API_URL/v1/memory/brain with {"url":"https://…/mcp","clientId":"…"}
(optionally label). The URL must be public https://. Never ask for or
send the client secret: clientSecret is refused here.brain.id (see the secret-drop skill). The form
shows them where their memory goes before they submit.disabled in the reply says why it isn't serving: secret_missing until they use the link,
member_brains_off when an org admin has turned members' brains off.Once it serves, recall and explicit writes for their personal memory also go to that brain,
attested as them, and their notebook keeps working. DELETE disconnects it.
401 unauthorized from the self-API — your token expired mid-turn; this resolves on
the next turn.502 with an application/problem+json body from /v1/memory/facts or
/v1/memory/search — a memory provider failed. added (or results) is what still
worked, and each entry in problems names the provider, what happened and a fix.
Don't send the same facts again; tell the user which provider failed and its fix.yc-software/qm
c94f65b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.