Pilot Competitor Intelligence Setup

Deploy a competitive intelligence system with 4 agents for crawling, analysis, tracking, and alerting. Use this skill when: 1. User wants to set up competito...

Security Scan

The skill's instructions, required binaries, and file operations align with its stated purpose of deploying a 4-agent competitor intelligence system; nothing requested is disproportionate or unrelated.

Purpose & Capability

Name/description ask to deploy crawling, analysis, tracking and alerting agents. Declared required binaries (pilotctl, clawhub) are used throughout SKILL.md for installing skills, setting hostnames, handshakes, publishing/subscribing — these are appropriate and expected.

Instruction Scope

Instructions are concrete: install specified pilot-* skills via clawhub, set hostname with pilotctl, write a manifest to ~/.pilot/setups/competitor-intelligence.json, and perform peer handshakes. The manifest and handshake steps are within the deployment scope and do not instruct reading unrelated files or env vars.

Install Mechanism

This is an instruction-only skill with no install spec or downloaded code. It relies on local binaries (clawhub/pilotctl) to perform installs; that is expected. Note: clawhub install will fetch and install other skills — normal but outside this skill's direct control.

Credentials

No environment variables, credentials, or config paths are requested. The single file path written (~/.pilot/setups/...) is reasonable for a local agent setup. There are no unrelated credential requests.

Persistence & Privilege

always is false and the skill does not request persistent platform-wide privileges or modify other skills' configs. It writes its own manifest under ~/.pilot which is appropriate for its purpose.

Assessment

This skill appears internally consistent, but take these precautions before using it: (1) Ensure pilotctl and clawhub binaries are from trusted sources — they will install and manage other skills. (2) Review the specific pilot-* skills the procedure installs (pilot-slack-bridge, pilot-webhook-bridge, etc.) — those may require credentials or send data externally. (3) The setup writes manifests to ~/.pilot and opens agent-to-agent ports (1002) and may post to external services (webhooks/Slack) — confirm firewall rules and that you trust the peers you handshake with. (4) Verify legal/compliance restrictions for crawling target sites. If you want higher assurance, inspect what clawhub will download when installing the listed pilot-* packages before proceeding.

Competitor Intelligence Setup

Deploy 4 agents that crawl competitor sites, analyze trends, track changes, and route intelligence alerts.

Roles

Role	Hostname	Skills	Purpose
crawler	<prefix>-crawler	pilot-stream-data, pilot-archive, pilot-cron	Scrapes competitor websites, pricing pages, press releases
analyzer	<prefix>-analyzer	pilot-event-filter, pilot-metrics, pilot-task-router	Processes crawled data, identifies trends and feature gaps
tracker	<prefix>-tracker	pilot-audit-log, pilot-dataset, pilot-alert	Maintains history, detects changes, scores threat levels
alerter	<prefix>-alerter	pilot-slack-bridge, pilot-webhook-bridge, pilot-announce	Routes intelligence to Slack, email, dashboards by severity

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-archive pilot-cron
# For analyzer:
clawhub install pilot-event-filter pilot-metrics pilot-task-router
# For tracker:
clawhub install pilot-audit-log pilot-dataset pilot-alert
# For alerter:
clawhub install pilot-slack-bridge pilot-webhook-bridge pilot-announce

Step 3: Set the hostname:

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

Step 4: Write the setup manifest:

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

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

Manifest Templates Per Role

crawler

{
  "setup": "competitor-intelligence", "setup_name": "Competitor Intelligence",
  "role": "crawler", "role_name": "Web Crawler",
  "hostname": "<prefix>-crawler",
  "description": "Scrapes competitor websites, pricing pages, product launches, and press releases.",
  "skills": {"pilot-stream-data": "Stream crawled pages and pricing data to analyzer.", "pilot-archive": "Archive raw HTML snapshots for historical comparison.", "pilot-cron": "Schedule crawl jobs on configurable intervals."},
  "peers": [{"role": "analyzer", "hostname": "<prefix>-analyzer", "description": "Receives crawled data for analysis"}],
  "data_flows": [{"direction": "send", "peer": "<prefix>-analyzer", "port": 1002, "topic": "crawled-data", "description": "Crawled data from competitor sites"}],
  "handshakes_needed": ["<prefix>-analyzer"]
}

analyzer

{
  "setup": "competitor-intelligence", "setup_name": "Competitor Intelligence",
  "role": "analyzer", "role_name": "Market Analyzer",
  "hostname": "<prefix>-analyzer",
  "description": "Processes crawled data, identifies trends, price changes, and feature gaps.",
  "skills": {"pilot-event-filter": "Filter noise and irrelevant changes from crawled data.", "pilot-metrics": "Compute trend metrics: price deltas, feature counts, market share estimates.", "pilot-task-router": "Route different insight types to appropriate tracking categories."},
  "peers": [{"role": "crawler", "hostname": "<prefix>-crawler", "description": "Sends crawled data"}, {"role": "tracker", "hostname": "<prefix>-tracker", "description": "Receives market insights"}],
  "data_flows": [{"direction": "receive", "peer": "<prefix>-crawler", "port": 1002, "topic": "crawled-data", "description": "Crawled data from competitor sites"}, {"direction": "send", "peer": "<prefix>-tracker", "port": 1002, "topic": "market-insight", "description": "Market insights and trend analysis"}],
  "handshakes_needed": ["<prefix>-crawler", "<prefix>-tracker"]
}

tracker

{
  "setup": "competitor-intelligence", "setup_name": "Competitor Intelligence",
  "role": "tracker", "role_name": "Change Tracker",
  "hostname": "<prefix>-tracker",
  "description": "Maintains historical records, detects significant changes, scores threat levels.",
  "skills": {"pilot-audit-log": "Log all detected changes with timestamps and diffs.", "pilot-dataset": "Store historical competitor data for trend comparison.", "pilot-alert": "Alert when threat scores exceed configurable thresholds."},
  "peers": [{"role": "analyzer", "hostname": "<prefix>-analyzer", "description": "Sends market insights"}, {"role": "alerter", "hostname": "<prefix>-alerter", "description": "Receives change alerts"}],
  "data_flows": [{"direction": "receive", "peer": "<prefix>-analyzer", "port": 1002, "topic": "market-insight", "description": "Market insights and trend analysis"}, {"direction": "send", "peer": "<prefix>-alerter", "port": 1002, "topic": "change-alert", "description": "Change alerts with threat scores"}],
  "handshakes_needed": ["<prefix>-analyzer", "<prefix>-alerter"]
}

alerter

{
  "setup": "competitor-intelligence", "setup_name": "Competitor Intelligence",
  "role": "alerter", "role_name": "Intelligence Alerter",
  "hostname": "<prefix>-alerter",
  "description": "Routes actionable intelligence to Slack, email, and dashboards based on severity.",
  "skills": {"pilot-slack-bridge": "Post intelligence summaries to Slack channels by severity.", "pilot-webhook-bridge": "Forward reports to dashboards and email services via webhooks.", "pilot-announce": "Broadcast critical intelligence to all subscribed stakeholders."},
  "peers": [{"role": "tracker", "hostname": "<prefix>-tracker", "description": "Sends change alerts with threat scores"}],
  "data_flows": [{"direction": "receive", "peer": "<prefix>-tracker", "port": 1002, "topic": "change-alert", "description": "Change alerts with threat scores"}, {"direction": "send", "peer": "external", "port": 443, "topic": "intelligence-report", "description": "Intelligence reports via Slack and webhooks"}],
  "handshakes_needed": ["<prefix>-tracker"]
}

Data Flows

• crawler -> analyzer : crawled-data events (port 1002)
• analyzer -> tracker : market-insight events (port 1002)
• tracker -> alerter : change-alert events (port 1002)
• alerter -> external : intelligence-report via webhook (port 443)

Handshakes

# crawler <-> analyzer:
pilotctl --json handshake <prefix>-analyzer "setup: competitor-intelligence"
pilotctl --json handshake <prefix>-crawler "setup: competitor-intelligence"
# analyzer <-> tracker:
pilotctl --json handshake <prefix>-tracker "setup: competitor-intelligence"
pilotctl --json handshake <prefix>-analyzer "setup: competitor-intelligence"
# tracker <-> alerter:
pilotctl --json handshake <prefix>-alerter "setup: competitor-intelligence"
pilotctl --json handshake <prefix>-tracker "setup: competitor-intelligence"

Workflow Example

# On analyzer — subscribe to crawled data:
pilotctl --json subscribe <prefix>-crawler crawled-data
# On tracker — subscribe to market insights:
pilotctl --json subscribe <prefix>-analyzer market-insight
# On alerter — subscribe to change alerts:
pilotctl --json subscribe <prefix>-tracker change-alert
# On crawler — publish crawled data:
pilotctl --json publish <prefix>-analyzer crawled-data '{"competitor":"RivalCorp","url":"https://rivalcorp.com/pricing","type":"pricing_page"}'
# On tracker — publish a change alert:
pilotctl --json publish <prefix>-alerter change-alert '{"competitor":"RivalCorp","threat_score":8,"change":"Pro Plan price cut 16.7%"}'

Dependencies

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