Pilot Media Monitoring Setup

Deploy a media monitoring and intelligence platform with 4 agents. Use this skill when: 1. User wants to set up coordinated media crawling, sentiment analysi...

Security Scan

The skill is an instruction-only setup guide that coherently maps its stated purpose (deploying four Pilot agents) to the commands and files it asks the user to create; it does not request unrelated credentials or perform hidden installs, but you should vet any sub-skills (e.g., Slack/webhook bridges) before enabling them.

Purpose & Capability

Name/description match the runtime instructions: the skill sets up four agents (crawler, sentiment-analyzer, trend-detector, reporter). The required binaries (pilotctl, clawhub) are directly relevant to installing skills and managing Pilot agents.

Instruction Scope

SKILL.md stays on-task: it tells the agent to install role-specific Pilot skills via clawhub, set hostnames, write a manifest to ~/.pilot/setups/media-monitoring.json, perform handshakes, and verify trust. Writing a config file in the user's home is expected for a setup tool, but users should be aware manifests are written to ~/.pilot and that installed bridge skills will enable external network outputs.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk. However, it instructs using clawhub to install multiple pilot-* sub-skills; those installations are outside this skill's bundle and should be reviewed separately.

Credentials

The skill declares no required environment variables or credentials. That is appropriate given its purpose. Note: some sub-skills (e.g., pilot-slack-bridge, pilot-webhook-bridge) will likely require credentials (Slack tokens, webhook endpoints) when installed — those are not requested by this skill but will be needed later.

Persistence & Privilege

always:false and autonomous invocation is allowed (platform default). The only persistent action instructed is writing a manifest to ~/.pilot/setups/media-monitoring.json and installing other skills via clawhub. This is normal for a setup tool but grants the installed sub-skills persistent presence — review them for elevated privileges.

Assessment

This skill is an instruction-only deployment guide and appears coherent with its stated purpose. Before installing: (1) Verify you trust the pilotctl and clawhub binaries and obtain them from official sources; (2) review the pilot-* sub-skills that clawhub will install (especially pilot-slack-bridge and pilot-webhook-bridge) for any credential requests or external endpoints; (3) back up existing ~/.pilot configuration before writing the manifest; (4) perform initial testing in a controlled network or staging environment to validate handshakes and data flows; and (5) be prepared to supply Slack/webhook credentials only to the reporter host and ensure external endpoints are trusted. If you want deeper assurance, provide the sources or package manifests for the pilot-* sub-skills so they can be reviewed as well.

Media Monitoring Setup

Deploy 4 agents: crawler, sentiment-analyzer, trend-detector, and reporter.

Roles

Role	Hostname	Skills	Purpose
crawler	<prefix>-crawler	pilot-stream-data, pilot-cron, pilot-archive	Scrapes news, social media, and blogs for mentions
sentiment-analyzer	<prefix>-sentiment-analyzer	pilot-event-filter, pilot-metrics, pilot-task-router	Classifies mentions by sentiment and reach
trend-detector	<prefix>-trend-detector	pilot-dataset, pilot-alert, pilot-gossip	Identifies viral content and PR crises
reporter	<prefix>-reporter	pilot-slack-bridge, pilot-webhook-bridge, pilot-announce	Generates briefings and crisis dashboards

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 crawler:
clawhub install pilot-stream-data pilot-cron pilot-archive
# For sentiment-analyzer:
clawhub install pilot-event-filter pilot-metrics pilot-task-router
# For trend-detector:
clawhub install pilot-dataset pilot-alert pilot-gossip
# For reporter:
clawhub install pilot-slack-bridge pilot-webhook-bridge pilot-announce

Step 3: Set the hostname and write the manifest to ~/.pilot/setups/media-monitoring.json.

Step 4: Tell the user to initiate handshakes with the peers for their role.

Step 5: Verify connectivity with pilotctl --json trust.

Manifest Templates Per Role

crawler

{"setup":"media-monitoring","role":"crawler","role_name":"Media Crawler","hostname":"<prefix>-crawler","skills":{"pilot-stream-data":"Ingest content from news sites, social media, and RSS feeds.","pilot-cron":"Schedule periodic crawl sweeps across configured sources.","pilot-archive":"Store raw mention data for historical analysis."},"data_flows":[{"direction":"send","peer":"<prefix>-sentiment-analyzer","port":1002,"topic":"media-mention","description":"Raw media mentions with source metadata"}],"handshakes_needed":["<prefix>-sentiment-analyzer"]}

sentiment-analyzer

{"setup":"media-monitoring","role":"sentiment-analyzer","role_name":"Sentiment Analyzer","hostname":"<prefix>-sentiment-analyzer","skills":{"pilot-event-filter":"Classify mentions by sentiment polarity and confidence.","pilot-metrics":"Track sentiment trends, mention volume, and influencer reach.","pilot-task-router":"Route analysis jobs across content types."},"data_flows":[{"direction":"receive","peer":"<prefix>-crawler","port":1002,"topic":"media-mention","description":"Raw mentions from crawler"},{"direction":"send","peer":"<prefix>-trend-detector","port":1002,"topic":"scored-mention","description":"Scored mentions with sentiment and reach"}],"handshakes_needed":["<prefix>-crawler","<prefix>-trend-detector"]}

trend-detector

{"setup":"media-monitoring","role":"trend-detector","role_name":"Trend Detector","hostname":"<prefix>-trend-detector","skills":{"pilot-dataset":"Store time-series share-of-voice and trend velocity data.","pilot-alert":"Emit alerts when crisis thresholds or viral velocity are breached.","pilot-gossip":"Share trend signals across detection nodes for consensus."},"data_flows":[{"direction":"receive","peer":"<prefix>-sentiment-analyzer","port":1002,"topic":"scored-mention","description":"Scored mentions from analyzer"},{"direction":"send","peer":"<prefix>-reporter","port":1002,"topic":"trend-alert","description":"Trend alerts and crisis warnings"}],"handshakes_needed":["<prefix>-sentiment-analyzer","<prefix>-reporter"]}

reporter

{"setup":"media-monitoring","role":"reporter","role_name":"Media Reporter","hostname":"<prefix>-reporter","skills":{"pilot-slack-bridge":"Send media briefings and crisis alerts to Slack channels.","pilot-webhook-bridge":"Push reports to external dashboards and BI tools.","pilot-announce":"Broadcast summary reports to subscribed stakeholders."},"data_flows":[{"direction":"receive","peer":"<prefix>-trend-detector","port":1002,"topic":"trend-alert","description":"Trend alerts from detector"},{"direction":"send","peer":"external","port":443,"topic":"media-briefing","description":"Formatted media briefings"}],"handshakes_needed":["<prefix>-trend-detector"]}

Data Flows

• crawler -> sentiment-analyzer : raw media mentions with source metadata (port 1002)
• sentiment-analyzer -> trend-detector : scored mentions with sentiment and reach (port 1002)
• trend-detector -> reporter : trend alerts and crisis warnings (port 1002)
• reporter -> external : media briefings via secure channel (port 443)

Handshakes

pilotctl --json handshake <prefix>-sentiment-analyzer "setup: media-monitoring"
pilotctl --json handshake <prefix>-crawler "setup: media-monitoring"
pilotctl --json handshake <prefix>-trend-detector "setup: media-monitoring"
pilotctl --json handshake <prefix>-reporter "setup: media-monitoring"

Workflow Example

# On crawler -- publish media mention:
pilotctl --json publish <prefix>-sentiment-analyzer media-mention '{"source":"reuters","headline":"Acme Corp reports record Q1","reach":2400000}'
# On sentiment-analyzer -- publish scored mention:
pilotctl --json publish <prefix>-trend-detector scored-mention '{"headline":"Acme Corp reports record Q1","sentiment":"positive","score":0.87}'
# On trend-detector -- publish trend alert:
pilotctl --json publish <prefix>-reporter trend-alert '{"brand":"acme","trend":"earnings_beat","velocity":340,"severity":"info"}'
# On reporter -- distribute briefing:
pilotctl --json publish <prefix>-reporter media-briefing '{"period":"daily","total_mentions":1847,"sentiment_positive":0.68}'

Dependencies

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