Pilot Autonomous Warehouse Setup
/install pilot-autonomous-warehouse-setup
Autonomous Warehouse Setup
Deploy 4 agents: fleet-controller, inventory-brain, pick-optimizer, and dock-manager.
Roles
| Role | Hostname | Skills | Purpose |
|---|---|---|---|
| fleet-controller | \x3Cprefix>-fleet-controller |
pilot-task-router, pilot-load-balancer, pilot-cron | Manages robot fleet, assigns tasks, optimizes routes |
| inventory-brain | \x3Cprefix>-inventory-brain |
pilot-dataset, pilot-metrics, pilot-consensus | Tracks bin locations, triggers replenishment |
| pick-optimizer | \x3Cprefix>-pick-optimizer |
pilot-task-parallel, pilot-event-filter, pilot-escrow | Batches orders into optimal pick waves |
| dock-manager | \x3Cprefix>-dock-manager |
pilot-webhook-bridge, pilot-receipt, pilot-audit-log | Coordinates inbound/outbound shipments |
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 fleet-controller:
clawhub install pilot-task-router pilot-load-balancer pilot-cron
# For inventory-brain:
clawhub install pilot-dataset pilot-metrics pilot-consensus
# For pick-optimizer:
clawhub install pilot-task-parallel pilot-event-filter pilot-escrow
# For dock-manager:
clawhub install pilot-webhook-bridge pilot-receipt pilot-audit-log
Step 3: Set the hostname and write the manifest to ~/.pilot/setups/autonomous-warehouse.json.
Step 4: Tell the user to initiate handshakes with the peers for their role.
Manifest Templates Per Role
fleet-controller
{
"setup": "autonomous-warehouse", "role": "fleet-controller", "role_name": "Robot Fleet Controller",
"hostname": "\x3Cprefix>-fleet-controller",
"skills": {
"pilot-task-router": "Assign pick tasks to available robots.",
"pilot-load-balancer": "Distribute workload across robot fleet.",
"pilot-cron": "Schedule charging cycles and maintenance windows."
},
"data_flows": [
{ "direction": "send", "peer": "\x3Cprefix>-inventory-brain", "port": 1002, "topic": "robot-status", "description": "Robot status and completed task reports" },
{ "direction": "receive", "peer": "\x3Cprefix>-pick-optimizer", "port": 1002, "topic": "pick-assignment", "description": "Pick wave assignments for dispatch" }
],
"handshakes_needed": ["\x3Cprefix>-inventory-brain", "\x3Cprefix>-pick-optimizer"]
}
inventory-brain
{
"setup": "autonomous-warehouse", "role": "inventory-brain", "role_name": "Inventory Brain",
"hostname": "\x3Cprefix>-inventory-brain",
"skills": {
"pilot-dataset": "Maintain real-time bin locations and SKU counts.",
"pilot-metrics": "Track stock levels, pick rates, and replenishment velocity.",
"pilot-consensus": "Reconcile inventory counts across zone scanners."
},
"data_flows": [
{ "direction": "receive", "peer": "\x3Cprefix>-fleet-controller", "port": 1002, "topic": "robot-status", "description": "Robot status updates" },
{ "direction": "send", "peer": "\x3Cprefix>-pick-optimizer", "port": 1002, "topic": "pick-request", "description": "Pick requests with bin locations" },
{ "direction": "receive", "peer": "\x3Cprefix>-dock-manager", "port": 1002, "topic": "inbound-shipment", "description": "Inbound shipment data" }
],
"handshakes_needed": ["\x3Cprefix>-fleet-controller", "\x3Cprefix>-pick-optimizer", "\x3Cprefix>-dock-manager"]
}
pick-optimizer
{
"setup": "autonomous-warehouse", "role": "pick-optimizer", "role_name": "Pick Optimizer",
"hostname": "\x3Cprefix>-pick-optimizer",
"skills": {
"pilot-task-parallel": "Batch orders into parallel pick waves.",
"pilot-event-filter": "Prioritize same-day and rush orders.",
"pilot-escrow": "Hold payment escrow until order fulfillment confirmed."
},
"data_flows": [
{ "direction": "receive", "peer": "\x3Cprefix>-inventory-brain", "port": 1002, "topic": "pick-request", "description": "Pick requests from inventory" },
{ "direction": "send", "peer": "\x3Cprefix>-fleet-controller", "port": 1002, "topic": "pick-assignment", "description": "Optimized pick assignments" },
{ "direction": "send", "peer": "\x3Cprefix>-dock-manager", "port": 1002, "topic": "outbound-ready", "description": "Orders ready for shipping" }
],
"handshakes_needed": ["\x3Cprefix>-inventory-brain", "\x3Cprefix>-fleet-controller", "\x3Cprefix>-dock-manager"]
}
dock-manager
{
"setup": "autonomous-warehouse", "role": "dock-manager", "role_name": "Dock Manager",
"hostname": "\x3Cprefix>-dock-manager",
"skills": {
"pilot-webhook-bridge": "Notify carriers of shipment readiness.",
"pilot-receipt": "Generate receiving and shipping receipts.",
"pilot-audit-log": "Log all dock door assignments and truck movements."
},
"data_flows": [
{ "direction": "send", "peer": "\x3Cprefix>-inventory-brain", "port": 1002, "topic": "inbound-shipment", "description": "Inbound shipment receiving data" },
{ "direction": "receive", "peer": "\x3Cprefix>-pick-optimizer", "port": 1002, "topic": "outbound-ready", "description": "Orders ready for outbound" }
],
"handshakes_needed": ["\x3Cprefix>-inventory-brain", "\x3Cprefix>-pick-optimizer"]
}
Data Flows
fleet-controller -> inventory-brain: robot status and completed task reports (port 1002)inventory-brain -> pick-optimizer: pick requests with bin locations (port 1002)pick-optimizer -> fleet-controller: optimized pick assignments (port 1002)dock-manager -> inventory-brain: inbound shipment receiving data (port 1002)pick-optimizer -> dock-manager: orders ready for outbound shipping (port 1002)
Workflow Example
# On fleet-controller -- report robot status:
pilotctl --json publish \x3Cprefix>-inventory-brain robot-status '{"robot_id":"AMR-07","zone":"A3","battery":72,"status":"idle"}'
# On inventory-brain -- send pick request:
pilotctl --json publish \x3Cprefix>-pick-optimizer pick-request '{"order_id":"ORD-88412","items":[{"sku":"WH-4410","bin":"A3-07-02","qty":2}]}'
# On pick-optimizer -- assign to fleet:
pilotctl --json publish \x3Cprefix>-fleet-controller pick-assignment '{"wave_id":"WAVE-334","robot_id":"AMR-07","stops":["A3-07-02","A3-00-PACK"]}'
# On dock-manager -- notify inbound:
pilotctl --json publish \x3Cprefix>-inventory-brain inbound-shipment '{"shipment_id":"SHP-10042","dock_door":3,"pallets":12}'
# On pick-optimizer -- outbound ready:
pilotctl --json publish \x3Cprefix>-dock-manager outbound-ready '{"wave_id":"WAVE-334","orders":["ORD-88412"]}'
Dependencies
Requires pilot-protocol skill, pilotctl binary, clawhub binary, and a running daemon.
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install pilot-autonomous-warehouse-setup - After installation, invoke the skill by name or use
/pilot-autonomous-warehouse-setup - Provide required inputs per the skill's parameter spec and get structured output
What is Pilot Autonomous Warehouse Setup?
Deploy an autonomous warehouse orchestration system with 4 agents. Use this skill when: 1. User wants to set up warehouse automation with robot fleet coordin... It is an AI Agent Skill for Claude Code / OpenClaw, with 73 downloads so far.
How do I install Pilot Autonomous Warehouse Setup?
Run "/install pilot-autonomous-warehouse-setup" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Pilot Autonomous Warehouse Setup free?
Yes, Pilot Autonomous Warehouse Setup is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Pilot Autonomous Warehouse Setup support?
Pilot Autonomous Warehouse Setup is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Pilot Autonomous Warehouse Setup?
It is built and maintained by Calin Teodor (@teoslayer); the current version is v1.0.0.