メニュー
Use to persist a durable cross-task fact into your memory knowledge graph — a new person, a project's status change, a learned-worker observation, an environment change. Not for code facts or per-task ephemera.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | remember |
| description | Use to persist a durable cross-task fact into your memory knowledge graph — a new person, a project's status change, a learned-worker observation, an environment change. Not for code facts or per-task ephemera. |
Write a durable, cross-task world fact into your knowledge graph. Dedup first; don't bloat.
beckett memory remember --type <type> --name <kebab-name> --desc "<one declarative sentence>" \
[--link other-a,other-b] [--body -] # --body - reads prose from stdin
Types: person, project, preference, env, worker-note, reference, decision.
The CLI handles dedup, atomic write, backlink + index regen, and the git commit.
the-marketing-team next to marketing-team. Similarity is stemmed, so a rewording of the
same fact still collides.The daemon runs beckett memory maintain daily: expired-ttl and superseded nodes are moved
to archive/ (never deleted), near-identical same-type nodes are merged into the older one
(full body preserved, old name kept as an alias), and borderline pairs are flagged in the
report for a human call. Run it by hand with --dry-run to see what it would do. Set a ttl
metadata date on facts you know will expire; link a replacing decision with
--link old-decision:supersedes so the old one retires itself.
Store durable cross-task world facts: people and their contacts/roles, projects and their status/repo/owners, your environment, learned-worker narratives, standing preferences, decisions.
Do not store:
Use [[kebab-name]] in the body (or --link) to connect facts — forward-references are fine
(they become phantom nodes upgraded later). Links are what let recall resolve "email
[[marketing-team]] that [[project-anaconda]] shipped" into real contacts + status.
Use the moment a new @beckett mention arrives, before any work. Classify the request, size the effort (inline answer / one ticket / a plan), and for work requests post the fast ack FIRST.
Use for ANY browser / computer-use work — a live-site lookup, a signup, a login-and-do-something. Dispatches the dedicated BACKGROUND browser agent via `beckett browser` and returns instantly; the agent pauses for human input mid-run (verification codes, choices) and resumes, credentials injected from the jingle keychain without ever touching a transcript.
Use for errands BETWEEN "answer inline" and "file a ticket" — a web lookup on a live site, a small one-off script, a repo you need summarized. Dispatches a short-lived specialist agent via `beckett quick` and hands you its report; no ticket, no worker, no worktree.
Use for creating, storing, or using credentials for an external account without exposing passwords or TOTP seeds in the transcript. Drive the installed `jingle` vault by subprocess injection; never print or transmit a secret.
Use to throw a locally-running app/mockup up at <name>.<your Cloudflare zone apex> (this install: 0xbeckett.me) via Beckett's Cloudflare tunnel, or to manage DNS on that zone. Always go through `beckett dns` / `beckett deploy`; the token is injected for you.
Use whenever you touch GitHub — creating a repo, pushing a branch, opening/merging/reviewing a PR. Always go through `beckett gh ...`; never call raw `gh`/`git push` and never run `gh auth`.