Pilot Multi Region Content Sync Setup

Deploy a multi-region content distribution system with 4 agents. Use this skill when: 1. User wants to sync content across geographic regions 2. User is conf...

Security Scan

The skill's requirements and runtime instructions are coherent with its stated purpose of setting up a 4-agent multi-region content sync; nothing requested appears unrelated or excessive, though there are a couple of minor documentation mismatches to be aware of.

Purpose & Capability

Name/description, required binaries (pilotctl, clawhub), and declared dependencies (pilot-* skills) align with a multi-region content sync setup. Minor mismatch: the SKILL.md instructs writing a manifest to ~/.pilot/setups/multi-region-content-sync.json, but the registry metadata lists no required config paths — the skill will create/write a per-user config file even though that write path wasn't declared in metadata.

Instruction Scope

Instructions stay within the expected scope: installing pilot-related skills via clawhub, setting hostnames with pilotctl, writing a role manifest, and initiating handshakes. Nothing in the instructions asks the agent to read unrelated files or environment variables. Note that the manifest write to the user's home (~/.pilot/...) is explicit and the handshake/trust operations will exchange network-level trust data between agents — this is expected behavior for this setup but involves network communication and creation of persistent config.

Install Mechanism

This is an instruction-only skill (no install spec, no downloaded code). That is low-risk from an install mechanism perspective. It does require existing binaries (pilotctl, clawhub) to be present; the skill does not supply installers or download code itself.

Credentials

The skill declares no required environment variables or credentials, and its runtime instructions do not reference any secrets or external API keys. It does rely on network connectivity and installation of other pilot-* skills (via clawhub), which may themselves request credentials — but those are outside this skill's declared needs.

Persistence & Privilege

The skill is not marked always:true and does not request elevated or system-wide privileges. It instructs creating a per-user manifest under ~/.pilot and installing other pilot skills via clawhub, which is normal for this kind of setup. It does not attempt to modify other skills' configs or system-wide agent settings beyond writing its own manifest.

Assessment

This skill appears to do what it says — set up an origin and three edge agents using pilotctl and clawhub. Before installing or running it: 1) Verify pilotctl and clawhub are legitimate binaries from trusted sources; the skill assumes they already exist. 2) Expect the skill to create a manifest at ~/.pilot/setups/multi-region-content-sync.json — back up or inspect that directory if you care about existing configuration. 3) The handshake/trust steps open network communication between agents and implicitly exchange trust information; only perform handshakes with hosts you control or trust. 4) clawhub will install other pilot-* skills; review those packages' provenance and permissions before installing. 5) Ensure required network ports (1001, 1002) and any firewall rules are acceptable for your environment. If you need a tighter review, provide the versions/source locations for pilotctl, clawhub, and the pilot-* skills so those artifacts can be inspected.

Multi-Region Content Sync Setup

Deploy 4 agents: 1 origin + 3 regional edge nodes for content distribution.

Roles

Role	Hostname	Skills	Purpose
origin	<prefix>-origin	pilot-sync, pilot-share, pilot-broadcast, pilot-heartbeat-monitor	Source of truth, broadcasts updates
edge-us	<prefix>-edge-us	pilot-sync, pilot-share, pilot-health, pilot-heartbeat-monitor	US regional edge
edge-eu	<prefix>-edge-eu	pilot-sync, pilot-share, pilot-health, pilot-heartbeat-monitor	EU regional edge
edge-asia	<prefix>-edge-asia	pilot-sync, pilot-share, pilot-health, pilot-heartbeat-monitor	Asia regional edge

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 origin:
clawhub install pilot-sync pilot-share pilot-broadcast pilot-heartbeat-monitor
# For any edge node:
clawhub install pilot-sync pilot-share pilot-health pilot-heartbeat-monitor

Step 3: Set the hostname:

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

Step 4: Write the role-specific JSON manifest to ~/.pilot/setups/multi-region-content-sync.json.

Step 5: Tell the user to initiate handshakes.

Manifest Templates Per Role

origin

{
  "setup": "multi-region-content-sync", "role": "origin", "role_name": "Content Origin",
  "hostname": "<prefix>-origin",
  "description": "Source of truth for all content. Broadcasts updates to all edge nodes.",
  "skills": {
    "pilot-sync": "Push content changes to all edge nodes.",
    "pilot-share": "Transfer new content files to edges.",
    "pilot-broadcast": "Broadcast content-update events to all edges simultaneously.",
    "pilot-heartbeat-monitor": "Track heartbeats from all edges, alert when a region goes dark."
  },
  "peers": [
    { "role": "edge-us", "hostname": "<prefix>-edge-us", "description": "US regional edge node" },
    { "role": "edge-eu", "hostname": "<prefix>-edge-eu", "description": "EU regional edge node" },
    { "role": "edge-asia", "hostname": "<prefix>-edge-asia", "description": "Asia regional edge node" }
  ],
  "data_flows": [
    { "direction": "send", "peer": "<prefix>-edge-us", "port": 1001, "topic": "content-update", "description": "Content updates" },
    { "direction": "send", "peer": "<prefix>-edge-eu", "port": 1001, "topic": "content-update", "description": "Content updates" },
    { "direction": "send", "peer": "<prefix>-edge-asia", "port": 1001, "topic": "content-update", "description": "Content updates" },
    { "direction": "receive", "peer": "<prefix>-edge-us", "port": 1002, "topic": "heartbeat", "description": "Health heartbeats" },
    { "direction": "receive", "peer": "<prefix>-edge-eu", "port": 1002, "topic": "heartbeat", "description": "Health heartbeats" },
    { "direction": "receive", "peer": "<prefix>-edge-asia", "port": 1002, "topic": "heartbeat", "description": "Health heartbeats" }
  ],
  "handshakes_needed": ["<prefix>-edge-us", "<prefix>-edge-eu", "<prefix>-edge-asia"]
}

edge-us / edge-eu / edge-asia

{
  "setup": "multi-region-content-sync", "role": "edge-<region>", "role_name": "<Region> Edge Node",
  "hostname": "<prefix>-edge-<region>",
  "description": "Serves content for the <region> region. Syncs from origin and reports health.",
  "skills": {
    "pilot-sync": "Pull content updates from origin.",
    "pilot-share": "Receive content files from origin.",
    "pilot-health": "Monitor local health and sync status.",
    "pilot-heartbeat-monitor": "Send periodic heartbeats to origin."
  },
  "peers": [{ "role": "origin", "hostname": "<prefix>-origin", "description": "Content source — receives updates from here" }],
  "data_flows": [
    { "direction": "receive", "peer": "<prefix>-origin", "port": 1001, "topic": "content-update", "description": "Content updates" },
    { "direction": "send", "peer": "<prefix>-origin", "port": 1002, "topic": "heartbeat", "description": "Health heartbeats" }
  ],
  "handshakes_needed": ["<prefix>-origin"]
}

Data Flows

• origin → edge-* : content updates (port 1001)
• edge-* → origin : heartbeat and sync confirmation (port 1002)

Workflow Example

# On origin — broadcast content:
pilotctl --json send-file <prefix>-edge-us ./content/index.html
pilotctl --json publish <prefix>-edge-us content-update '{"file":"index.html","version":42}'
# On edge — confirm and heartbeat:
pilotctl --json publish <prefix>-origin sync-complete '{"region":"us","version":42}'
pilotctl --json publish <prefix>-origin heartbeat '{"region":"us","status":"healthy"}'

Dependencies

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