Menu
Use for cross-repo questions. Relay a message to another agentsbox agent and return its answer.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user wants to set up, configure, or review `.agentsbox/config.toml` for a project — e.g. "set my default agent to claude", "add a published port for my dev server", "persist my cargo/pip/go cache across `agentsbox enter` runs", "configure agentsbox for this repo", or any time they want to extend the project config without clobbering existing keys. Inspects the project to propose `[[ports]]` and `[[volumes]]` and writes valid TOML directly (the `agentsbox` CLI isn't available in-box).
Use when the user asks to scaffold a minimal Nix flake for a project that does not have one.
| name | agentsbox-ask-agent |
| description | Use for cross-repo questions. Relay a message to another agentsbox agent and return its answer. |
Run:
send-message <agent-name> "<question>"
<agent-name> is the other container's A2A alias: the basename of its project directory by default, or the value passed to agentsbox enter --a2a --name <name>.
Completion criterion: the response is printed. Relay it to the user, quoting the parts that matter; do not dump it verbatim.
Before sending a DataPart for an op like put, search, or delete, confirm the target supports it:
curl -s http://<agent-name>:4096/.well-known/agent-card.json
Completion criterion: the op is listed in the agent card. Only then send the DataPart.
could not reach agent '<name>' means the container is not running with --a2a, or the alias is wrong. Tell the user to start it with agentsbox enter --a2a and confirm the alias. Do not retry blindly.