Pilot Energy Grid Optimizer Setup

Deploy an energy grid optimization system with 4 agents. Use this skill when: 1. User wants to set up coordinated energy monitoring, forecasting, optimizatio...

Security Scan

The skill's requests and runtime instructions are coherent with its stated purpose (deploying a four-agent energy grid setup), but it directs the agent to install multiple other packages and write persistent configuration so you should vet those downstream components before installing.

Purpose & Capability

Name, description, required binaries (pilotctl, clawhub), and the steps (install pilot-* skills, set hostname, handshake) align with an orchestrator that provisions four coordinated agents for grid monitoring and control.

Instruction Scope

SKILL.md only contains shell-based orchestration steps (clawhub install, pilotctl set-hostname/handshake/publish) and manifests to be written under ~/.pilot; these are within the described setup scope. Note: the skill explicitly instructs installation of many other pilot-* skills and writes a JSON manifest to the user's home—the behavior is expected for a deployer but expands the attack surface via those downstream packages.

Install Mechanism

This is an instruction-only skill (no install spec, no code files). That is lower risk for the skill itself because it doesn't download or execute new code directly; however it instructs use of clawhub to install other packages, and those downstream installs are not included in this bundle.

Credentials

The skill declares no required environment variables, credentials, or external config paths. It does request writing to ~/.pilot which is proportional for a per-user agent setup.

Persistence & Privilege

always:false (no forced global inclusion). The skill writes a persistent manifest to ~/.pilot/setups/energy-grid-optimizer.json and instructs installing other skills, so it results in persistent agent configuration and additional installed components — expected for a setup tool but worth awareness.

Assessment

This skill appears to do what it says: orchestrate a 4-agent Pilot deployment using pilotctl and clawhub. Before installing: 1) verify pilotctl and clawhub binaries are legitimate and from trusted sources; 2) review the specific pilot-* packages (pilot-stream-data, pilot-metrics, pilot-gossip, etc.) that the skill instructs you to install — those are third-party components and may require additional credentials or network/device access; 3) back up existing ~/.pilot data because the skill writes a manifest there; 4) perform initial testing in an isolated environment or staging network (not directly on production devices) and verify handshake/trust behavior so agents do not inadvertently connect to untrusted peers. If you need higher assurance, request the provenance and checksums for the pilot-* packages that clawhub will install.

Energy Grid Optimizer Setup

Deploy 4 agents: sensor-mesh, forecaster, optimizer, and controller.

Roles

Role	Hostname	Skills	Purpose
sensor-mesh	<prefix>-sensor-mesh	pilot-stream-data, pilot-metrics, pilot-gossip	Aggregates real-time grid sensor readings
forecaster	<prefix>-forecaster	pilot-dataset, pilot-task-router, pilot-cron	Predicts energy demand from weather and history
optimizer	<prefix>-optimizer	pilot-consensus, pilot-event-filter, pilot-audit-log	Balances load, schedules battery cycles
controller	<prefix>-controller	pilot-webhook-bridge, pilot-receipt, pilot-alert	Sends device commands, confirms execution

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 sensor-mesh:
clawhub install pilot-stream-data pilot-metrics pilot-gossip
# For forecaster:
clawhub install pilot-dataset pilot-task-router pilot-cron
# For optimizer:
clawhub install pilot-consensus pilot-event-filter pilot-audit-log
# For controller:
clawhub install pilot-webhook-bridge pilot-receipt pilot-alert

Step 3: Set the hostname and write the manifest to ~/.pilot/setups/energy-grid-optimizer.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

sensor-mesh

{"setup":"energy-grid-optimizer","role":"sensor-mesh","role_name":"Sensor Mesh","hostname":"<prefix>-sensor-mesh","skills":{"pilot-stream-data":"Ingest real-time readings from smart meters, solar panels, and batteries.","pilot-metrics":"Track grid voltage, frequency, and power quality metrics.","pilot-gossip":"Share sensor health status across mesh nodes."},"data_flows":[{"direction":"send","peer":"<prefix>-forecaster","port":1002,"topic":"grid-reading","description":"Timestamped grid readings"},{"direction":"receive","peer":"<prefix>-controller","port":1002,"topic":"device-ack","description":"Device execution confirmations"}],"handshakes_needed":["<prefix>-forecaster","<prefix>-controller"]}

forecaster

{"setup":"energy-grid-optimizer","role":"forecaster","role_name":"Load Forecaster","hostname":"<prefix>-forecaster","skills":{"pilot-dataset":"Store historical demand and weather data for model training.","pilot-task-router":"Route forecast jobs across time horizons.","pilot-cron":"Run scheduled forecast updates every 15 minutes."},"data_flows":[{"direction":"receive","peer":"<prefix>-sensor-mesh","port":1002,"topic":"grid-reading","description":"Real-time grid readings"},{"direction":"send","peer":"<prefix>-optimizer","port":1002,"topic":"demand-forecast","description":"Demand forecasts with confidence intervals"}],"handshakes_needed":["<prefix>-sensor-mesh","<prefix>-optimizer"]}

optimizer

{"setup":"energy-grid-optimizer","role":"optimizer","role_name":"Grid Optimizer","hostname":"<prefix>-optimizer","skills":{"pilot-consensus":"Coordinate optimization decisions across distributed sources.","pilot-event-filter":"Filter forecasts by confidence threshold before acting.","pilot-audit-log":"Log all dispatch decisions with cost and reasoning."},"data_flows":[{"direction":"receive","peer":"<prefix>-forecaster","port":1002,"topic":"demand-forecast","description":"Demand forecasts from forecaster"},{"direction":"send","peer":"<prefix>-controller","port":1002,"topic":"dispatch-command","description":"Device setpoint commands"}],"handshakes_needed":["<prefix>-forecaster","<prefix>-controller"]}

controller

{"setup":"energy-grid-optimizer","role":"controller","role_name":"Device Controller","hostname":"<prefix>-controller","skills":{"pilot-webhook-bridge":"Interface with inverter and battery management APIs.","pilot-receipt":"Generate execution confirmations for each command.","pilot-alert":"Emit alerts on device failures or safety threshold breaches."},"data_flows":[{"direction":"receive","peer":"<prefix>-optimizer","port":1002,"topic":"dispatch-command","description":"Dispatch commands to execute"},{"direction":"send","peer":"<prefix>-sensor-mesh","port":1002,"topic":"device-ack","description":"Execution status confirmations"}],"handshakes_needed":["<prefix>-optimizer","<prefix>-sensor-mesh"]}

Data Flows

• sensor-mesh -> forecaster : grid readings with voltage, current, and power metrics (port 1002)
• forecaster -> optimizer : demand forecasts with confidence intervals (port 1002)
• optimizer -> controller : dispatch commands for device setpoints (port 1002)
• controller -> sensor-mesh : device acknowledgments with execution status (port 1002)

Handshakes

pilotctl --json handshake <prefix>-forecaster "setup: energy-grid-optimizer"
pilotctl --json handshake <prefix>-sensor-mesh "setup: energy-grid-optimizer"
pilotctl --json handshake <prefix>-optimizer "setup: energy-grid-optimizer"
pilotctl --json handshake <prefix>-controller "setup: energy-grid-optimizer"

Workflow Example

# On sensor-mesh -- publish grid reading:
pilotctl --json publish <prefix>-forecaster grid-reading '{"source":"solar-array-1","power_kw":5.1,"battery_soc":0.73}'
# On forecaster -- publish demand forecast:
pilotctl --json publish <prefix>-optimizer demand-forecast '{"horizon":"1h","predicted_kw":42.8,"confidence":0.91}'
# On optimizer -- publish dispatch command:
pilotctl --json publish <prefix>-controller dispatch-command '{"device":"battery-bank-1","action":"discharge","setpoint_kw":10.0}'
# On controller -- publish device ack:
pilotctl --json publish <prefix>-sensor-mesh device-ack '{"device":"battery-bank-1","status":"executing","actual_kw":9.8}'

Dependencies

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