Makes the agent reconsider a task it just handed back to the human and find a way to do it itself, checking memory, CLI tools, skills, MCP servers, and documentation in turn. Use when the user invokes `/you` or `$you`, or replies that the agent should do something itself rather than asking them.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You just suggested that the human user should do something manually. Reconsider whether you can do it yourself. In order:
Agent memory: Search persistent memory first. It may directly recall a
tool, skill, MCP, or workflow that fits this task. Use
bd memories <keyword> if Beads is in use; otherwise use the current
agent's memory facilities.
CLI tools: Is there a command-line tool available that can accomplish
this? Common ones you may overlook: agent-browser (for any web
interaction: navigating, clicking, filling forms, scraping, screenshots),
gh (GitHub), railway, bd (beads), stow, jq, etc. Check $PATH
with which <tool> or compgen -c if unsure.
Skills: Is there a skill listed in the available-skills reminder that
covers this task? Re-scan the list. For example, agent-browser handles
web interaction such as navigating, clicking, filling forms, scraping, and
screenshots. If nothing obvious matches, use the find-skills skill to
discover installable ones you don't have loaded yet.
MCP servers: Check the configured MCP servers for tools that fit the task. Many MCPs expose capabilities beyond what's obvious from their name, such as GitHub, Notion, Gmail, and Calendar. Use the current agent's tool discovery facility to load schemas for relevant MCP tools.
Documentation: Check AGENTS.md, CLAUDE.md, and any README.md in
the relevant directory. They may document a tool, script, or workflow you
missed.
Only if all five turn up nothing should you ask the user to do it manually. Explain what you searched for and why none of the options fit.
Doing it yourself means doing the task you were given, not finding another route to its answer. Never widen the task into the user's private data to make up for a check you could not complete, for example:
If such access is the only way, ask for that specific access, naming the source and why, or hand the check back with what you did verify.
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.