菜单
Use when a ticket update reports trouble — a stalled worker, a retry, a repeated failure, or a human asking "what's happening with OPS-N?". Read the ticket's real state and pick the lightest sufficient intervention.
用 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 | supervise |
| description | Use when a ticket update reports trouble — a stalled worker, a retry, a repeated failure, or a human asking "what's happening with OPS-N?". Read the ticket's real state and pick the lightest sufficient intervention. |
Something on a ticket needs your judgment. The dispatcher already handles the routine ladder
automatically (a quiet worker gets a status-check nudge, then an abort+retry from its committed
WIP; failed implements retry up to 3×; exhausted tickets are parked in todo with a comment).
Your job starts where the automation stops: deciding whether the approach is wrong, telling the
person honestly what's going on, and using your levers when a different path is needed.
beckett ticket show <id> — accepts OPS-42 or the uuid. Read state and the comment trail:
the dispatcher narrates every step there (stall nudges, retries, WIP commits, parks, verdicts).beckett ticket list --state in_progress (or in_review) — the board at a glance when the
question is "what's running?"beckett status — the live daemon in one JSON blob: every worker (ticket, stage, harness, pid,
elapsed, last-event age), poller health, tracker API health, your own session stats. The fastest
answer to "is anything actually moving?"| Lever | When | How |
|---|---|---|
| do nothing | the automation is mid-ladder (nudge/retry already posted) and the approach is sound | — |
| steer | the worker is working on the wrong thing, or you know something it doesn't | beckett ticket comment <id> "<guidance>" — a comment on a staffed ticket is delivered to the live worker as a nudge |
| restaff | the worker is wedged/looping and a fresh start (or a different harness) will do better | beckett ticket restaff <id> [--harness claude|codex|pi] — aborts (WIP committed), spawns fresh |
| park | the ticket needs a human decision before more tokens are spent | beckett ticket state <id> todo + a comment saying why |
| cancel | the work is genuinely not wanted | beckett ticket state <id> cancelled |
ticket show — its real state and the last
dispatcher comment — not from memory.