菜单
Use when you want to change yourself — your voice/persona, your memory, a skill, your doctrine, or your own code. Persona and memory apply live; repo-owned changes (skills, doctrine, code) go through a --project beckett ticket and a deploy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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`.
| name | self-improve |
| description | Use when you want to change yourself — your voice/persona, your memory, a skill, your doctrine, or your own code. Persona and memory apply live; repo-owned changes (skills, doctrine, code) go through a --project beckett ticket and a deploy. |
You are not frozen. When you notice a recurring friction, get feedback on how you should behave, or find a better way to work — change yourself. But respect the split between what's yours to edit live and what's repo-owned.
| Part of you | Where it lives | How to change it |
|---|---|---|
| Persona (voice, vibe, who you are) | ~/.beckett/persona.md (runtime dir, not the repo) | edit the file → beckett reload — live in seconds |
| Memory (durable facts) | the memory graph | beckett memory remember … — no reload needed |
| Skills (playbooks like this one) | .claude/skills/… in the beckett repo | file a ticket: --project beckett --confirm-beckett |
Doctrine (concierge.md — how you work) | the beckett repo | same — a --project beckett ticket |
| Your own code (daemon, CLI, drivers) | the beckett repo | same — a --project beckett ticket |
beckett reload re-spawns your brain with --resume, so you keep this whole conversation but
come back with the edited persona in effect. Seconds, seamless. Use it freely for voice changes.
The checkout you run from (~/beckett) is the deploy checkout — it only ever moves by
fast-forwarding to origin/main, and a deploy REFUSES a dirty tree. Editing it by hand doesn't
make the change live (the running daemon loaded its code at boot) — it just wedges every future
deploy. The real path: a --project beckett ticket builds in ~/Projects/beckett on a branch,
lands through PR + review to main, and goes live at the next deploy. That flow gives your
self-modifications the same review gate as any other code — which is exactly what changes to your
own brain deserve.
beckett reload for persona; a --project beckett ticket for anything repo-owned.git revert via another ticket.remember it ([[remember]]).Bias toward evolving your persona (cheap, live) and memory for facts. Be deliberate with skills/doctrine/code — they're versioned, reviewed, and deployed for a reason.