Pilot Ci Cd Pipeline Setup

Deploy a decentralized CI/CD pipeline with 3 agents. Use this skill when: 1. User wants to set up a CI/CD pipeline across multiple agents 2. User is configur...

Security Scan

The skill's instructions, required binaries, and actions are coherent with its stated purpose of deploying a 3-agent decentralized CI/CD pipeline; it does not request unrelated credentials or perform unexplained actions.

Purpose & Capability

Name and description match the actions requested: installing Pilot skills via clawhub, setting hostnames with pilotctl, writing a local ~/.pilot manifest, and performing peer handshakes. Required binaries (pilotctl, clawhub) are appropriate and necessary for the described workflow.

Instruction Scope

SKILL.md stays within CI/CD setup scope: it instructs installing declared Pilot skills, creating manifests under ~/.pilot, setting hostnames, and initiating handshakes. It does instruct network actions (handshakes, publish/send-file) which are expected for a decentralized pipeline. Note: it delegates GitHub/webhook functionality to other Pilot skills (pilot-github-bridge, pilot-webhook-bridge) — those subordinate skills may require external credentials or additional configuration not listed here.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — nothing will be downloaded or written by the skill itself beyond the manifest it asks the operator to create. Low install risk.

Credentials

The skill requests no environment variables or credentials itself, which is proportionate. However, the recommended subordinate skills (e.g., pilot-github-bridge, pilot-webhook-bridge) commonly require service tokens or webhook secrets; the SKILL.md does not enumerate those, so users must supply and configure those credentials separately.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request persistent system-wide privileges or modify other skills' configurations beyond writing a setup manifest to ~/.pilot, which is reasonable for configuration purposes.

Assessment

This skill appears internally consistent with its purpose. Before installing: ensure you have the pilotctl and clawhub binaries; confirm you trust the Pilot network peers you will handshake with (handshakes auto-approve trust once both sides send them); be prepared to supply credentials for services the subordinate skills use (GitHub webhooks, Slack/webhook targets, etc.), since this SKILL.md does not configure those; verify the skill source/homepage and review AGPL licensing implications. If you need tighter security, inspect the subordinate Pilot skills (pilot-github-bridge, pilot-webhook-bridge, pilot-share, etc.) for any credential or network behavior before enabling them.

CI/CD Pipeline Setup

Deploy 3 agents that build, test, and deploy code with zero central server.

Roles

Role	Hostname	Skills	Purpose
ci-builder	<prefix>-ci-builder	pilot-task-router, pilot-share, pilot-github-bridge	Builds code, shares artifacts
ci-tester	<prefix>-ci-tester	pilot-task-router, pilot-share, pilot-audit-log	Runs tests, logs results
ci-deployer	<prefix>-ci-deployer	pilot-task-router, pilot-share, pilot-webhook-bridge, pilot-receipt	Deploys, sends receipts

Setup Procedure

Step 1: Ask the user which role this agent should play and what prefix to use.

Step 2: Install the skills for the chosen role:

# For ci-builder:
clawhub install pilot-task-router pilot-share pilot-github-bridge
# For ci-tester:
clawhub install pilot-task-router pilot-share pilot-audit-log
# For ci-deployer:
clawhub install pilot-task-router pilot-share pilot-webhook-bridge pilot-receipt

Step 3: Set the hostname:

pilotctl --json set-hostname <prefix>-<role>

Step 4: Write the setup manifest:

mkdir -p ~/.pilot/setups

Then write the role-specific JSON manifest to ~/.pilot/setups/ci-cd-pipeline.json.

Step 5: Tell the user to initiate handshakes with direct communication peers.

Manifest Templates Per Role

ci-builder

{
  "setup": "ci-cd-pipeline",
  "setup_name": "CI/CD Pipeline",
  "role": "ci-builder",
  "role_name": "Build Agent",
  "hostname": "<prefix>-ci-builder",
  "description": "Listens for GitHub push/PR webhooks, clones the repo, runs builds, and shares artifacts with the test agent.",
  "skills": {
    "pilot-task-router": "Accept build requests and route artifacts to ci-tester.",
    "pilot-share": "Send build artifacts (tarballs, binaries) to ci-tester.",
    "pilot-github-bridge": "Listen for GitHub webhooks (push, PR) to trigger builds."
  },
  "peers": [
    { "role": "ci-tester", "hostname": "<prefix>-ci-tester", "description": "Receives build artifacts for testing" },
    { "role": "ci-deployer", "hostname": "<prefix>-ci-deployer", "description": "Receives deployment receipt" }
  ],
  "data_flows": [
    { "direction": "send", "peer": "<prefix>-ci-tester", "port": 1001, "topic": "build-ready", "description": "Build artifacts and test instructions" },
    { "direction": "receive", "peer": "<prefix>-ci-deployer", "port": 1002, "topic": "deploy-receipt", "description": "Deployment confirmation" }
  ],
  "handshakes_needed": ["<prefix>-ci-tester", "<prefix>-ci-deployer"]
}

ci-tester

{
  "setup": "ci-cd-pipeline",
  "setup_name": "CI/CD Pipeline",
  "role": "ci-tester",
  "role_name": "Test Agent",
  "hostname": "<prefix>-ci-tester",
  "description": "Receives build artifacts, runs test suites, and logs results. Passes successful builds to the deployer.",
  "skills": {
    "pilot-task-router": "Accept test tasks from ci-builder and forward passing builds to ci-deployer.",
    "pilot-share": "Receive artifacts from ci-builder, send tested artifacts to ci-deployer.",
    "pilot-audit-log": "Log all test runs with pass/fail results and coverage."
  },
  "peers": [
    { "role": "ci-builder", "hostname": "<prefix>-ci-builder", "description": "Sends build artifacts" },
    { "role": "ci-deployer", "hostname": "<prefix>-ci-deployer", "description": "Receives tested artifacts" }
  ],
  "data_flows": [
    { "direction": "receive", "peer": "<prefix>-ci-builder", "port": 1001, "topic": "build-ready", "description": "Build artifacts" },
    { "direction": "send", "peer": "<prefix>-ci-deployer", "port": 1001, "topic": "tests-passed", "description": "Tested artifacts with report" }
  ],
  "handshakes_needed": ["<prefix>-ci-builder", "<prefix>-ci-deployer"]
}

ci-deployer

{
  "setup": "ci-cd-pipeline",
  "setup_name": "CI/CD Pipeline",
  "role": "ci-deployer",
  "role_name": "Deploy Agent",
  "hostname": "<prefix>-ci-deployer",
  "description": "Receives tested artifacts, deploys to production, sends deployment receipts, and triggers post-deploy webhooks.",
  "skills": {
    "pilot-task-router": "Accept deploy tasks from ci-tester.",
    "pilot-share": "Receive tested artifacts from ci-tester.",
    "pilot-webhook-bridge": "Trigger post-deploy webhooks (Slack, monitoring).",
    "pilot-receipt": "Send deployment receipts back to ci-builder."
  },
  "peers": [
    { "role": "ci-builder", "hostname": "<prefix>-ci-builder", "description": "Receives deployment receipt" },
    { "role": "ci-tester", "hostname": "<prefix>-ci-tester", "description": "Sends tested artifacts" }
  ],
  "data_flows": [
    { "direction": "receive", "peer": "<prefix>-ci-tester", "port": 1001, "topic": "tests-passed", "description": "Tested artifacts" },
    { "direction": "send", "peer": "<prefix>-ci-builder", "port": 1002, "topic": "deploy-receipt", "description": "Deployment confirmation" }
  ],
  "handshakes_needed": ["<prefix>-ci-builder", "<prefix>-ci-tester"]
}

Data Flows

• ci-builder → ci-tester : build artifacts (port 1001)
• ci-tester → ci-deployer : tested artifacts with test report (port 1001)
• ci-deployer → ci-builder : deployment receipt (port 1002)

Handshakes

# All three agents handshake each other:
pilotctl --json handshake <prefix>-ci-tester "setup: ci-cd-pipeline"
pilotctl --json handshake <prefix>-ci-deployer "setup: ci-cd-pipeline"
pilotctl --json handshake <prefix>-ci-builder "setup: ci-cd-pipeline"

Workflow Example

# On ci-builder — send build artifact:
pilotctl --json send-file <prefix>-ci-tester ./build/app-v2.3.tar.gz
pilotctl --json publish <prefix>-ci-tester build-ready '{"commit":"a1b2c3d","branch":"main"}'

# On ci-tester — forward to deployer:
pilotctl --json send-file <prefix>-ci-deployer ./build/app-v2.3.tar.gz
pilotctl --json publish <prefix>-ci-deployer tests-passed '{"commit":"a1b2c3d","tests":142,"passed":142}'

# On ci-deployer — send receipt:
pilotctl --json publish <prefix>-ci-builder deploy-receipt '{"commit":"a1b2c3d","status":"success"}'

Dependencies

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