Pilot Inventory Management Setup

Deploy an inventory management system with 3 agents. Use this skill when: 1. User wants to set up an automated inventory management system 2. User is configu...

Security Scan

The skill's required tools and instructions align with its stated purpose of deploying three Pilot agents; nothing requested appears disproportionate or unrelated.

Purpose & Capability

Name/description match the actions in SKILL.md: it installs agent skills (via clawhub), sets hostnames and manifests (via pilotctl), and wires agent-to-agent and external webhook flows. Required binaries (pilotctl, clawhub) are appropriate and expected.

Instruction Scope

Instructions are mostly scoped to setup tasks (install skills, set hostname, write a manifest to ~/.pilot/setups, establish handshakes). They also describe outbound data flows (alerter -> external supplier on port 443) and installing bridge skills (webhook/slack) that will require external credentials/configuration later; the SKILL.md does not itself request those credentials but it does direct network-facing behavior, so operators should confirm external endpoints and credential configuration before enabling those bridges.

Install Mechanism

No install spec is embedded in the skill bundle (instruction-only). All runtime installs are CLI commands (clawhub install) invoked by the operator; no arbitrary downloads or archive extraction are included in the skill itself.

Credentials

The skill declares no environment variables or credentials, which is consistent with the provided instructions. However, some installed bridge skills (pilot-webhook-bridge, pilot-slack-bridge) will typically require external credentials or webhooks to function; their absence from requires.env is not malicious but users must be prepared to supply and secure those credentials outside this skill.

Persistence & Privilege

The skill has no always:true flag and does not request elevated/persistent platform privileges. It writes a manifest under the user's home (~/.pilot) which is appropriate for a per-deployment setup and does not modify other skills' configs beyond installing them via clawhub (expected for setup).

Assessment

This skill appears to do what it claims: install Pilot skills, set hostnames, write a local manifest, and establish agent handshakes. Before running it, verify you trust the pilotctl and clawhub binaries and understand what those commands do on your systems. Manually review the manifest templates and the exact clawhub install commands before executing. Be aware that webhook and Slack bridges will require external credentials/endpoints you must configure and secure — verify target URLs (supplier ERP endpoints, Slack/webhook destinations) to ensure you are not sending sensitive inventory data to unintended endpoints. Finally, confirm network connectivity and handshake coordination between the three hosts; the setup will open agent-to-agent and outbound webhook flows as part of normal operation.

Inventory Management Setup

Deploy 3 agents that automate inventory tracking from stock monitoring to reorder alerts.

Roles

Role	Hostname	Skills	Purpose
tracker	<prefix>-tracker	pilot-metrics, pilot-stream-data, pilot-audit-log	Monitors stock levels, tracks shipments, updates quantities
forecaster	<prefix>-forecaster	pilot-dataset, pilot-task-router, pilot-cron	Analyzes sales trends and predicts stock needs
alerter	<prefix>-alerter	pilot-alert, pilot-webhook-bridge, pilot-slack-bridge	Triggers reorder notifications and sends PO requests

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 tracker:
clawhub install pilot-metrics pilot-stream-data pilot-audit-log

# For forecaster:
clawhub install pilot-dataset pilot-task-router pilot-cron

# For alerter:
clawhub install pilot-alert pilot-webhook-bridge 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/inventory-management.json << 'MANIFEST'
<role-specific manifest from templates below>
MANIFEST

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

Manifest Templates Per Role

tracker

{
  "setup": "inventory-management", "setup_name": "Inventory Management",
  "role": "tracker", "role_name": "Stock Tracker",
  "hostname": "<prefix>-tracker",
  "description": "Monitors warehouse stock levels, tracks incoming/outgoing shipments, and updates quantities in real time.",
  "skills": {
    "pilot-metrics": "Collect and expose real-time stock level metrics and movement rates.",
    "pilot-stream-data": "Stream live inventory updates as shipments arrive and orders ship.",
    "pilot-audit-log": "Log all stock movements for compliance and audit trail."
  },
  "peers": [{"role": "forecaster", "hostname": "<prefix>-forecaster", "description": "Receives stock snapshots for demand analysis"}],
  "data_flows": [{"direction": "send", "peer": "<prefix>-forecaster", "port": 1002, "topic": "stock-snapshot", "description": "Stock snapshots with quantities and movement history"}],
  "handshakes_needed": ["<prefix>-forecaster"]
}

forecaster

{
  "setup": "inventory-management", "setup_name": "Inventory Management",
  "role": "forecaster", "role_name": "Demand Forecaster",
  "hostname": "<prefix>-forecaster",
  "description": "Analyzes sales trends, seasonal patterns, and lead times to predict stock needs.",
  "skills": {
    "pilot-dataset": "Load and analyze historical sales data and seasonal patterns.",
    "pilot-task-router": "Route incoming stock snapshots to the appropriate forecasting model.",
    "pilot-cron": "Schedule recurring demand forecast runs on daily and weekly cadences."
  },
  "peers": [
    {"role": "tracker", "hostname": "<prefix>-tracker", "description": "Sends stock snapshots with current levels"},
    {"role": "alerter", "hostname": "<prefix>-alerter", "description": "Receives reorder forecasts for threshold alerting"}
  ],
  "data_flows": [
    {"direction": "receive", "peer": "<prefix>-tracker", "port": 1002, "topic": "stock-snapshot", "description": "Stock snapshots with quantities and movement history"},
    {"direction": "send", "peer": "<prefix>-alerter", "port": 1002, "topic": "reorder-forecast", "description": "Reorder forecasts with quantities and urgency scores"}
  ],
  "handshakes_needed": ["<prefix>-tracker", "<prefix>-alerter"]
}

alerter

{
  "setup": "inventory-management", "setup_name": "Inventory Management",
  "role": "alerter", "role_name": "Reorder Alerter",
  "hostname": "<prefix>-alerter",
  "description": "Triggers reorder notifications when stock hits thresholds and sends PO requests to suppliers.",
  "skills": {
    "pilot-alert": "Evaluate stock levels against thresholds and fire reorder alerts.",
    "pilot-webhook-bridge": "Send purchase order requests to supplier systems via webhook.",
    "pilot-slack-bridge": "Notify procurement team in Slack when reorders are triggered."
  },
  "peers": [{"role": "forecaster", "hostname": "<prefix>-forecaster", "description": "Sends reorder forecasts with quantities and urgency"}],
  "data_flows": [
    {"direction": "receive", "peer": "<prefix>-forecaster", "port": 1002, "topic": "reorder-forecast", "description": "Reorder forecasts with quantities and urgency scores"},
    {"direction": "send", "peer": "external", "port": 443, "topic": "purchase-order", "description": "Purchase order requests to suppliers"}
  ],
  "handshakes_needed": ["<prefix>-forecaster"]
}

Data Flows

• tracker -> forecaster : stock-snapshot (port 1002)
• forecaster -> alerter : reorder-forecast (port 1002)
• alerter -> external : purchase-order via webhook (port 443)

Handshakes

# tracker and forecaster handshake with each other:
pilotctl --json handshake <prefix>-forecaster "setup: inventory-management"
pilotctl --json handshake <prefix>-tracker "setup: inventory-management"

# forecaster and alerter handshake with each other:
pilotctl --json handshake <prefix>-alerter "setup: inventory-management"
pilotctl --json handshake <prefix>-forecaster "setup: inventory-management"

Workflow Example

# On forecaster -- subscribe to stock snapshots:
pilotctl --json subscribe <prefix>-tracker stock-snapshot

# On alerter -- subscribe to reorder forecasts:
pilotctl --json subscribe <prefix>-forecaster reorder-forecast

# On tracker -- publish a stock snapshot:
pilotctl --json publish <prefix>-forecaster stock-snapshot '{"warehouse":"us-east-1","sku":"WIDGET-A100","quantity_on_hand":142,"daily_velocity":12}'

# On forecaster -- publish reorder forecast to alerter:
pilotctl --json publish <prefix>-alerter reorder-forecast '{"sku":"WIDGET-A100","current_stock":142,"reorder_quantity":500,"urgency":"high"}'

Dependencies

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