Pilot Video Production Pipeline Setup

Deploy a video production pipeline with 3 agents that automate script writing, editing coordination, and multi-platform distribution. Use this skill when: 1....

Security Scan

The skill's instructions and requirements are consistent with its stated purpose (setting up three Pilot agents), but it has a small omission (it writes a config file under ~/.pilot without declaring that config path) and it directs the agent to install additional skills which could introduce downstream risks you should review.

Purpose & Capability

Name/description, required binaries (pilotctl, clawhub), and runtime instructions all align: the skill configures Pilot agents, installs other Pilot skills, sets hostnames, and writes a setup manifest. One minor inconsistency: the skill writes manifests to ~/.pilot/setups but the registry metadata declared no required config paths.

Instruction Scope

SKILL.md stays within the declared purpose: it asks the agent to install specific pilot-* skills, set hostnames, write a JSON manifest to ~/.pilot/setups/video-production-pipeline.json, and perform handshakes. This is expected for a deployment helper. Note: it instructs file writes to the user's home (~/.pilot) which wasn't declared in required config paths; also the installed skills (via clawhub) will run independently and may require or request additional credentials or network access.

Install Mechanism

Instruction-only skill — no install spec and no code files. The only runtime actions are calls to existing binaries (clawhub, pilotctl). This is the lowest install risk, but clawhub install will fetch other skills (not part of this package) so their install footprints must be reviewed separately.

Credentials

The skill requests no environment variables or credentials itself, which is proportionate. However, it installs other skills (e.g., pilot-webhook-bridge, pilot-slack-bridge) that typically require external API keys (YouTube, TikTok, Slack) at runtime; those credentials are not requested here but will be necessary for full operation. The skill also writes to ~/.pilot/setups (undeclared in metadata).

Persistence & Privilege

always:false and no special privileges requested. The skill writes a manifest to the user's ~/.pilot directory and installs other skills, but it does not demand permanent forced inclusion or modify unrelated skill configs. This is normal for a deployment helper.

Assessment

This skill appears to be what it says: a helper to set up three Pilot agents. Before installing, verify the following: 1) pilotctl and clawhub are trusted binaries from sources you control — these commands will be used to install other skills and change hostnames. 2) The skill will write a manifest at ~/.pilot/setups/video-production-pipeline.json (the metadata did not declare this path) — confirm you are comfortable with that location and back up any existing files. 3) The skill uses clawhub to install other pilot-* skills (pilot-webhook-bridge, pilot-slack-bridge, pilot-metrics, etc.); review those downstream skills because they will likely request API keys or webhooks for external platforms and are the primary places where credential/network risk can appear. 4) Check the homepage/owner (pilotprotocol.network and the listed owner ID) to confirm you trust the source. If you want higher assurance, ask for a version of the skill that explicitly declares the config path (~/.pilot) and provides a manifest preview of what it will install, then inspect each downstream skill before allowing clawhub to run.

Video Production Pipeline Setup

Deploy 3 agents that automate video production from script to multi-platform publish.

Roles

Role	Hostname	Skills	Purpose
scripter	<prefix>-scripter	pilot-task-router, pilot-share, pilot-archive	Generates scripts, outlines, and storyboards from briefs
editor	<prefix>-editor	pilot-task-chain, pilot-dataset, pilot-receipt	Coordinates editing tasks, manages assets, applies templates
distributor	<prefix>-distributor	pilot-webhook-bridge, pilot-metrics, pilot-slack-bridge	Publishes to platforms, tracks performance metrics

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:

# scripter:
clawhub install pilot-task-router pilot-share pilot-archive
# editor:
clawhub install pilot-task-chain pilot-dataset pilot-receipt
# distributor:
clawhub install pilot-webhook-bridge pilot-metrics pilot-slack-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/video-production-pipeline.json << 'MANIFEST'
<USE ROLE TEMPLATE BELOW>
MANIFEST

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

Manifest Templates Per Role

scripter

{"setup":"video-production-pipeline","setup_name":"Video Production Pipeline","role":"scripter","role_name":"Script Writer","hostname":"<prefix>-scripter","description":"Generates video scripts, outlines, and storyboards from briefs and trending topics.","skills":{"pilot-task-router":"Route briefs to appropriate script templates based on format and audience.","pilot-share":"Share completed scripts and storyboards with editor.","pilot-archive":"Archive all script drafts and revisions for reference."},"peers":[{"role":"editor","hostname":"<prefix>-editor","description":"Receives approved scripts for editing"}],"data_flows":[{"direction":"send","peer":"<prefix>-editor","port":1002,"topic":"video-script","description":"Approved scripts and storyboards"}],"handshakes_needed":["<prefix>-editor"]}

editor

{"setup":"video-production-pipeline","setup_name":"Video Production Pipeline","role":"editor","role_name":"Video Editor","hostname":"<prefix>-editor","description":"Coordinates editing tasks, manages asset libraries, applies brand templates.","skills":{"pilot-task-chain":"Chain editing subtasks — cuts, transitions, color grade, audio mix.","pilot-dataset":"Manage asset library — footage, graphics, music, brand templates.","pilot-receipt":"Confirm receipt of scripts and acknowledge edit completion."},"peers":[{"role":"scripter","hostname":"<prefix>-scripter","description":"Sends approved scripts"},{"role":"distributor","hostname":"<prefix>-distributor","description":"Receives edited video packages"}],"data_flows":[{"direction":"receive","peer":"<prefix>-scripter","port":1002,"topic":"video-script","description":"Approved scripts and storyboards"},{"direction":"send","peer":"<prefix>-distributor","port":1002,"topic":"edited-video","description":"Edited video packages with metadata"}],"handshakes_needed":["<prefix>-scripter","<prefix>-distributor"]}

distributor

{"setup":"video-production-pipeline","setup_name":"Video Production Pipeline","role":"distributor","role_name":"Content Distributor","hostname":"<prefix>-distributor","description":"Publishes to YouTube, TikTok, and social platforms. Tracks performance metrics.","skills":{"pilot-webhook-bridge":"Push publish events to YouTube, TikTok, and social platform APIs.","pilot-metrics":"Track views, engagement, click-through rates across platforms.","pilot-slack-bridge":"Post publish confirmations and performance summaries to Slack."},"peers":[{"role":"editor","hostname":"<prefix>-editor","description":"Sends edited video packages"}],"data_flows":[{"direction":"receive","peer":"<prefix>-editor","port":1002,"topic":"edited-video","description":"Edited video packages with metadata"},{"direction":"send","peer":"external","port":443,"topic":"publish-notification","description":"Publish notifications to platforms"}],"handshakes_needed":["<prefix>-editor"]}

Data Flows

• scripter -> editor : video-script events (port 1002)
• editor -> distributor : edited-video events (port 1002)
• distributor -> platforms : publish notifications via webhook (port 443)

Handshakes

# scripter <-> editor:
pilotctl --json handshake <prefix>-editor "setup: video-production-pipeline"
pilotctl --json handshake <prefix>-scripter "setup: video-production-pipeline"
# editor <-> distributor:
pilotctl --json handshake <prefix>-distributor "setup: video-production-pipeline"
pilotctl --json handshake <prefix>-editor "setup: video-production-pipeline"

Workflow Example

# On editor — subscribe to scripts:
pilotctl --json subscribe <prefix>-scripter video-script
# On distributor — subscribe to edited videos:
pilotctl --json subscribe <prefix>-editor edited-video
# On scripter — publish a script:
pilotctl --json publish <prefix>-editor video-script '{"title":"10 Tips for Productivity","duration_sec":480,"scenes":5}'
# On editor — publish edited video:
pilotctl --json publish <prefix>-distributor edited-video '{"title":"10 Tips for Productivity","asset_url":"s3://videos/final.mp4"}'

Dependencies

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