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...

Security Scan

The skill's requirements and runtime instructions are consistent with its stated purpose (deploying four pilot protocol agents) and do not request unrelated credentials or install artifacts themselves.

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.

Assessment

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.

Dev Team Assistants Setup

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

Roles

Role	Hostname	Skills	Purpose
reviewer	<prefix>-reviewer	pilot-github-bridge, pilot-review, pilot-chat	Reviews PR diffs for quality
test-runner	<prefix>-test-runner	pilot-github-bridge, pilot-task-router, pilot-audit-log	Runs test suites
doc-writer	<prefix>-doc-writer	pilot-github-bridge, pilot-share, pilot-task-router	Generates docs
coordinator	<prefix>-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": "<prefix>-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": "<prefix>-reviewer", "port": 1002, "topic": "pr-review", "description": "PR details for review" },
    { "direction": "send", "peer": "<prefix>-test-runner", "port": 1002, "topic": "pr-test", "description": "PR details for testing" },
    { "direction": "send", "peer": "<prefix>-doc-writer", "port": 1002, "topic": "pr-docs", "description": "PR details for docs" },
    { "direction": "receive", "peer": "<prefix>-reviewer", "port": 1002, "topic": "review-result", "description": "Review findings" },
    { "direction": "receive", "peer": "<prefix>-test-runner", "port": 1002, "topic": "test-result", "description": "Test results" },
    { "direction": "receive", "peer": "<prefix>-doc-writer", "port": 1001, "topic": "docs-result", "description": "Generated docs" }
  ],
  "handshakes_needed": ["<prefix>-reviewer", "<prefix>-test-runner", "<prefix>-doc-writer"]
}

reviewer

{
  "setup": "dev-team-assistants", "role": "reviewer", "role_name": "Code Reviewer",
  "hostname": "<prefix>-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": "<prefix>-coordinator", "port": 1002, "topic": "pr-review", "description": "PR details" },
    { "direction": "send", "peer": "<prefix>-coordinator", "port": 1002, "topic": "review-result", "description": "Review findings" }
  ],
  "handshakes_needed": ["<prefix>-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 <prefix>-reviewer --task '{"pr":1234,"repo":"acme/api","action":"review"}'
pilotctl --json task submit <prefix>-test-runner --task '{"pr":1234,"action":"test","branch":"feature/auth"}'
# On reviewer — return:
pilotctl --json publish <prefix>-coordinator review-result '{"pr":1234,"issues":2,"approval":"changes_requested"}'
# On test-runner — return:
pilotctl --json publish <prefix>-coordinator test-result '{"pr":1234,"passed":89,"failed":0,"coverage":82}'

Dependencies

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