← Back to Skills Marketplace
femto

Acp Team

by femto · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ⚠ suspicious
383
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install acp-team
Description
Team coordination layer for multi-agent workflows with mailbox, task board, and lease-based task management. Use when users need to coordinate multiple AI ag...
README (SKILL.md)

acp-team: Multi-Agent Team Coordination

Team coordination layer for acpx - mailbox, task board, and multi-agent workflows.

When to Use This Skill

Use this skill when the user:

  • Wants to coordinate multiple AI agents working together
  • Needs a shared task board with claim/lease mechanics
  • Wants agents to communicate via message inboxes
  • Asks about spawning team members with different roles
  • Needs task assignment and status tracking across agents

Architecture

┌─────────────────────────────────────────────────────────┐
│                    acp-team                             │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐     │
│  │  TaskStore  │  │ MessageBus  │  │  TeamStore  │     │
│  │  .tasks/    │  │ .team/inbox │  │ .team/config│     │
│  └─────────────┘  └─────────────┘  └─────────────┘     │
│         │                │                │             │
│         └────────────────┼────────────────┘             │
│                          │                              │
│                    Coordinator                          │
│                          │                              │
│                          ▼                              │
│                   acpx sessions                         │
└─────────────────────────────────────────────────────────┘

Installation

npm install -g acp-team

Requires acpx to be installed:

npm install -g acpx

Quick Start

# Initialize team in your project
acp-team init --name my-project

# Create tasks
acp-team task create "Fix authentication bug"
acp-team task create "Write unit tests"

# Spawn a team member
acp-team spawn alice -r coder -p "Fix the auth bug in task #1"

# Check status
acp-team status

# Send messages
acp-team msg send alice "How's the bug fix going?"
acp-team msg inbox alice

Commands Reference

Team Management

Command Description
acp-team init [--name \x3Cteam>] Initialize team in project
acp-team status Show team and task status
acp-team spawn \x3Cname> -r \x3Crole> -p \x3Cprompt> Spawn a team member with acpx
acp-team shutdown \x3Cmember> Request member shutdown

Task Board

Command Description
acp-team task create \x3Csubject> Create a new task
acp-team task list List all tasks
acp-team task unclaimed List unclaimed tasks
acp-team task claim \x3Cid> [-o \x3Cowner>] Claim a task
acp-team task assign \x3Cid> \x3Cmember> Assign task to member
acp-team task done \x3Cid> Mark task as done

Task Lease System

Command Description
acp-team task claim-lease \x3Cid> -o \x3Cowner> -d \x3Cms> Claim with lease (default 60s)
acp-team task heartbeat \x3Cid> -t \x3Ctoken> Renew lease
acp-team task release-expired Release all expired leases

Messaging

Command Description
acp-team msg send \x3Cto> \x3Cmessage> Send direct message
acp-team msg broadcast \x3Cmessage> Broadcast to all members
acp-team msg inbox [name] Read inbox (drains messages)
acp-team msg peek [name] Peek inbox (without draining)

Task State Machine

pending → claimed → running → blocked → completed
                                 ↓           ↓
                            cancelled    failed
                                 ↓           ↓
                                     timed_out

Message Envelope Format

{
  "schema_version": "1.0",
  "message_id": "uuid",
  "trace_id": "...",
  "sender": "alice",
  "recipient": "bob",
  "type": "message",
  "content": "...",
  "created_at": 1234567890,
  "priority": 1
}

File Structure

.team/
├── config.json          # Team configuration
└── inbox/
    ├── alice.jsonl      # Alice's inbox
    ├── bob.jsonl        # Bob's inbox
    └── lead.jsonl       # Lead's inbox

.tasks/
├── task_1.json          # Task #1
├── task_2.json          # Task #2
└── ...

Workflow Example

# 1. Initialize
acp-team init --name feature-dev

# 2. Create tasks
acp-team task create "Design API schema"
acp-team task create "Implement backend"
acp-team task create "Write tests"

# 3. Spawn designer
acp-team spawn designer -r architect -p "Design the API schema for task #1" -a claude

# 4. After design is done, spawn implementer
acp-team spawn coder -r backend -p "Implement the API based on the design"

# 5. Monitor progress
acp-team status
acp-team msg inbox lead

# 6. Spawn tester
acp-team spawn tester -r qa -p "Write tests for the new API"

Resources

Usage Guidance
This skill is an instruction-only description of an npm-based CLI that manages local task/inbox files and orchestrates agents through acpx. Before installing or using it: 1) verify the npm package (acp-team) and its publisher—review the package source code or GitHub repo and confirm it matches the SKILL.md; 2) be aware npm -g installs execute third-party code and may require elevated privileges—prefer inspecting the package or using a local/non-global install or a sandbox; 3) acpx likely needs model-provider credentials (e.g., Anthropic/OpenAI) even though the skill metadata doesn't declare them—check acpx docs and only provide credentials you trust; 4) understand that 'msg inbox' can drain (delete) messages and the tool will create/modify .team/ .tasks files in your project; and 5) run the CLI in an isolated project or container if you want to limit blast radius. The primary issue is the mismatch between what the README says you must install/use and the registry metadata (no declared binaries/credentials/install spec).
Capability Analysis
Type: OpenClaw Skill Name: acp-team Version: 0.1.0 The acp-team skill bundle provides a coordination layer for multi-agent workflows, including task management, messaging, and agent spawning. It utilizes the Agent Control Protocol (ACP) ecosystem (referencing acpx) and manages state through local directories (.team/ and .tasks/). The instructions and commands are consistent with the stated purpose of team coordination, and there is no evidence of malicious intent, data exfiltration, or hidden prompt injection.
Capability Assessment
Purpose & Capability
The skill's name and description claim a team coordination layer for multi-agent workflows and the SKILL.md describes exactly that (taskboard, inbox, lease system, spawning agents via acpx). This purpose is consistent with the commands and file layout described. However, the skill instructions require installing an npm package and the acpx tool, but the registry metadata lists no required binaries or install steps—an omission that is inconsistent and worth noting.
Instruction Scope
SKILL.md contains concrete CLI usage and describes local filesystem paths (.team/, .tasks/) and message inbox semantics (including 'drain' behavior). It does not instruct reading unrelated system files or exfiltrating data. The only scope concern is that 'msg inbox' is documented to drain messages (deleting local data) which is expected behavior but should be understood by users.
Install Mechanism
There is no install spec in the registry (instruction-only), but SKILL.md tells users to run 'npm install -g acp-team' and to install 'acpx'. Installing a global npm package is a common but moderately risky install mechanism because it runs third-party code on the host. The registry not declaring this install step is an inconsistency and increases the burden on the user to verify the package origin and contents before installing globally.
Credentials
The skill declares no required environment variables or credentials. The SKILL.md does not explicitly request provider API keys, but it references 'acpx sessions' and spawning agents (example uses '-a claude'), which implies integration with model providers or external services that likely require credentials handled by acpx. The lack of declared credential requirements in the metadata is an omission that could surprise users at runtime.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. As an instruction-only skill it does not persist configuration in the registry, but the CLI it documents will create/modify local directories (.team, .tasks) within the project. That file-system persistence is expected for this functionality and is confined to the project directory as described.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install acp-team
  3. After installation, invoke the skill by name or use /acp-team
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release of acp-team: multi-agent team coordination for acpx - Provides mailbox-based messaging, shared task board, and team management for multi-agent workflows - Supports task creation, assignment, status tracking, and lease-based task claiming - Enables spawning team members (agents) with different roles and prompts - Direct and broadcast messaging between agents via inboxes - Includes command-line interface for managing teams, tasks, and communication
Metadata
Slug acp-team
Version 0.1.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Acp Team?

Team coordination layer for multi-agent workflows with mailbox, task board, and lease-based task management. Use when users need to coordinate multiple AI ag... It is an AI Agent Skill for Claude Code / OpenClaw, with 383 downloads so far.

How do I install Acp Team?

Run "/install acp-team" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Acp Team free?

Yes, Acp Team is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Acp Team support?

Acp Team is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Acp Team?

It is built and maintained by femto (@femto); the current version is v0.1.0.

💬 Comments