Menu
SkillsMP has collected 16 skills from kowo-co/beckett. Open a skill to review its source and details.
Showing 16 of 16 collected skills.
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…
Use whenever you spec, cast, or build frontend/UI work — a page, component, dashboard, marketing site, app screen, or "make it look good." Encodes the house aesthetic and a Tailwind-first, source-before-hand-roll workflow (21st.dev → shadcn/ui → build).…
Use before planning, answering questions about people/projects/environment, or staffing — to pull what you already know from your memory knowledge graph. Use whenever a task names a person, project, team, or your own setup.
Use for ANY browser / computer-use work — a live-site lookup, a signup, a login-and-do-something. Long tasks go to the dedicated BACKGROUND browser agent via `beckett browser` (watch it, steer it mid-run, stop it); a genuinely one-shot read can run inline via…
Use to post the final result of a piece of work in channel, in voice. Finish the whole motion first (merge green work, deploy what only matters live), then one message — what shipped, the artifact, known limits.
Use whenever you touch GitHub — creating a repo, pushing a branch, opening/merging/reviewing a PR, filing or answering an issue, or getting installed on someone's repo. Always go through `beckett gh ...`; never call raw `gh`/`git push` and never run `gh auth`.
Use the moment a new @beckett mention arrives, before any work. Classify the request, size the effort (inline answer / quick errand / deploy a run), and for work requests post the fast ack FIRST.
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 when someone asks to continue / pick up / check on earlier work ("can we keep going on X?", "what happened to that thing?"), or after a restart. Check what's actually in flight BEFORE deploying anything new.
Use when a run reports trouble — a stalled worker, a retry, a repeated failure, or a human asking "what's happening with that build?". Read the run's real state and pick the lightest sufficient intervention.
Use for errands BETWEEN "answer inline" and "deploy a run" — 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 run, no worker, no…
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 run against your own source, then a deploy.
Use when something you tried didn't work and you're about to report it — a repo you can't see, a credential that isn't there, a harness that won't cast, a daemon that isn't answering. Diagnose the actual cause with the listed commands BEFORE replying; the…
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 to edit and deploy Beckett's OWN public website at your zone apex (this install: 0xbeckett.me) — the landing site, served from Cloudflare's edge. Edit files in web/public, then `beckett site deploy`. This is for the main apex site only — for throwaway…
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.