Creates a Beads issue for a requested piece of work, completes exactly that work, and closes the issue. Use when the user invokes `/bx` or `$bx`, or asks for a bead to be created and the described work done in the same go. For creating a bead without doing the work, use the `bc` skill instead.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
The user's request text is the sole authority for implementation scope. Do not broaden it when writing or updating the bead.
An audit, investigation, review, plan, recommendation, or proposal is complete when its requested artifact or findings are delivered. Do NOT implement, apply, or act on findings, recommendations, or proposed changes unless the request explicitly asks for that too.
Do NOT explore the codebase, launch subagents, or do any other work before creating the bead issue.
beads-best-practices skill and follow it when writing any bead.
In particular, a bead is done by a person or by an agent, never by both:
split out anything needing a human decision, approval, credential, or
observation into its own human-labelled bead joined by a dependency.
This applies to every bead you create here, including incidental ones for
follow-up work you noticed along the way.bug, feature, task) from context; default to
task.bd create --title="<title>" --description="<description>" --type=<type>
bd update <id> --status=in_progress
Use "Investigating..." if the scope is unclear. Do not add deliverables
absent from the request.bd update <id> --title="<better title>" \ --description="<final description>"bd close <id>.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Applies local reliability, viewport, tab-safety, stale-ref, widget, and browser-boundary lessons to every agent-browser automation. Use alongside the upstream agent-browser skill whenever navigating, clicking, filling, testing, extracting, taking screenshots, or debugging any website with agent-browser.
The English summary is being prepared. Showing the original description.
Size the agent-browser Chromium window to fill its current screen, leaving a configurable bottom margin for the desktop panel. Use before any agent-browser automation that needs the full screen visible without elements overlapping or scrolling off (e.g. Xero, dense web apps).
The English summary is being prepared. Showing the original description.
Create Claude Code slash commands, OpenCode command files, Pi prompt templates, and Codex custom prompts that delegate to the right subagent or skill. Use when creating new commands, porting commands across agent platforms, or refactoring existing commands to follow platform conventions.
The English summary is being prepared. Showing the original description.
Adds or changes allowed commands in AI agent permission configs for OpenCode and Claude Code. Use when a command needs adding to an agent's allow list, when permission settings for existing commands need changing, when setting up a new AI tool that requires command permissions, or when the user asks to stop being prompted for a particular command.
The English summary is being prepared. Showing the original description.
Creates a Beads issue for a described problem or piece of work without doing the work itself. Use when the user invokes `/bc` or `$bc`, or asks to file, log, or record a bead for something. To also carry out the work, use the `bx` skill instead.
The English summary is being prepared. Showing the original description.
Stores a persistent memory or learning with `bd remember` so it survives across sessions. Use when the user invokes `/bdr` or `$bdr`, or asks to remember, note, or persist an insight in a Beads workspace.
The English summary is being prepared. Showing the original description.