Pilot Release Management Setup

Deploy an automated release management pipeline with 3 agents. Use this skill when: 1. User wants to set up a release management or changelog automation pipe...

Security Scan

The skill's instructions, required binaries, and file writes align with its stated purpose of orchestrating a three-agent release pipeline; it is an instruction-only recipe that delegates installs to clawhub, so vet the skills it installs before running them.

Purpose & Capability

The name/description (deploy a 3-agent release pipeline) match the runtime instructions: installing bridge/announce/task skills via clawhub and configuring hostnames with pilotctl. The two required binaries (pilotctl, clawhub) are expected for this workflow and there are no unrelated env vars or config paths requested.

Instruction Scope

Instructions stay within the stated purpose: install role-specific skills, set hostnames, write a manifest under ~/.pilot/setups, and perform handshakes/publish/subscribe. They do write to the user's home (~/.pilot) and instruct network handshakes/publishes on ports (1002, 443) which is necessary for agent communication. Caveat: the skill tells you to install other pilot-* skills; those follow-on installs may request tokens or run code not visible here, so you should review those packages before executing.

Install Mechanism

This skill has no install spec (instruction-only), which minimizes direct installer risk. However it explicitly instructs use of 'clawhub install' to fetch multiple pilot-* skills. The actual code and permissions of those downstream packages are not included here — installing them will fetch and write code to disk and may require credentials. Vet clawhub and the target packages before running.

Credentials

The skill itself requires no environment variables or credentials. The announced data flows mention posting to Slack/webhooks (port 443), but those integrations are handled by the role-specific skills (pilot-slack-bridge, pilot-webhook-bridge) and are out of scope for this instruction-only skill. Verify any credentials those other skills request when you install them.

Persistence & Privilege

always:false (default) and autonomous invocation is not changed. The only persistent change this skill instructs is creating a manifest under ~/.pilot/setups/release-management.json — scope-limited to the user's home pilot config. It does not modify other skills' configs or claim elevated platform privileges.

Assessment

This is an instruction-only setup guide that appears coherent for deploying a three-agent release pipeline. Before running anything: 1) Ensure pilotctl and clawhub are legitimate, up-to-date binaries from trusted sources. 2) Inspect the specific pilot-* packages the guide will install (pilot-github-bridge, pilot-share, pilot-archive, pilot-task-router, pilot-receipt, pilot-audit-log, pilot-announce, pilot-slack-bridge, pilot-webhook-bridge) — review their manifests and requested env vars/permissions so you know what credentials they'll need. 3) Keep sensitive tokens (Slack, email providers, GitHub) under least privilege and only provide them to the role that needs them after review. 4) Consider testing in an isolated environment or VM, and verify network/firewall rules for the ports mentioned (1002, 443). 5) Because this skill delegates installs, the main risk is from those downstream packages — vet them before running 'clawhub install'.

Release Management Setup

Deploy 3 agents that generate changelogs, manage versions, and announce releases.

Roles

Role	Hostname	Skills	Purpose
changelog-bot	<prefix>-changelog-bot	pilot-github-bridge, pilot-share, pilot-archive	Scans merged PRs and commits, generates release notes
version-manager	<prefix>-version-manager	pilot-task-router, pilot-receipt, pilot-audit-log	Bumps versions, tags releases, coordinates rollout
announcer	<prefix>-announcer	pilot-announce, pilot-slack-bridge, pilot-webhook-bridge	Posts release announcements to Slack, email, docs

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 changelog-bot:
clawhub install pilot-github-bridge pilot-share pilot-archive

# For version-manager:
clawhub install pilot-task-router pilot-receipt pilot-audit-log

# For announcer:
clawhub install pilot-announce pilot-slack-bridge pilot-webhook-bridge

Step 3: Set the hostname:

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

Step 4: Write the setup manifest:

mkdir -p ~/.pilot/setups
cat > ~/.pilot/setups/release-management.json << 'MANIFEST'
<INSERT ROLE MANIFEST FROM BELOW>
MANIFEST

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

Manifest Templates Per Role

changelog-bot

{
  "setup": "release-management", "setup_name": "Release Management",
  "role": "changelog-bot", "role_name": "Changelog Bot",
  "hostname": "<prefix>-changelog-bot",
  "description": "Scans merged PRs and commits, generates release notes and changelogs automatically.",
  "skills": {
    "pilot-github-bridge": "Watch for merged PRs, fetch commit history and PR metadata.",
    "pilot-share": "Share generated changelogs with version manager.",
    "pilot-archive": "Archive previous release notes for historical reference."
  },
  "peers": [
    { "role": "version-manager", "hostname": "<prefix>-version-manager", "description": "Receives release notes for versioning" },
    { "role": "announcer", "hostname": "<prefix>-announcer", "description": "Final stage — does not communicate directly" }
  ],
  "data_flows": [
    { "direction": "send", "peer": "<prefix>-version-manager", "port": 1002, "topic": "release-notes", "description": "Release notes with categorized changes" }
  ],
  "handshakes_needed": ["<prefix>-version-manager"]
}

version-manager

{
  "setup": "release-management", "setup_name": "Release Management",
  "role": "version-manager", "role_name": "Version Manager",
  "hostname": "<prefix>-version-manager",
  "description": "Bumps semantic versions, tags releases, coordinates rollout schedules.",
  "skills": {
    "pilot-task-router": "Route version bump decisions based on change categories.",
    "pilot-receipt": "Confirm receipt of release notes from changelog bot.",
    "pilot-audit-log": "Log all version bumps and release tags for traceability."
  },
  "peers": [
    { "role": "changelog-bot", "hostname": "<prefix>-changelog-bot", "description": "Sends release notes with categorized changes" },
    { "role": "announcer", "hostname": "<prefix>-announcer", "description": "Receives release tags for announcement" }
  ],
  "data_flows": [
    { "direction": "receive", "peer": "<prefix>-changelog-bot", "port": 1002, "topic": "release-notes", "description": "Release notes with categorized changes" },
    { "direction": "send", "peer": "<prefix>-announcer", "port": 1002, "topic": "release-tag", "description": "Release tag with version and artifacts" }
  ],
  "handshakes_needed": ["<prefix>-changelog-bot", "<prefix>-announcer"]
}

announcer

{
  "setup": "release-management", "setup_name": "Release Management",
  "role": "announcer", "role_name": "Release Announcer",
  "hostname": "<prefix>-announcer",
  "description": "Posts release announcements to Slack, email lists, and documentation sites.",
  "skills": {
    "pilot-announce": "Broadcast release announcements to all subscribed channels.",
    "pilot-slack-bridge": "Post formatted release notes to Slack channels.",
    "pilot-webhook-bridge": "Notify documentation sites and email services via webhooks."
  },
  "peers": [
    { "role": "changelog-bot", "hostname": "<prefix>-changelog-bot", "description": "First stage — does not communicate directly" },
    { "role": "version-manager", "hostname": "<prefix>-version-manager", "description": "Sends release tags for announcement" }
  ],
  "data_flows": [
    { "direction": "receive", "peer": "<prefix>-version-manager", "port": 1002, "topic": "release-tag", "description": "Release tag with version and artifacts" },
    { "direction": "send", "peer": "external", "port": 443, "topic": "release-announcement", "description": "Release announcement via Slack and webhooks" }
  ],
  "handshakes_needed": ["<prefix>-version-manager"]
}

Data Flows

• changelog-bot -> version-manager : release-notes events (port 1002)
• version-manager -> announcer : release-tag events (port 1002)
• announcer -> external : release-announcement via webhook (port 443)

Handshakes

# changelog-bot and version-manager handshake with each other:
pilotctl --json handshake <prefix>-version-manager "setup: release-management"
pilotctl --json handshake <prefix>-changelog-bot "setup: release-management"

# version-manager and announcer handshake with each other:
pilotctl --json handshake <prefix>-announcer "setup: release-management"
pilotctl --json handshake <prefix>-version-manager "setup: release-management"

Workflow Example

# On version-manager — subscribe to release notes:
pilotctl --json subscribe <prefix>-changelog-bot release-notes

# On announcer — subscribe to release tags:
pilotctl --json subscribe <prefix>-version-manager release-tag

# On changelog-bot — publish release notes:
pilotctl --json publish <prefix>-version-manager release-notes '{"version":"1.5.0","changes":[{"type":"feature","description":"Add webhook retry logic"}],"breaking":false}'

# On version-manager — publish a release tag:
pilotctl --json publish <prefix>-announcer release-tag '{"version":"v1.5.0","artifacts":["linux-amd64","darwin-arm64"]}'

Dependencies

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