メニュー
Use whenever you need to GENERATE or EDIT a raster image — a mockup graphic, logo, sprite, icon, illustration, banner, product shot, or any "make me a picture of…" request. Always use `beckett image`; never scaffold an image project or call codex/python/SVG yourself.
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 | image |
| description | Use whenever you need to GENERATE or EDIT a raster image — a mockup graphic, logo, sprite, icon, illustration, banner, product shot, or any "make me a picture of…" request. Always use `beckett image`; never scaffold an image project or call codex/python/SVG yourself. |
You can make images. There is one way to do it: the beckett image command. It wraps the
Codex image_gen tool (authed and enabled for you) into a single deterministic call that saves
a real file to an exact path and hands you back that path.
Never improvise image generation. Do NOT create a project (you once made ~/projects/imagegen
instead of just generating), do NOT call codex directly, do NOT reach for python/PIL/SVG/HTML/CSS
to fake a raster image. If the user wants a photo, logo, sprite, icon, illustration, banner, or
product image → beckett image. (If they want a vector/UI asset that should match existing
repo SVGs, edit those directly instead — that's the one case where image gen is the wrong tool.)
beckett image "<description>" [--out <path>] [--size <s>] [--ref <file[,file]>] [--transparent] [--model <m>]
| Flag | Meaning |
|---|---|
| (positional) | The image description. Be concrete: subject, style, colors, composition. |
--out <path> | Where to save. Default: ~/.beckett/images/<ts>-<slug>.png. |
--size <s> | 1024x1024 (default), 1536x1024 (landscape), 1024x1536 (portrait), or auto. |
--ref <file[,file]> | Reference image(s) to edit / build on (comma-separated). Turns it into an edit. |
--transparent | Produce a real transparent (alpha) PNG. |
--model <m> | Optional Codex driver model override (rarely needed). |
Returns JSON: { path, bytes, size, prompt, edited, relocated }. path is the absolute file —
that's what you hand off or deploy. (relocated:true just means the wrapper moved the file from
Codex's default dir to your --out; nothing to act on.)
The quality is in the prompt. Give it: the subject, the style ("flat vector", "photoreal", "pixel-art sprite", "3D render"), palette, background, and any text verbatim in quotes. One clear paragraph beats a vague line. Example:
beckett image "flat-design app icon: a friendly robot mascot head, rounded squircle, mint-green
background, soft drop shadow, no text" --size 1024x1024 --transparent --out ~/.beckett/images/beckett-icon.png
beckett image "…" --out <path>. Grab path from the JSON.beckett discord reply --channel <id> --file <path> "here's the mockup"
(the reply command takes --file; see your tool map). Don't just describe it — send it.beckett deploy a page that references it, or host it (see [[deploy]]).--ref <path> and a tweak
("same but warmer palette and a darker background").This is exactly the muscle for the proactive move (see [[proactive]]) — "saw yall debating the logo, threw a few options together" — and for delivering visual work ([[deliver]]).
--ref path is wrong; check it.