Box0 (b0) Multi-Agent Platform

VerifiedCaution

Delegate tasks to AI agents via Box0. Use for parallel execution, specialized agents, and scheduled tasks.

Sby Skills Guide Bot
DevelopmentIntermediate
7/22/2026
Claude Code
#multi-agent#delegation#parallel-execution#cli#code-review

Recommended for

Automated summary

This skill delegates tasks to specialized AI agents through the Box0 (b0) command-line platform, supporting parallel or scheduled execution.

Strengths

  • Complete setup walkthrough with step-by-step verification (npm or Rust build)
  • Enables running multiple agents in parallel and collecting their results
  • Emphasizes composing detailed task prompts instead of forwarding the user's wording
  • Covers creating reusable named agents that run on a schedule or via webhook

Limitations

  • Requires installing the @box0/cli package and running a local Box0 server
  • The provided skill text is truncated (the concurrent-tasks section is incomplete)
  • Output quality depends heavily on how well the caller composes task prompts
When to use it

Use it when the user wants code review, security checks, or research gathered from several distinct agents or perspectives.

When not to use it

Avoid it for a quick single-step task one agent could handle, or where Box0 cannot be installed.

Security analysis

Caution
Quality score88/100

The skill does not contain destructive commands, secret exfiltration, obfuscated payloads, or attempts to disable safety controls. However, it uses Bash for legitimate but powerful setup and operational steps: unpinned global npm installation, source builds, starting a local server, and optionally exposing webhook endpoints that trigger agents. These are reasonable for the stated purpose but warrant caution.

Findings
  • •Instructs global installation of @box0/cli@latest via npm, which pulls and executes third-party package code without pinning a version
  • •Instructs building from source via git clone and cargo build, introducing additional supply-chain and local execution considerations
  • •Starts a persistent local Box0 server and may expose webhook trigger endpoints that run agents on any unauthenticated HTTP POST unless --webhook-secret is configured
  • •Delegates tasks to AI agents through b0 run, which may perform actions using the agent's own tool access; scope and permissions are not described here
How this analysis is made

Examples

Parallell code and security review
Use b0 to run a code review and a security check in parallel on the changes in branch feature-timeout, then summarize the findings.
Create a reusable reviewer agent
Create a Box0 agent named reviewer with instructions to review Rust pull requests for correctness and error handling, then run it on my current diff.
Scheduled research agent
Set up a b0 agent that researches AI agent frameworks every morning at 9h and reports the top new items.

name: b0 description: | Delegate tasks to AI agents via Box0. Use when the user asks to review code, check security, run tests, compare tools, get multiple perspectives, research a topic, analyze data, write docs, or any task that could benefit from specialized or parallel execution. Also use when the user mentions agent names or says "ask", "delegate", "get opinions from", or "have someone". allowed-tools:

  • Bash

Box0 (b0) Multi-Agent Platform

Run AI agents in parallel. Create agents with roles, trigger them on demand or on a schedule, and collect results.

Setup

Step 1: Check if Box0 is installed

b0 --version

If this succeeds, skip to Step 3.

Step 2: Install

npm install -g @box0/cli@latest

If npm is not available, build from source:

git clone https://github.com/risingwavelabs/box0.git
cd box0 && cargo build --release
export PATH="$PWD/target/release:$PATH"

Step 3: Check if server is running

b0 server status

If this shows "Server is running", skip to Step 5.

Step 4: Start the server

b0 server

On first start, Box0 creates an admin account and auto-configures ~/.b0/config.toml.

Step 5: Install the skill

npx skills add risingwavelabs/skills --skill b0

Step 6: Verify

b0 ls

This should run without errors. Setup is complete.

Tell the user: "Box0 is installed and ready. You can now delegate tasks to agents."


When to use

When the user's request could benefit from specialized agents or parallel execution, delegate.

Choosing an agent

Always use b0 run with an existing agent or create one with b0 add. Use b0 ls to see what is available.

Use b0 add when:

  • No existing agent matches the task
  • The user wants a named agent for future reuse

Use b0 run <name> when:

  • b0 ls shows an existing agent that matches the task
  • The user mentions an agent by name ("ask the reviewer")

Commands

b0 ls                                                  # list available agents
b0 add <name> --instructions "..."                     # create a named agent
b0 add <name> --instructions "..." --every 1h --task "..." # create scheduled agent
b0 add <name> --instructions "..." --webhook           # create agent with trigger URL
b0 add <name> --instructions "..." --webhook-secret s  # create agent with HMAC secret
b0 rm <name>                                           # delete an agent
b0 run <agent> "<detailed task prompt>"                # trigger agent and wait for result
b0 run <agent> "<task>" --timeout 600                  # trigger with custom timeout
b0 info <name>                                         # show agent info including trigger URL
b0 logs <name>                                         # show recent agent logs
b0 update <name> --instructions "..."                  # update agent instructions

How to write task prompts

This is critical. Do NOT forward the user's words. Compose a complete, actionable prompt.

Bad:

b0 run reviewer "review this PR"

Good:

b0 run reviewer "Review the changes on branch feature-timeout in this repo.
The PR adds timeout handling to src/handler.rs.
Focus on correctness, edge cases, and error handling.
Cite line numbers for any issues found."

Steps:

  1. Gather context first - read relevant files, run git diff, check the branch
  2. Include specifics - file paths, line numbers, branch names, what changed and why
  3. State the deliverable - what the agent should produce (a list of issues, a summary, a fix)

For large content (diffs, file contents), pipe via stdin:

git diff main..HEAD | b0 run reviewer "Review the following diff. Focus on correctness."

Concurrent tasks

Run multiple agents in parallel:

b0 run reviewer "Review the changes on branch feature-timeout..." &
b0 run security "Check src/handler.rs for OWASP top 10 vulnerabilities..." &
b0 run doc-writer "Update README to reflect the new timeout config option..." &
wait

Each b0 run call blocks until its agent completes. Run them in the background with & to parallelize.

Scheduled agents

Create an agent that runs automatically on a schedule:

b0 add monitor --instructions "Check logs for errors." --every 1h --task "scan logs"

Intervals: 30s, 5m, 1h, 6h, 1d.

Webhook triggers

Every agent with --webhook has a trigger URL. Any HTTP POST to that URL runs the agent.

b0 add notifier --instructions "Process incoming alerts." --webhook

This prints the trigger URL: <server>/trigger/<workspace>/<agent-name>.

To see the trigger URL for an existing agent:

b0 info notifier

To add HMAC signature verification:

b0 add notifier --instructions "Process alerts." --webhook --webhook-secret mysecret

Then sign requests with X-Hub-Signature-256: sha256=<hmac-sha256-of-body>.

Error handling

If an agent fails, b0 run reports the error. Decide whether to:

  • Retry with a clearer prompt
  • Try a different agent
  • Handle the task yourself
  • Report the failure to the user

Troubleshooting

| Symptom | Fix | |---------|-----| | b0: command not found | Run npm install -g @box0/cli@latest | | b0 server status shows not running | Run b0 server | | b0 run times out | Increase timeout with --timeout 600 | | Agent returns empty result | Check agent instructions with b0 info <name> |

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/box0-b0-multi-agent-platform-mrwakf3u/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/box0-b0-multi-agent-platform-mrwakf3u' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/box0-b0-multi-agent-platform-mrwakf3u/download' --output '.skill-downloads/box0-b0-multi-agent-platform-mrwakf3u/SKILL.md.part' && mv '.skill-downloads/box0-b0-multi-agent-platform-mrwakf3u/SKILL.md.part' '.skill-downloads/box0-b0-multi-agent-platform-mrwakf3u/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Setup

Step 1: Check if Box0 is installed

b0 --version

If this succeeds, skip to Step 3.

Step 2: Install

npm install -g @box0/cli@latest

If npm is not available, build from source:

git clone https://github.com/risingwavelabs/box0.git
cd box0 && cargo build --release
export PATH="$PWD/target/release:$PATH"

Step 3: Check if server is running

b0 server status

If this shows "Server is running", skip to Step 5.

Step 4: Start the server

b0 server

On first start, Box0 creates an admin account and auto-configures ~/.b0/config.toml.

Step 5: Install the skill

npx skills add risingwavelabs/skills --skill b0

Step 6: Verify

b0 ls

This should run without errors. Setup is complete.

Tell the user: "Box0 is installed and ready. You can now delegate tasks to agents."


The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/box0-b0-multi-agent-platform-mrwakf3u/SKILL.md' && test -s '.skill-downloads/box0-b0-multi-agent-platform-mrwakf3u/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/b0' && cp -R '.skill-downloads/box0-b0-multi-agent-platform-mrwakf3u' '.claude/skills/b0'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/box0-b0-multi-agent-platform-mrwakf3u'

openskills read 'box0-b0-multi-agent-platform-mrwakf3u'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/box0-b0-multi-agent-platform-mrwakf3u/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills