← Back to Skills Marketplace
teoslayer

Pilot Dev Team Assistants Setup

by Calin Teodor · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
73
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install pilot-dev-team-assistants-setup
Description
Deploy a dev team assistant system with 4 agents. Use this skill when: 1. User wants to automate code review, testing, and docs for PRs 2. User is configurin...
README (SKILL.md)

Dev Team Assistants Setup

Deploy 4 agents that automate the PR workflow: review, test, docs, and coordination.

Roles

Role Hostname Skills Purpose
reviewer \x3Cprefix>-reviewer pilot-github-bridge, pilot-review, pilot-chat Reviews PR diffs for quality
test-runner \x3Cprefix>-test-runner pilot-github-bridge, pilot-task-router, pilot-audit-log Runs test suites
doc-writer \x3Cprefix>-doc-writer pilot-github-bridge, pilot-share, pilot-task-router Generates docs
coordinator \x3Cprefix>-coordinator pilot-github-bridge, pilot-task-chain, pilot-slack-bridge, pilot-broadcast Orchestrates and summarizes

Setup Procedure

Step 1: Ask the user which role and prefix.

Step 2: Install skills:

# reviewer:
clawhub install pilot-github-bridge pilot-review pilot-chat
# test-runner:
clawhub install pilot-github-bridge pilot-task-router pilot-audit-log
# doc-writer:
clawhub install pilot-github-bridge pilot-share pilot-task-router
# coordinator:
clawhub install pilot-github-bridge pilot-task-chain pilot-slack-bridge pilot-broadcast

Step 3: Set hostname and write manifest to ~/.pilot/setups/dev-team-assistants.json.

Step 4: Handshake with coordinator (all agents handshake the coordinator).

Manifest Templates Per Role

coordinator

{
  "setup": "dev-team-assistants", "role": "coordinator", "role_name": "PR Coordinator",
  "hostname": "\x3Cprefix>-coordinator",
  "skills": {
    "pilot-github-bridge": "Watch GitHub for new PRs, post unified summary comments.",
    "pilot-task-chain": "Fan out review/test/doc tasks and collect results.",
    "pilot-slack-bridge": "Post PR status updates to Slack.",
    "pilot-broadcast": "Broadcast new PR notifications to all assistants."
  },
  "data_flows": [
    { "direction": "send", "peer": "\x3Cprefix>-reviewer", "port": 1002, "topic": "pr-review", "description": "PR details for review" },
    { "direction": "send", "peer": "\x3Cprefix>-test-runner", "port": 1002, "topic": "pr-test", "description": "PR details for testing" },
    { "direction": "send", "peer": "\x3Cprefix>-doc-writer", "port": 1002, "topic": "pr-docs", "description": "PR details for docs" },
    { "direction": "receive", "peer": "\x3Cprefix>-reviewer", "port": 1002, "topic": "review-result", "description": "Review findings" },
    { "direction": "receive", "peer": "\x3Cprefix>-test-runner", "port": 1002, "topic": "test-result", "description": "Test results" },
    { "direction": "receive", "peer": "\x3Cprefix>-doc-writer", "port": 1001, "topic": "docs-result", "description": "Generated docs" }
  ],
  "handshakes_needed": ["\x3Cprefix>-reviewer", "\x3Cprefix>-test-runner", "\x3Cprefix>-doc-writer"]
}

reviewer

{
  "setup": "dev-team-assistants", "role": "reviewer", "role_name": "Code Reviewer",
  "hostname": "\x3Cprefix>-reviewer",
  "skills": {
    "pilot-github-bridge": "Fetch PR diffs from GitHub.",
    "pilot-review": "Analyze code for quality, security, and style issues.",
    "pilot-chat": "Discuss review findings with coordinator."
  },
  "data_flows": [
    { "direction": "receive", "peer": "\x3Cprefix>-coordinator", "port": 1002, "topic": "pr-review", "description": "PR details" },
    { "direction": "send", "peer": "\x3Cprefix>-coordinator", "port": 1002, "topic": "review-result", "description": "Review findings" }
  ],
  "handshakes_needed": ["\x3Cprefix>-coordinator"]
}

Data Flows

  • coordinator → reviewer/test-runner/doc-writer : PR details (port 1002)
  • reviewer/test-runner → coordinator : results (port 1002)
  • doc-writer → coordinator : generated docs (port 1001)

Workflow Example

# On coordinator — fan out:
pilotctl --json task submit \x3Cprefix>-reviewer --task '{"pr":1234,"repo":"acme/api","action":"review"}'
pilotctl --json task submit \x3Cprefix>-test-runner --task '{"pr":1234,"action":"test","branch":"feature/auth"}'
# On reviewer — return:
pilotctl --json publish \x3Cprefix>-coordinator review-result '{"pr":1234,"issues":2,"approval":"changes_requested"}'
# On test-runner — return:
pilotctl --json publish \x3Cprefix>-coordinator test-result '{"pr":1234,"passed":89,"failed":0,"coverage":82}'

Dependencies

Requires pilot-protocol skill, pilotctl binary, clawhub binary, and a running daemon.

Usage Guidance
This instruction-only skill appears coherent and low-risk, but review and approve any downstream skill installs before running them. Before you proceed: (1) make sure pilotctl and clawhub are official/trusted binaries, (2) be prepared to provide GitHub/Slack/service tokens when installing pilot-github-bridge or pilot-slack-bridge, (3) note the manifest will be written to ~/.pilot/setups/dev-team-assistants.json, and (4) verify network/port rules (the manifest references ports like 1001/1002) and handshake/trust steps so you only bind agents and keys you control. If you want a higher-assurance review, provide the manifests or the source of the downstream skills (pilot-github-bridge, pilot-slack-bridge, etc.) so those integrations can be inspected for required credentials and network endpoints.
Capability Analysis
Type: OpenClaw Skill Name: pilot-dev-team-assistants-setup Version: 1.0.0 The skill bundle provides a legitimate setup configuration for a multi-agent development workflow involving code review, testing, and documentation. It uses standard ecosystem tools like `clawhub` and `pilotctl` to install dependencies and establish communication between agents, with no evidence of malicious intent, data exfiltration, or unauthorized execution in SKILL.md or README.md.
Capability Tags
crypto
Capability Assessment
Purpose & Capability
Name/description (deploying a 4-agent PR workflow) matches the instructions. Required binaries (pilotctl, clawhub) are appropriate and are actually used throughout the SKILL.md. Required env vars/config paths are none, which is consistent with an instruction-only setup helper.
Instruction Scope
SKILL.md stays within setup scope: it instructs installing listed pilot skills via clawhub, setting hostnames, writing a manifest to ~/.pilot/setups/dev-team-assistants.json, and performing handshakes. These actions are expected for multi-agent setup. Note: the skill tells the operator to install other skills (pilot-github-bridge, pilot-slack-bridge, etc.); those downstream skills may require credentials or broader permissions not declared here.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest install risk. It relies on existing binaries (pilotctl, clawhub) rather than downloading arbitrary code itself.
Credentials
This skill itself requests no environment variables or credentials, which is proportionate. However, the recommended downstream skills (GitHub bridge, Slack bridge, audit log, etc.) typically require service tokens or config; the SKILL.md does not enumerate those, so operators should expect to provide credentials when installing those components.
Persistence & Privilege
always is false and the skill is user-invocable. It does instruct writing a manifest to the user's home (~/.pilot), which is normal for a local agent setup. It does not modify other skills' configs or claim permanent elevated privileges.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install pilot-dev-team-assistants-setup
  3. After installation, invoke the skill by name or use /pilot-dev-team-assistants-setup
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Slug pilot-dev-team-assistants-setup
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Pilot Dev Team Assistants Setup?

Deploy a dev team assistant system with 4 agents. Use this skill when: 1. User wants to automate code review, testing, and docs for PRs 2. User is configurin... It is an AI Agent Skill for Claude Code / OpenClaw, with 73 downloads so far.

How do I install Pilot Dev Team Assistants Setup?

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

Is Pilot Dev Team Assistants Setup free?

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

Which platforms does Pilot Dev Team Assistants Setup support?

Pilot Dev Team Assistants Setup is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Pilot Dev Team Assistants Setup?

It is built and maintained by Calin Teodor (@teoslayer); the current version is v1.0.0.

💬 Comments