Org Zoo

Ad Campaign Manager

Deploy an ad campaign management system with 4 agents that automate campaign strategy, creative prod

intermediate 4 agents

Agent Marketplace

A decentralized marketplace where agents advertise their capabilities, a matchmaker pairs requesters

advanced 4 agents

AI Tutoring System

An adaptive tutoring pipeline where a content curator organizes learning materials, a tutor delivers

intermediate 3 agents

API Gateway Manager

Deploy an API gateway management system with 4 agents that handle service discovery, request routing

intermediate 4 agents

Autonomous Warehouse

An autonomous warehouse orchestration system that coordinates robot fleets, tracks inventory in real

advanced 4 agents

Backup & Disaster Recovery

Automated backup infrastructure across multiple sites.

intermediate 4 agents

Brand Protection

Deploy a brand protection system with 4 agents that monitor for unauthorized brand usage, classify t

intermediate 4 agents

Chat & Collaboration Hub

A self-hosted collaboration platform for agent teams.

intermediate 4 agents

CI/CD Pipeline

A fully decentralized CI/CD pipeline where each stage runs on a separate agent.

intermediate 3 agents

Cloud Cost Optimizer

A distributed FinOps pipeline that continuously scans cloud environments for waste, analyzes spendin

intermediate 4 agents

Code Review Pipeline

Deploy an automated code review pipeline with 3 agents that scan pull requests for issues, analyze c

beginner 3 agents

Competitor Intelligence

Deploy a multi-agent competitive intelligence system that crawls competitor websites, analyzes marke

intermediate 4 agents

Compliance & Governance

Automated compliance for regulated environments.

advanced 4 agents

Content Marketing Pipeline

Deploy a content production pipeline where a researcher gathers trending topics and source material,

beginner 3 agents

Customer Onboarding

Deploy a customer onboarding system with 3 agents that automate the new customer journey from welcom

intermediate 3 agents

Customer Support Triage

Deploy a support ticket triage system where incoming tickets are classified by urgency and category,

beginner 3 agents

Data Labeling Pipeline

Deploy a distributed data labeling pipeline with 4 agents that ingests raw data, applies ML-based la

advanced 4 agents

Dev Team Assistants

A team of four agents that automate the PR workflow.

intermediate 4 agents

Digital Twin

A digital twin platform that mirrors physical assets in real time, predicts failures before they occ

advanced 4 agents

Disaster Response

A multi-agent emergency management system that coordinates sensor aggregation, disaster assessment,

advanced 4 agents

Document Processing

Deploy a document processing pipeline with 3 agents that automate document ingestion, structured dat

beginner 3 agents

E-Commerce Ops

Deploy a multi-agent e-commerce operations system that manages product catalogs, processes orders, t

intermediate 4 agents

Energy Grid Optimizer

A multi-agent energy management system that coordinates real-time sensor aggregation, demand forecas

advanced 4 agents

ETL Data Pipeline

A five-stage ETL pipeline for production data processing.

advanced 5 agents

Expense Tracker

Deploy an expense tracking pipeline with 3 agents that automate receipt collection, expense categori

beginner 3 agents

Feedback Collector

Deploy a feedback collection pipeline with 3 agents that automate feedback intake, sentiment analysi

beginner 3 agents

Financial Trading Desk

A multi-agent trading desk that coordinates market analysis, sentiment scanning, risk management, an

advanced 4 agents

Fleet Health Monitor

Deploy monitoring agents across your fleet that continuously check service health, aggregate metrics

beginner 3 agents

Fraud Detection Pipeline

A real-time fraud detection pipeline that processes transaction streams through four escalation stag

advanced 4 agents

Game NPC Network

A living village powered by four AI agents that act as non-player characters.

advanced 4 agents

Healthcare Triage

Deploy a healthcare triage system with 4 agents that collects patient symptoms, performs differentia

advanced 4 agents

Incident Response

A four-stage incident response pipeline.

advanced 4 agents

Inventory Management

Deploy an inventory management system where a tracker monitors warehouse stock levels and shipments,

beginner 3 agents

Knowledge Base (RAG)

A retrieval-augmented generation pipeline.

intermediate 4 agents

Legal Contract Review

An automated contract review pipeline that extracts key terms from uploaded documents, assesses risk

intermediate 3 agents

Log Analytics

Deploy a log analytics system with 4 agents that collect, parse, alert on, and visualize log data.

intermediate 4 agents

MCP Bridge Fleet

Bridge different agent ecosystems over Pilot tunnels.

beginner 3 agents

Media Monitoring

A multi-agent media intelligence platform that coordinates web crawling, sentiment analysis, trend d

advanced 4 agents

Meeting Assistant

Deploy a meeting assistant system where a scheduler manages calendar availability and sends invites,

beginner 3 agents

ML Training Pipeline

An end-to-end machine learning pipeline spanning four agents.

advanced 4 agents

Multi-Region Content Sync

Distribute content from a central origin to edge nodes across multiple regions.

intermediate 4 agents

Newsletter Automation

Deploy an automated newsletter pipeline with 3 agents that curate trending content, transform it int

beginner 3 agents

Penetration Testing

Deploy an automated penetration testing pipeline with 4 agents that perform reconnaissance, scan for

advanced 4 agents

Podcast Production

Deploy a podcast production pipeline where a researcher finds trending topics and guest suggestions,

beginner 3 agents

Proposal Writer

Deploy a multi-agent proposal writing system with 3 agents that research RFP requirements and compet

intermediate 3 agents

Quality Assurance Pipeline

Deploy a quality assurance pipeline with 3 agents that automate test generation, execution, and repo

intermediate 3 agents

Real Estate Analyzer

Deploy a real estate analysis system with 4 agents that monitors property listings, calculates valua

advanced 4 agents

Recruitment Pipeline

Deploy a multi-agent recruitment pipeline that automates candidate sourcing, resume screening, and i

intermediate 3 agents

Release Management

Deploy an automated release pipeline with 3 agents that generate changelogs from merged PRs, manage

beginner 3 agents

Sales Pipeline

Deploy a sales pipeline with 4 agents that automate lead generation, qualification, personalized out

intermediate 4 agents

Scientific Research Team

A collaborative research pipeline that automates the scientific method across four specialized agent

advanced 4 agents

Security Operations Center

A SOC pipeline that collects security events, analyzes patterns, replays incidents for forensics, an

advanced 4 agents

Smart Home Coordinator

A decentralized smart home system where sensors, a central brain, device actuators, and a dashboard

intermediate 4 agents

Social Media Manager

Deploy a social media management system where a planner analyzes trends and audience data to build a

beginner 3 agents

Status Page

Deploy a status page pipeline with 3 agents that automate service monitoring, status aggregation, an

beginner 3 agents

Supply Chain Orchestrator

An end-to-end supply chain orchestration pipeline coordinating inventory management, logistics routi

advanced 4 agents

Swarm Task Farm

A self-organizing compute swarm.

advanced 5 agents

Threat Intelligence

A threat intelligence platform that aggregates indicators of compromise from multiple sources, enric

advanced 4 agents

Translation Pipeline

Deploy an automated translation pipeline with 3 agents that extract content from sources, translate

beginner 3 agents

Video Production Pipeline

Deploy a video production pipeline with 3 agents that automate script writing, video editing coordin

intermediate 3 agents

Ad Campaign Manager

intermediate 4 agents · 12 skills

Deploy an ad campaign management system with 4 agents that automate campaign strategy, creative production, real-time bidding, and performance analytics. A strategist defines audiences and budgets, a creative producer generates ad variations, a bid manager optimizes spend across channels, and a performance analyst tracks conversions and ROAS. The feedback loop from analyst back to strategist enables continuous campaign optimization.

pilot-task-router pilot-dataset pilot-cron pilot-share pilot-task-parallel pilot-receipt pilot-metrics pilot-stream-data pilot-escrow pilot-event-filter pilot-slack-bridge pilot-webhook-bridge

clawhub install pilot-ad-campaign-manager-setup

ClawHub Source

Agents 4

<your-prefix>-strategist Campaign Strategist

Defines audiences, budgets, channel mix, and KPIs

pilot-task-router pilot-dataset pilot-cron

clawhub install pilot-task-router pilot-dataset pilot-cron

pilotctl set-hostname <your-prefix>-strategist

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-creative "setup: ad-campaign-manager"

pilotctl handshake <your-prefix>-analyst "setup: ad-campaign-manager"

<your-prefix>-creative Creative Producer

Generates ad copy, headlines, and A/B test variations

pilot-share pilot-task-parallel pilot-receipt

clawhub install pilot-share pilot-task-parallel pilot-receipt

pilotctl set-hostname <your-prefix>-creative

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-strategist "setup: ad-campaign-manager"

pilotctl handshake <your-prefix>-bidder "setup: ad-campaign-manager"

<your-prefix>-bidder Bid Manager

Manages real-time bidding and spend optimization

pilot-metrics pilot-stream-data pilot-escrow

clawhub install pilot-metrics pilot-stream-data pilot-escrow

pilotctl set-hostname <your-prefix>-bidder

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-creative "setup: ad-campaign-manager"

pilotctl handshake <your-prefix>-analyst "setup: ad-campaign-manager"

<your-prefix>-analyst Performance Analyst

Tracks conversions, ROAS, CTR; feeds insights back to strategist

pilot-event-filter pilot-slack-bridge pilot-webhook-bridge

clawhub install pilot-event-filter pilot-slack-bridge pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-analyst

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-bidder "setup: ad-campaign-manager"

pilotctl handshake <your-prefix>-strategist "setup: ad-campaign-manager"

Data Flows

<your-prefix>-strategist → <your-prefix>-creative campaign-brief :1002

<your-prefix>-creative → <your-prefix>-bidder creative-asset :1002

<your-prefix>-bidder → <your-prefix>-analyst bid-result :1002

<your-prefix>-analyst → <your-prefix>-strategist performance-insight :1002

<your-prefix>-analyst → external campaign-report via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-creative -- subscribe to campaign briefs:

pilotctl subscribe <your-prefix>-strategist campaign-brief

# On <your-prefix>-strategist -- publish a campaign brief:

pilotctl publish <your-prefix>-creative campaign-brief '{"campaign":"Summer Sale 2026","audience":{"age":"25-45","interests":["outdoor","fitness"]},"budget":15000,"channels":["google","meta","tiktok"],"kpis":{"target_roas":3.5,"target_ctr":0.02}}'

# On <your-prefix>-bidder -- subscribe to creative assets:

pilotctl subscribe <your-prefix>-creative creative-asset

# On <your-prefix>-creative -- publish a creative asset:

pilotctl publish <your-prefix>-bidder creative-asset '{"campaign":"Summer Sale 2026","variant":"A","headline":"Get Fit This Summer - 40% Off","format":"carousel","channels":["meta","tiktok"],"cta":"Shop Now"}'

# On <your-prefix>-analyst -- subscribe to bid results:

pilotctl subscribe <your-prefix>-bidder bid-result

# On <your-prefix>-bidder -- publish a bid result:

pilotctl publish <your-prefix>-analyst bid-result '{"campaign":"Summer Sale 2026","channel":"meta","spend":2450.00,"impressions":185000,"clicks":4100,"conversions":82,"cpc":0.60}'

# On <your-prefix>-strategist -- subscribe to performance insights:

pilotctl subscribe <your-prefix>-analyst performance-insight

# On <your-prefix>-analyst -- publish a performance insight:

pilotctl publish <your-prefix>-strategist performance-insight '{"campaign":"Summer Sale 2026","roas":4.1,"ctr":0.022,"top_channel":"meta","recommendation":"Shift 20% budget from google to tiktok based on CPA trend"}'

# On <your-prefix>-analyst -- publish external campaign report:

pilotctl publish <your-prefix>-analyst campaign-report '{"campaign":"Summer Sale 2026","period":"week_2","total_spend":8200,"total_conversions":310,"roas":3.8,"status":"on_track"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (campaign strategist)

clawhub install pilot-task-router pilot-dataset pilot-cron

pilotctl set-hostname <your-prefix>-strategist

# On server 2 (creative producer)

clawhub install pilot-share pilot-task-parallel pilot-receipt

pilotctl set-hostname <your-prefix>-creative

# On server 3 (bid manager)

clawhub install pilot-metrics pilot-stream-data pilot-escrow

pilotctl set-hostname <your-prefix>-bidder

# On server 4 (performance analyst)

clawhub install pilot-event-filter pilot-slack-bridge pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-analyst

# strategist <-> creative

# On strategist:

pilotctl handshake <your-prefix>-creative "setup: ad-campaign-manager"

# On creative:

pilotctl handshake <your-prefix>-strategist "setup: ad-campaign-manager"

# creative <-> bidder

# On creative:

pilotctl handshake <your-prefix>-bidder "setup: ad-campaign-manager"

# On bidder:

pilotctl handshake <your-prefix>-creative "setup: ad-campaign-manager"

# bidder <-> analyst

# On bidder:

pilotctl handshake <your-prefix>-analyst "setup: ad-campaign-manager"

# On analyst:

pilotctl handshake <your-prefix>-bidder "setup: ad-campaign-manager"

# analyst <-> strategist (feedback loop)

# On analyst:

pilotctl handshake <your-prefix>-strategist "setup: ad-campaign-manager"

# On strategist:

pilotctl handshake <your-prefix>-analyst "setup: ad-campaign-manager"

pilotctl trust

Agent Marketplace

advanced 4 agents · 15 skills

A decentralized marketplace where agents advertise their capabilities, a matchmaker pairs requesters with providers, and transactions are settled through escrow. Reputation scores ensure quality. No central platform takes a cut.

pilot-directory pilot-announce-capabilities pilot-discover pilot-reputation pilot-matchmaker pilot-auction pilot-priority-queue pilot-audit-log pilot-escrow pilot-receipt pilot-webhook-bridge pilot-api-gateway pilot-health pilot-load-balancer pilot-metrics

clawhub install pilot-agent-marketplace-setup

ClawHub Source

Agents 4

<your-prefix>-directory Capability Directory

Capability registry

pilot-directory pilot-announce-capabilities pilot-discover pilot-reputation

clawhub install pilot-directory pilot-announce-capabilities pilot-discover pilot-reputation

pilotctl set-hostname <your-prefix>-directory

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-matchmaker "setup: agent-marketplace"

pilotctl handshake <your-prefix>-escrow "setup: agent-marketplace"

pilotctl handshake <your-prefix>-gateway "setup: agent-marketplace"

<your-prefix>-matchmaker Request Matchmaker

Matches requests to providers

pilot-matchmaker pilot-auction pilot-priority-queue pilot-audit-log

clawhub install pilot-matchmaker pilot-auction pilot-priority-queue pilot-audit-log

pilotctl set-hostname <your-prefix>-matchmaker

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-directory "setup: agent-marketplace"

pilotctl handshake <your-prefix>-escrow "setup: agent-marketplace"

pilotctl handshake <your-prefix>-gateway "setup: agent-marketplace"

<your-prefix>-escrow Transaction Escrow

Transaction settlement

pilot-escrow pilot-receipt pilot-audit-log pilot-webhook-bridge

clawhub install pilot-escrow pilot-receipt pilot-audit-log pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-escrow

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-matchmaker "setup: agent-marketplace"

pilotctl handshake <your-prefix>-directory "setup: agent-marketplace"

<your-prefix>-gateway Marketplace Gateway

Public API entry point

pilot-api-gateway pilot-health pilot-load-balancer pilot-metrics

clawhub install pilot-api-gateway pilot-health pilot-load-balancer pilot-metrics

pilotctl set-hostname <your-prefix>-gateway

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-directory "setup: agent-marketplace"

pilotctl handshake <your-prefix>-matchmaker "setup: agent-marketplace"

Data Flows

<your-prefix>-gateway → <your-prefix>-matchmaker incoming task requests :1002

<your-prefix>-matchmaker → <your-prefix>-directory capability queries :1002

<your-prefix>-matchmaker → <your-prefix>-escrow escrow initiation :1002

<your-prefix>-escrow → <your-prefix>-directory reputation updates :1002

<your-prefix>-gateway → <your-prefix>-directory discovery queries :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-gateway — submit a capability request:

pilotctl publish <your-prefix>-matchmaker capability-request '{"requester":"client-a","need":"image-classification","budget":50}'

# On <your-prefix>-matchmaker — query directory and find match:

pilotctl publish <your-prefix>-directory discover-capability '{"capability":"image-classification","min_reputation":4.0}'

# On <your-prefix>-directory — return matching providers:

pilotctl publish <your-prefix>-matchmaker capability-match '{"providers":[{"agent":"img-classifier-1","reputation":4.8,"price":30}]}'

# On <your-prefix>-matchmaker — initiate escrow:

pilotctl publish <your-prefix>-escrow escrow-create '{"requester":"client-a","provider":"img-classifier-1","amount":30,"task":"image-classification"}'

# On <your-prefix>-escrow — settle and update reputation:

pilotctl publish <your-prefix>-directory reputation-update '{"agent":"img-classifier-1","rating":5,"transaction":"TXN-2891"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On directory node

clawhub install pilot-directory pilot-announce-capabilities pilot-discover pilot-reputation

pilotctl set-hostname <your-prefix>-directory

# On matchmaker node

clawhub install pilot-matchmaker pilot-auction pilot-priority-queue pilot-audit-log

pilotctl set-hostname <your-prefix>-matchmaker

# On escrow node

clawhub install pilot-escrow pilot-receipt pilot-audit-log pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-escrow

# On gateway node

clawhub install pilot-api-gateway pilot-health pilot-load-balancer pilot-metrics

pilotctl set-hostname <your-prefix>-gateway

# gateway <-> matchmaker

# On gateway:

pilotctl handshake <your-prefix>-matchmaker "marketplace"

# On matchmaker:

pilotctl handshake <your-prefix>-gateway "marketplace"

# matchmaker <-> directory

# On matchmaker:

pilotctl handshake <your-prefix>-directory "marketplace"

# On directory:

pilotctl handshake <your-prefix>-matchmaker "marketplace"

# matchmaker <-> escrow

# On matchmaker:

pilotctl handshake <your-prefix>-escrow "marketplace"

# On escrow:

pilotctl handshake <your-prefix>-matchmaker "marketplace"

# escrow <-> directory

# On escrow:

pilotctl handshake <your-prefix>-directory "marketplace"

# On directory:

pilotctl handshake <your-prefix>-escrow "marketplace"

# gateway <-> directory

# On gateway:

pilotctl handshake <your-prefix>-directory "marketplace"

# On directory:

pilotctl handshake <your-prefix>-gateway "marketplace"

pilotctl trust

AI Tutoring System

intermediate 3 agents · 9 skills

An adaptive tutoring pipeline where a content curator organizes learning materials, a tutor delivers personalized lessons, and an assessment agent evaluates understanding. The three agents form a feedback loop -- gap analysis from assessments feeds back to the curator so the curriculum adapts to each learner in real time.

pilot-archive pilot-discover pilot-dataset pilot-chat pilot-task-router pilot-receipt pilot-metrics pilot-alert pilot-audit-log

clawhub install pilot-ai-tutoring-system-setup

ClawHub Source

Agents 3

<your-prefix>-content-curator Content Curator

Organizes learning materials by topic and difficulty, adapts curriculum from gap analysis.

pilot-archive pilot-discover pilot-dataset

clawhub install pilot-archive pilot-discover pilot-dataset

pilotctl set-hostname <your-prefix>-content-curator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-tutor "setup: ai-tutoring-system"

pilotctl handshake <your-prefix>-assessor "setup: ai-tutoring-system"

<your-prefix>-tutor Tutor Agent

Delivers personalized lessons, answers questions, tracks learner progress.

pilot-chat pilot-task-router pilot-receipt

clawhub install pilot-chat pilot-task-router pilot-receipt

pilotctl set-hostname <your-prefix>-tutor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-content-curator "setup: ai-tutoring-system"

pilotctl handshake <your-prefix>-assessor "setup: ai-tutoring-system"

<your-prefix>-assessor Assessment Agent

Creates quizzes, grades submissions, identifies knowledge gaps.

pilot-metrics pilot-alert pilot-audit-log

clawhub install pilot-metrics pilot-alert pilot-audit-log

pilotctl set-hostname <your-prefix>-assessor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-tutor "setup: ai-tutoring-system"

pilotctl handshake <your-prefix>-content-curator "setup: ai-tutoring-system"

Data Flows

<your-prefix>-content-curator → <your-prefix>-tutor lesson materials and curriculum :1002

<your-prefix>-tutor → <your-prefix>-assessor learner responses and progress :1002

<your-prefix>-assessor → <your-prefix>-content-curator gap analysis and adaptation signals :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-content-curator -- publish lesson material:

pilotctl publish <your-prefix>-tutor lesson-material '{"learner_id":"student-042","topic":"linear-algebra","difficulty":"intermediate","lesson":"matrices-intro","prerequisites_met":true,"content_url":"/lessons/matrices-intro.md"}'

# On <your-prefix>-tutor -- publish learner response:

pilotctl publish <your-prefix>-assessor learner-response '{"learner_id":"student-042","topic":"linear-algebra","lesson":"matrices-intro","answers":[{"q":"determinant_2x2","answer":"ad-bc","correct":true},{"q":"inverse_exists","answer":"det!=0","correct":true},{"q":"eigenvalue_def","answer":"unsure","correct":false}],"time_spent_sec":840}'

# On <your-prefix>-assessor -- publish gap analysis:

pilotctl publish <your-prefix>-content-curator gap-analysis '{"learner_id":"student-042","topic":"linear-algebra","mastery":0.67,"gaps":["eigenvalues","eigenvectors"],"recommendation":"introduce_eigenvalue_basics","confidence":0.85}'

# On <your-prefix>-content-curator -- subscribe to gap analysis:

pilotctl subscribe gap-analysis

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (content curator)

clawhub install pilot-archive pilot-discover pilot-dataset

pilotctl set-hostname <your-prefix>-content-curator

# On server 2 (tutor agent)

clawhub install pilot-chat pilot-task-router pilot-receipt

pilotctl set-hostname <your-prefix>-tutor

# On server 3 (assessment agent)

clawhub install pilot-metrics pilot-alert pilot-audit-log

pilotctl set-hostname <your-prefix>-assessor

# content-curator <-> tutor (lesson delivery)

# On content-curator:

pilotctl handshake <your-prefix>-tutor "setup: ai-tutoring-system"

# On tutor:

pilotctl handshake <your-prefix>-content-curator "setup: ai-tutoring-system"

# tutor <-> assessor (learner responses)

# On tutor:

pilotctl handshake <your-prefix>-assessor "setup: ai-tutoring-system"

# On assessor:

pilotctl handshake <your-prefix>-tutor "setup: ai-tutoring-system"

# assessor <-> content-curator (gap analysis feedback loop)

# On assessor:

pilotctl handshake <your-prefix>-content-curator "setup: ai-tutoring-system"

# On content-curator:

pilotctl handshake <your-prefix>-assessor "setup: ai-tutoring-system"

pilotctl trust

API Gateway Manager

intermediate 4 agents · 11 skills

Deploy an API gateway management system with 4 agents that handle service discovery, request routing, authentication, and monitoring. A discovery agent registers backend microservices and tracks their health, a router distributes incoming requests based on path and load, an auth gateway validates credentials and enforces rate limits, and a monitor tracks latency and error rates while alerting on anomalies. The feedback loop from monitor to discovery enables automatic removal of unhealthy backends.

pilot-discover pilot-health pilot-heartbeat-monitor pilot-load-balancer pilot-task-router pilot-metrics pilot-verify pilot-audit-log pilot-blocklist pilot-alert pilot-slack-bridge

clawhub install pilot-api-gateway-manager-setup

ClawHub Source

Agents 4

<your-prefix>-discovery Service Discovery

Registers and discovers backend microservices, maintains service registry, runs health checks.

pilot-discover pilot-health pilot-heartbeat-monitor

clawhub install pilot-discover pilot-health pilot-heartbeat-monitor

pilotctl set-hostname <your-prefix>-discovery

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-router "setup: api-gateway-manager"

pilotctl handshake <your-prefix>-monitor "setup: api-gateway-manager"

<your-prefix>-router Request Router

Routes incoming API requests to appropriate backends based on path, headers, and load.

pilot-load-balancer pilot-task-router pilot-metrics

clawhub install pilot-load-balancer pilot-task-router pilot-metrics

pilotctl set-hostname <your-prefix>-router

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-discovery "setup: api-gateway-manager"

pilotctl handshake <your-prefix>-auth "setup: api-gateway-manager"

<your-prefix>-auth Auth Gateway

Validates API keys and JWT tokens, enforces rate limits and quotas, blocks bad actors.

pilot-verify pilot-audit-log pilot-blocklist

clawhub install pilot-verify pilot-audit-log pilot-blocklist

pilotctl set-hostname <your-prefix>-auth

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-router "setup: api-gateway-manager"

pilotctl handshake <your-prefix>-monitor "setup: api-gateway-manager"

<your-prefix>-monitor API Monitor

Tracks latency, error rates, and throughput. Generates dashboards and alerts on anomalies.

pilot-metrics pilot-alert pilot-slack-bridge

clawhub install pilot-metrics pilot-alert pilot-slack-bridge

pilotctl set-hostname <your-prefix>-monitor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-auth "setup: api-gateway-manager"

pilotctl handshake <your-prefix>-discovery "setup: api-gateway-manager"

Data Flows

<your-prefix>-discovery → <your-prefix>-router service-registry updates with healthy backends :1002

<your-prefix>-router → <your-prefix>-auth auth-request for incoming API calls :1002

<your-prefix>-auth → <your-prefix>-monitor access-log with auth decisions and client metadata :1002

<your-prefix>-monitor → <your-prefix>-discovery health-feedback to deregister failing backends :1002

<your-prefix>-monitor → external api-alert via Slack and dashboards :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-router -- subscribe to service registry updates:

pilotctl subscribe <your-prefix>-discovery service-registry

# On <your-prefix>-discovery -- publish a service registration:

pilotctl publish <your-prefix>-router service-registry '{"service":"user-api","version":"2.1.0","instances":[{"host":"10.0.1.5","port":8080,"health":"passing"},{"host":"10.0.1.6","port":8080,"health":"passing"}],"routes":["/api/v2/users/*"]}'

# On <your-prefix>-auth -- subscribe to auth requests from router:

pilotctl subscribe <your-prefix>-router auth-request

# On <your-prefix>-router -- publish an auth request:

pilotctl publish <your-prefix>-auth auth-request '{"request_id":"req-88210","path":"/api/v2/users/profile","method":"GET","api_key":"key_example_4eC39HqLyjWDarjtT1zdp7dc","client_ip":"203.0.113.42","headers":{"Authorization":"Bearer eyJhbGciOiJSUzI1NiJ9..."}}'

# On <your-prefix>-monitor -- subscribe to access logs from auth:

pilotctl subscribe <your-prefix>-auth access-log

# On <your-prefix>-auth -- publish an access log:

pilotctl publish <your-prefix>-monitor access-log '{"request_id":"req-88210","client":"acme-corp","decision":"allow","latency_ms":12,"rate_limit_remaining":847,"quota_used_pct":15.3}'

# On <your-prefix>-discovery -- subscribe to health feedback from monitor:

pilotctl subscribe <your-prefix>-monitor health-feedback

# On <your-prefix>-monitor -- publish health feedback:

pilotctl publish <your-prefix>-discovery health-feedback '{"service":"user-api","instance":"10.0.1.6:8080","status":"failing","error_rate":0.42,"p99_latency_ms":2800,"recommendation":"deregister"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (service discovery)

clawhub install pilot-discover pilot-health pilot-heartbeat-monitor

pilotctl set-hostname <your-prefix>-discovery

# On server 2 (request router)

clawhub install pilot-load-balancer pilot-task-router pilot-metrics

pilotctl set-hostname <your-prefix>-router

# On server 3 (auth gateway)

clawhub install pilot-verify pilot-audit-log pilot-blocklist

pilotctl set-hostname <your-prefix>-auth

# On server 4 (API monitor)

clawhub install pilot-metrics pilot-alert pilot-slack-bridge

pilotctl set-hostname <your-prefix>-monitor

# discovery <-> router

# On discovery:

pilotctl handshake <your-prefix>-router "setup: api-gateway-manager"

# On router:

pilotctl handshake <your-prefix>-discovery "setup: api-gateway-manager"

# router <-> auth

# On router:

pilotctl handshake <your-prefix>-auth "setup: api-gateway-manager"

# On auth:

pilotctl handshake <your-prefix>-router "setup: api-gateway-manager"

# auth <-> monitor

# On auth:

pilotctl handshake <your-prefix>-monitor "setup: api-gateway-manager"

# On monitor:

pilotctl handshake <your-prefix>-auth "setup: api-gateway-manager"

# monitor <-> discovery (feedback loop)

# On monitor:

pilotctl handshake <your-prefix>-discovery "setup: api-gateway-manager"

# On discovery:

pilotctl handshake <your-prefix>-monitor "setup: api-gateway-manager"

pilotctl trust

Autonomous Warehouse

advanced 4 agents · 12 skills

An autonomous warehouse orchestration system that coordinates robot fleets, tracks inventory in real time, optimizes pick waves for order fulfillment, and manages dock scheduling for inbound and outbound shipments. The fleet controller dispatches robots, the inventory brain maintains bin-level location data, the pick optimizer batches orders into efficient waves, and the dock manager coordinates truck arrivals and departures.

pilot-task-router pilot-load-balancer pilot-cron pilot-dataset pilot-metrics pilot-consensus pilot-task-parallel pilot-event-filter pilot-escrow pilot-webhook-bridge pilot-receipt pilot-audit-log

clawhub install pilot-autonomous-warehouse-setup

ClawHub Source

Agents 4

<your-prefix>-fleet-controller Robot Fleet Controller

Robot status and completed task reports" },

pilot-task-router pilot-load-balancer pilot-cron

clawhub install pilot-task-router pilot-load-balancer pilot-cron

pilotctl set-hostname <your-prefix>-fleet-controller

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-inventory-brain "setup: autonomous-warehouse"

pilotctl handshake <your-prefix>-pick-optimizer "setup: autonomous-warehouse"

<your-prefix>-inventory-brain Inventory Brain

Robot status updates" },

pilot-dataset pilot-metrics pilot-consensus

clawhub install pilot-dataset pilot-metrics pilot-consensus

pilotctl set-hostname <your-prefix>-inventory-brain

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-fleet-controller "setup: autonomous-warehouse"

pilotctl handshake <your-prefix>-pick-optimizer "setup: autonomous-warehouse"

pilotctl handshake <your-prefix>-dock-manager "setup: autonomous-warehouse"

<your-prefix>-pick-optimizer Pick Optimizer

Pick requests from inventory" },

pilot-task-parallel pilot-event-filter pilot-escrow

clawhub install pilot-task-parallel pilot-event-filter pilot-escrow

pilotctl set-hostname <your-prefix>-pick-optimizer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-inventory-brain "setup: autonomous-warehouse"

pilotctl handshake <your-prefix>-fleet-controller "setup: autonomous-warehouse"

pilotctl handshake <your-prefix>-dock-manager "setup: autonomous-warehouse"

<your-prefix>-dock-manager Dock Manager

Inbound shipment receiving data" },

pilot-webhook-bridge pilot-receipt pilot-audit-log

clawhub install pilot-webhook-bridge pilot-receipt pilot-audit-log

pilotctl set-hostname <your-prefix>-dock-manager

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-inventory-brain "setup: autonomous-warehouse"

pilotctl handshake <your-prefix>-pick-optimizer "setup: autonomous-warehouse"

Data Flows

<your-prefix>-fleet-controller → <your-prefix>-inventory-brain robot status and completed task reports :1002

<your-prefix>-inventory-brain → <your-prefix>-pick-optimizer pick requests with bin locations :1002

<your-prefix>-pick-optimizer → <your-prefix>-fleet-controller optimized pick assignments :1002

<your-prefix>-dock-manager → <your-prefix>-inventory-brain inbound shipment receiving data :1002

<your-prefix>-pick-optimizer → <your-prefix>-dock-manager orders ready for outbound shipping :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-fleet-controller -- report robot status to inventory brain:

pilotctl publish <your-prefix>-inventory-brain robot-status '{"robot_id":"AMR-07","zone":"A3","battery":72,"status":"idle","last_task":"PICK-2291","completed_at":"2026-04-10T14:22:00Z"}'

# On <your-prefix>-inventory-brain -- send pick request to optimizer:

pilotctl publish <your-prefix>-pick-optimizer pick-request '{"order_id":"ORD-88412","items":[{"sku":"WH-4410","bin":"A3-07-02","qty":2},{"sku":"WH-1198","bin":"A3-12-01","qty":1}],"priority":"standard"}'

# On <your-prefix>-pick-optimizer -- assign pick wave to fleet:

pilotctl publish <your-prefix>-fleet-controller pick-assignment '{"wave_id":"WAVE-334","robot_id":"AMR-07","stops":["A3-07-02","A3-12-01","A3-00-PACK"],"estimated_time_sec":145}'

# On <your-prefix>-dock-manager -- notify inventory of inbound shipment:

pilotctl publish <your-prefix>-inventory-brain inbound-shipment '{"shipment_id":"SHP-10042","dock_door":3,"carrier":"FastFreight","pallets":12,"expected_skus":["WH-4410","WH-5521","WH-3390"]}'

# On <your-prefix>-pick-optimizer -- notify dock that outbound is ready:

pilotctl publish <your-prefix>-dock-manager outbound-ready '{"wave_id":"WAVE-334","orders":["ORD-88412","ORD-88415"],"packed_at":"2026-04-10T14:35:00Z","dock_door_requested":5}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On fleet controller node

clawhub install pilot-task-router pilot-load-balancer pilot-cron

pilotctl set-hostname <your-prefix>-fleet-controller

# On inventory brain node

clawhub install pilot-dataset pilot-metrics pilot-consensus

pilotctl set-hostname <your-prefix>-inventory-brain

# On pick optimizer node

clawhub install pilot-task-parallel pilot-event-filter pilot-escrow

pilotctl set-hostname <your-prefix>-pick-optimizer

# On dock manager node

clawhub install pilot-webhook-bridge pilot-receipt pilot-audit-log

pilotctl set-hostname <your-prefix>-dock-manager

# fleet-controller <-> inventory-brain (robot status)

# On fleet-controller:

pilotctl handshake <your-prefix>-inventory-brain "setup: autonomous-warehouse"

# On inventory-brain:

pilotctl handshake <your-prefix>-fleet-controller "setup: autonomous-warehouse"

# inventory-brain <-> pick-optimizer (pick requests)

# On inventory-brain:

pilotctl handshake <your-prefix>-pick-optimizer "setup: autonomous-warehouse"

# On pick-optimizer:

pilotctl handshake <your-prefix>-inventory-brain "setup: autonomous-warehouse"

# pick-optimizer <-> fleet-controller (pick assignments)

# On pick-optimizer:

pilotctl handshake <your-prefix>-fleet-controller "setup: autonomous-warehouse"

# On fleet-controller:

pilotctl handshake <your-prefix>-pick-optimizer "setup: autonomous-warehouse"

# dock-manager <-> inventory-brain (inbound shipments)

# On dock-manager:

pilotctl handshake <your-prefix>-inventory-brain "setup: autonomous-warehouse"

# On inventory-brain:

pilotctl handshake <your-prefix>-dock-manager "setup: autonomous-warehouse"

# pick-optimizer <-> dock-manager (outbound ready)

# On pick-optimizer:

pilotctl handshake <your-prefix>-dock-manager "setup: autonomous-warehouse"

# On dock-manager:

pilotctl handshake <your-prefix>-pick-optimizer "setup: autonomous-warehouse"

pilotctl trust

Backup & Disaster Recovery

intermediate 4 agents · 12 skills

Automated backup infrastructure across multiple sites. A scheduler triggers periodic backups, the primary backup agent compresses and archives data, a secondary site syncs copies for disaster recovery, and a tester periodically restores and verifies backup integrity.

pilot-cron pilot-task-chain pilot-audit-log pilot-slack-bridge pilot-backup pilot-archive pilot-compress pilot-share pilot-sync pilot-verify pilot-health pilot-alert

clawhub install pilot-backup-disaster-recovery-setup

ClawHub Source

Agents 4

<your-prefix>-scheduler Backup Scheduler

Trigger backup jobs" },

pilot-cron pilot-task-chain pilot-audit-log pilot-slack-bridge

clawhub install pilot-cron pilot-task-chain pilot-audit-log pilot-slack-bridge

pilotctl set-hostname <your-prefix>-scheduler

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-backup-primary "setup: backup-disaster-recovery"

pilotctl handshake <your-prefix>-backup-secondary "setup: backup-disaster-recovery"

pilotctl handshake <your-prefix>-restore-tester "setup: backup-disaster-recovery"

<your-prefix>-primary Primary Backup

Backup triggers" },

pilot-backup pilot-archive pilot-compress pilot-share

clawhub install pilot-backup pilot-archive pilot-compress pilot-share

pilotctl set-hostname <your-prefix>-primary

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-backup-sched "setup: backup-disaster-recovery"

pilotctl handshake <your-prefix>-backup-secondary "setup: backup-disaster-recovery"

<your-prefix>-secondary Offsite Replica

Compressed archives" },

pilot-sync pilot-verify pilot-health pilot-share

clawhub install pilot-sync pilot-verify pilot-health pilot-share

pilotctl set-hostname <your-prefix>-secondary

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-backup-primary "setup: backup-disaster-recovery"

pilotctl handshake <your-prefix>-backup-sched "setup: backup-disaster-recovery"

pilotctl handshake <your-prefix>-restore-tester "setup: backup-disaster-recovery"

<your-prefix>-tester Restore Tester

Backups to test" },

pilot-backup pilot-verify pilot-health pilot-alert

clawhub install pilot-backup pilot-verify pilot-health pilot-alert

pilotctl set-hostname <your-prefix>-tester

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-backup-secondary "setup: backup-disaster-recovery"

pilotctl handshake <your-prefix>-backup-sched "setup: backup-disaster-recovery"

Data Flows

<your-prefix>-scheduler → <your-prefix>-primary backup triggers :1002

<your-prefix>-primary → <your-prefix>-secondary compressed archives :1001

<your-prefix>-secondary → <your-prefix>-tester backups for testing :1001

<your-prefix>-tester → <your-prefix>-scheduler restore test results :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-backup-sched — trigger a scheduled backup:

pilotctl publish <your-prefix>-backup-primary backup-start '{"job_id":"BK-0315","type":"full","targets":["postgres","redis"]}'

# On <your-prefix>-backup-primary — create and ship backup:

pilotctl send-file <your-prefix>-backup-secondary ./backups/BK-0315-postgres.tar.gz

pilotctl send-file <your-prefix>-backup-secondary ./backups/BK-0315-redis.rdb

pilotctl publish <your-prefix>-backup-secondary sync-backup '{"job_id":"BK-0315","files":2,"size_mb":1240,"checksum":"sha256:d4e5f6"}'

# On <your-prefix>-backup-secondary — confirm sync:

pilotctl publish <your-prefix>-backup-sched sync-confirmed '{"job_id":"BK-0315","verified":true,"checksum_match":true}'

# On <your-prefix>-restore-tester — test restore and report:

pilotctl publish <your-prefix>-backup-sched restore-result '{"job_id":"BK-0315","restore":"success","tables_verified":42,"rows_checked":100000}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On scheduler node

clawhub install pilot-cron pilot-task-chain pilot-audit-log pilot-slack-bridge

pilotctl set-hostname <your-prefix>-backup-sched

# On primary backup server

clawhub install pilot-backup pilot-archive pilot-compress pilot-share

pilotctl set-hostname <your-prefix>-backup-primary

# On offsite secondary (different region/datacenter)

clawhub install pilot-sync pilot-verify pilot-health pilot-share

pilotctl set-hostname <your-prefix>-backup-secondary

# On restore test server

clawhub install pilot-backup pilot-verify pilot-health pilot-alert

pilotctl set-hostname <your-prefix>-restore-tester

# scheduler <-> primary

# On backup-sched:

pilotctl handshake <your-prefix>-backup-primary "backup dr"

# On backup-primary:

pilotctl handshake <your-prefix>-backup-sched "backup dr"

# primary <-> secondary

# On backup-primary:

pilotctl handshake <your-prefix>-backup-secondary "backup dr"

# On backup-secondary:

pilotctl handshake <your-prefix>-backup-primary "backup dr"

# secondary <-> tester

# On backup-secondary:

pilotctl handshake <your-prefix>-restore-tester "backup dr"

# On restore-tester:

pilotctl handshake <your-prefix>-backup-secondary "backup dr"

# tester <-> scheduler

# On restore-tester:

pilotctl handshake <your-prefix>-backup-sched "backup dr"

# On backup-sched:

pilotctl handshake <your-prefix>-restore-tester "backup dr"

# scheduler <-> secondary

# On backup-sched:

pilotctl handshake <your-prefix>-backup-secondary "backup dr"

# On backup-secondary:

pilotctl handshake <your-prefix>-backup-sched "backup dr"

pilotctl trust

Brand Protection

intermediate 4 agents · 11 skills

Deploy a brand protection system with 4 agents that monitor for unauthorized brand usage, classify threats, enforce takedowns, and visualize brand health. A scanner crawls marketplaces and social media for counterfeits and impersonation, a classifier categorizes violations by type and severity, an enforcer files DMCA notices and platform reports, and a dashboard tracks violation trends and enforcement success rates.

pilot-stream-data pilot-cron pilot-archive pilot-event-filter pilot-task-router pilot-metrics pilot-webhook-bridge pilot-audit-log pilot-receipt pilot-slack-bridge pilot-announce

clawhub install pilot-brand-protection-setup

ClawHub Source

Agents 4

<your-prefix>-scanner Brand Scanner

Crawls marketplaces, social media, and domains for unauthorized brand usage and counterfeits.

pilot-stream-data pilot-cron pilot-archive

clawhub install pilot-stream-data pilot-cron pilot-archive

pilotctl set-hostname <your-prefix>-scanner

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-classifier "setup: brand-protection"

<your-prefix>-classifier Threat Classifier

Classifies violations by type (counterfeit, impersonation, trademark), severity, and platform.

pilot-event-filter pilot-task-router pilot-metrics

clawhub install pilot-event-filter pilot-task-router pilot-metrics

pilotctl set-hostname <your-prefix>-classifier

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-scanner "setup: brand-protection"

pilotctl handshake <your-prefix>-enforcer "setup: brand-protection"

<your-prefix>-enforcer Takedown Enforcer

Files DMCA notices, platform reports, and cease-and-desist requests. Tracks enforcement status.

pilot-webhook-bridge pilot-audit-log pilot-receipt

clawhub install pilot-webhook-bridge pilot-audit-log pilot-receipt

pilotctl set-hostname <your-prefix>-enforcer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-classifier "setup: brand-protection"

pilotctl handshake <your-prefix>-dashboard "setup: brand-protection"

<your-prefix>-dashboard Brand Dashboard

Visualizes brand health metrics, violation trends, and enforcement success rates.

pilot-metrics pilot-slack-bridge pilot-announce

clawhub install pilot-metrics pilot-slack-bridge pilot-announce

pilotctl set-hostname <your-prefix>-dashboard

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-enforcer "setup: brand-protection"

Data Flows

<your-prefix>-scanner → <your-prefix>-classifier brand-violation events from platform scans :1002

<your-prefix>-classifier → <your-prefix>-enforcer classified-threat with type, severity, and priority :1002

<your-prefix>-enforcer → <your-prefix>-dashboard enforcement-action with status and outcomes :1002

<your-prefix>-dashboard → external brand-report via Slack and webhooks :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-classifier -- subscribe to brand violations from scanner:

pilotctl subscribe <your-prefix>-scanner brand-violation

# On <your-prefix>-scanner -- publish a detected violation:

pilotctl publish <your-prefix>-classifier brand-violation '{"violation_id":"BV-20481","platform":"amazon","type":"counterfeit","brand":"Acme Corp","product":"Acme Pro Widget","listing_url":"https://amazon.com/dp/B0FAKE123","seller":"ShenzhenDirect","confidence":0.91,"evidence":["logo_match:98%","product_copy:87%"]}'

# On <your-prefix>-enforcer -- subscribe to classified threats:

pilotctl subscribe <your-prefix>-classifier classified-threat

# On <your-prefix>-classifier -- publish a classified threat:

pilotctl publish <your-prefix>-enforcer classified-threat '{"violation_id":"BV-20481","type":"counterfeit","severity":"high","platform":"amazon","priority_score":0.94,"recommended_action":"dmca_takedown","evidence_summary":"Logo match 98%, product copy 87%, seller history: 3 prior violations"}'

# On <your-prefix>-dashboard -- subscribe to enforcement actions:

pilotctl subscribe <your-prefix>-enforcer enforcement-action

# On <your-prefix>-enforcer -- publish an enforcement action:

pilotctl publish <your-prefix>-dashboard enforcement-action '{"violation_id":"BV-20481","action":"dmca_filed","platform":"amazon","case_ref":"DMCA-2026-04091","status":"pending","filed_at":"2026-04-09T14:30:00Z","expected_resolution":"72h"}'

# On <your-prefix>-dashboard -- publish brand health report:

pilotctl publish <your-prefix>-dashboard brand-report '{"period":"2026-W15","violations_detected":23,"takedowns_filed":18,"takedowns_resolved":14,"success_rate":0.78,"top_platform":"amazon","trend":"improving"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (brand scanner)

clawhub install pilot-stream-data pilot-cron pilot-archive

pilotctl set-hostname <your-prefix>-scanner

# On server 2 (threat classifier)

clawhub install pilot-event-filter pilot-task-router pilot-metrics

pilotctl set-hostname <your-prefix>-classifier

# On server 3 (takedown enforcer)

clawhub install pilot-webhook-bridge pilot-audit-log pilot-receipt

pilotctl set-hostname <your-prefix>-enforcer

# On server 4 (brand dashboard)

clawhub install pilot-metrics pilot-slack-bridge pilot-announce

pilotctl set-hostname <your-prefix>-dashboard

# scanner <-> classifier

# On scanner:

pilotctl handshake <your-prefix>-classifier "setup: brand-protection"

# On classifier:

pilotctl handshake <your-prefix>-scanner "setup: brand-protection"

# classifier <-> enforcer

# On classifier:

pilotctl handshake <your-prefix>-enforcer "setup: brand-protection"

# On enforcer:

pilotctl handshake <your-prefix>-classifier "setup: brand-protection"

# enforcer <-> dashboard

# On enforcer:

pilotctl handshake <your-prefix>-dashboard "setup: brand-protection"

# On dashboard:

pilotctl handshake <your-prefix>-enforcer "setup: brand-protection"

pilotctl trust

Chat & Collaboration Hub

intermediate 4 agents · 15 skills

A self-hosted collaboration platform for agent teams. Supports group chat rooms with threaded conversations, real-time presence indicators, automatic message translation, and a moderation bot that filters content and maintains archives.

pilot-group-chat pilot-thread pilot-presence pilot-broadcast pilot-event-filter pilot-blocklist pilot-audit-log pilot-alert pilot-translate pilot-stream-data pilot-task-router pilot-archive pilot-event-log pilot-backup pilot-cron

clawhub install pilot-chat-collaboration-hub-setup

ClawHub Source

Agents 4

<your-prefix>-chat-server Chat Server

Messages for filtering" },

pilot-group-chat pilot-thread pilot-presence pilot-broadcast

clawhub install pilot-group-chat pilot-thread pilot-presence pilot-broadcast

pilotctl set-hostname <your-prefix>-chat-server

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-moderator "setup: chat-collaboration-hub"

pilotctl handshake <your-prefix>-translator "setup: chat-collaboration-hub"

pilotctl handshake <your-prefix>-archive-bot "setup: chat-collaboration-hub"

<your-prefix>-moderator Content Moderator

Messages to filter" },

pilot-event-filter pilot-blocklist pilot-audit-log pilot-alert

clawhub install pilot-event-filter pilot-blocklist pilot-audit-log pilot-alert

pilotctl set-hostname <your-prefix>-moderator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-chat "setup: chat-collaboration-hub"

<your-prefix>-translator Auto-Translator

Messages to translate" },

pilot-translate pilot-stream-data pilot-task-router

clawhub install pilot-translate pilot-stream-data pilot-task-router

pilotctl set-hostname <your-prefix>-translator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-chat "setup: chat-collaboration-hub"

<your-prefix>-archive-bot Archive Bot

Messages to archive" },

pilot-archive pilot-event-log pilot-backup pilot-cron

clawhub install pilot-archive pilot-event-log pilot-backup pilot-cron

pilotctl set-hostname <your-prefix>-archive-bot

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-chat "setup: chat-collaboration-hub"

Data Flows

<your-prefix>-chat-server → <your-prefix>-moderator/translator/archive-bot messages :1002

<your-prefix>-moderator → <your-prefix>-chat-server filter decisions :1002

<your-prefix>-translator → <your-prefix>-chat-server translated messages :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-chat — broadcast a message to room participants:

pilotctl publish <your-prefix>-moderator chat-message '{"room":"general","sender":"agent-alice","text":"Has anyone seen the deploy logs?"}'

pilotctl publish <your-prefix>-translator chat-message '{"room":"general","sender":"agent-alice","text":"Has anyone seen the deploy logs?","lang":"en"}'

pilotctl publish <your-prefix>-archive-bot chat-message '{"room":"general","sender":"agent-alice","text":"Has anyone seen the deploy logs?","ts":1711929600}'

# On <your-prefix>-moderator — approve or filter:

pilotctl publish <your-prefix>-chat moderation-result '{"msg_id":"M-5012","action":"approve","flags":[]}'

# On <your-prefix>-translator — return translation:

pilotctl publish <your-prefix>-chat translated-message '{"msg_id":"M-5012","original_lang":"en","target_lang":"ja","text":"デプロイログを見た人はいますか？"}'

# On <your-prefix>-archive-bot — confirm archival:

pilotctl publish <your-prefix>-chat archive-confirm '{"msg_id":"M-5012","stored":true,"index":"chat-2024-03"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On chat server

clawhub install pilot-group-chat pilot-thread pilot-presence pilot-broadcast

pilotctl set-hostname <your-prefix>-chat

# On moderator node

clawhub install pilot-event-filter pilot-blocklist pilot-audit-log pilot-alert

pilotctl set-hostname <your-prefix>-moderator

# On translator node

clawhub install pilot-translate pilot-stream-data pilot-task-router

pilotctl set-hostname <your-prefix>-translator

# On archive node

clawhub install pilot-archive pilot-event-log pilot-backup pilot-cron

pilotctl set-hostname <your-prefix>-archive-bot

# chat <-> moderator

# On chat:

pilotctl handshake <your-prefix>-moderator "chat hub"

# On moderator:

pilotctl handshake <your-prefix>-chat "chat hub"

# chat <-> translator

# On chat:

pilotctl handshake <your-prefix>-translator "chat hub"

# On translator:

pilotctl handshake <your-prefix>-chat "chat hub"

# chat <-> archive-bot

# On chat:

pilotctl handshake <your-prefix>-archive-bot "chat hub"

# On archive-bot:

pilotctl handshake <your-prefix>-chat "chat hub"

pilotctl trust

CI/CD Pipeline

intermediate 3 agents · 6 skills

A fully decentralized CI/CD pipeline where each stage runs on a separate agent. GitHub webhooks trigger builds, artifacts flow between stages over Pilot tunnels, and deployment receipts provide an audit trail.

pilot-task-router pilot-share pilot-github-bridge pilot-audit-log pilot-webhook-bridge pilot-receipt

clawhub install pilot-ci-cd-pipeline-setup

ClawHub Source

Agents 3

<your-prefix>-ci-builder Build Agent

Listens for GitHub push/PR webhooks, clones the repo, runs builds, and shares artifacts with the test agent.

pilot-task-router pilot-share pilot-github-bridge

clawhub install pilot-task-router pilot-share pilot-github-bridge

pilotctl set-hostname <your-prefix>-ci-builder

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-ci-tester "setup: ci-cd-pipeline"

pilotctl handshake <your-prefix>-ci-deployer "setup: ci-cd-pipeline"

<your-prefix>-ci-tester Test Agent

Receives build artifacts, runs test suites, and logs results. Passes successful builds to the deployer.

pilot-task-router pilot-share pilot-audit-log

clawhub install pilot-task-router pilot-share pilot-audit-log

pilotctl set-hostname <your-prefix>-ci-tester

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-ci-builder "setup: ci-cd-pipeline"

pilotctl handshake <your-prefix>-ci-deployer "setup: ci-cd-pipeline"

<your-prefix>-ci-deployer Deploy Agent

Receives tested artifacts, deploys to production, sends deployment receipts, and triggers post-deploy webhooks.

pilot-task-router pilot-share pilot-webhook-bridge pilot-receipt

clawhub install pilot-task-router pilot-share pilot-webhook-bridge pilot-receipt

pilotctl set-hostname <your-prefix>-ci-deployer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-ci-builder "setup: ci-cd-pipeline"

pilotctl handshake <your-prefix>-ci-tester "setup: ci-cd-pipeline"

Data Flows

<your-prefix>-ci-builder → <your-prefix>-ci-tester build artifacts :1001

<your-prefix>-ci-tester → <your-prefix>-ci-deployer tested artifacts with test report :1001

<your-prefix>-ci-deployer → <your-prefix>-ci-builder deployment receipt :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-ci-builder — receive a GitHub webhook and send build artifact:

pilotctl send-file <your-prefix>-ci-tester ./build/app-v2.3.tar.gz

pilotctl publish <your-prefix>-ci-tester build-ready '{"commit":"a1b2c3d","branch":"main","artifact":"app-v2.3.tar.gz"}'

# On <your-prefix>-ci-tester — run tests and forward to deployer:

pilotctl send-file <your-prefix>-ci-deployer ./build/app-v2.3.tar.gz

pilotctl publish <your-prefix>-ci-deployer tests-passed '{"commit":"a1b2c3d","tests":142,"passed":142,"coverage":87}'

# On <your-prefix>-ci-deployer — deploy and send receipt:

pilotctl publish <your-prefix>-ci-builder deploy-receipt '{"commit":"a1b2c3d","env":"production","status":"success","url":"https://app.example.com"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On build server

clawhub install pilot-task-router pilot-share pilot-github-bridge

pilotctl set-hostname <your-prefix>-ci-builder

# On test server

clawhub install pilot-task-router pilot-share pilot-audit-log

pilotctl set-hostname <your-prefix>-ci-tester

# On deploy server

clawhub install pilot-task-router pilot-share pilot-webhook-bridge pilot-receipt

pilotctl set-hostname <your-prefix>-ci-deployer

# On ci-builder:

pilotctl handshake <your-prefix>-ci-deployer "setup: ci-cd-pipeline"

# On ci-deployer:

pilotctl handshake <your-prefix>-ci-builder "setup: ci-cd-pipeline"

# On ci-builder:

pilotctl handshake <your-prefix>-ci-tester "setup: ci-cd-pipeline"

# On ci-tester:

pilotctl handshake <your-prefix>-ci-builder "setup: ci-cd-pipeline"

# On ci-deployer:

pilotctl handshake <your-prefix>-ci-tester "setup: ci-cd-pipeline"

# On ci-tester:

pilotctl handshake <your-prefix>-ci-deployer "setup: ci-cd-pipeline"

pilotctl trust

Cloud Cost Optimizer

intermediate 4 agents · 12 skills

A distributed FinOps pipeline that continuously scans cloud environments for waste, analyzes spending patterns, executes approved optimizations, and delivers savings reports. Four agents collaborate to keep cloud bills under control without any centralized orchestrator.

pilot-cron pilot-stream-data pilot-metrics pilot-health pilot-event-filter pilot-alert pilot-task-router pilot-audit-log pilot-receipt pilot-webhook-bridge pilot-slack-bridge pilot-announce

clawhub install pilot-cloud-cost-optimizer-setup

ClawHub Source

Agents 4

<your-prefix>-scanner Resource Scanner

Scans cloud resources, collects billing and utilization data

pilot-cron pilot-stream-data pilot-metrics pilot-health

clawhub install pilot-cron pilot-stream-data pilot-metrics pilot-health

pilotctl set-hostname <your-prefix>-scanner

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: cloud-cost-optimizer"

<your-prefix>-analyzer Cost Analyzer

Identifies waste, rightsizing, and spend anomalies

pilot-event-filter pilot-alert pilot-metrics

clawhub install pilot-event-filter pilot-alert pilot-metrics

pilotctl set-hostname <your-prefix>-analyzer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-scanner "setup: cloud-cost-optimizer"

pilotctl handshake <your-prefix>-optimizer "setup: cloud-cost-optimizer"

pilotctl handshake <your-prefix>-reporter "setup: cloud-cost-optimizer"

<your-prefix>-optimizer Optimization Agent

Executes approved optimizations, logs actions

pilot-task-router pilot-audit-log pilot-receipt

clawhub install pilot-task-router pilot-audit-log pilot-receipt

pilotctl set-hostname <your-prefix>-optimizer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: cloud-cost-optimizer"

pilotctl handshake <your-prefix>-reporter "setup: cloud-cost-optimizer"

<your-prefix>-reporter Cost Reporter

Generates cost reports, sends to Slack/email

pilot-webhook-bridge pilot-slack-bridge pilot-announce

clawhub install pilot-webhook-bridge pilot-slack-bridge pilot-announce

pilotctl set-hostname <your-prefix>-reporter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: cloud-cost-optimizer"

pilotctl handshake <your-prefix>-optimizer "setup: cloud-cost-optimizer"

Data Flows

<your-prefix>-scanner → <your-prefix>-analyzer resource utilization metrics :1002

<your-prefix>-analyzer → <your-prefix>-optimizer optimization recommendations :1002

<your-prefix>-analyzer → <your-prefix>-reporter cost anomaly alerts :1002

<your-prefix>-optimizer → <your-prefix>-reporter action receipts with savings :1002

<your-prefix>-reporter → external cost reports via Slack/email :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-scanner -- publish a resource scan:

pilotctl publish <your-prefix>-analyzer resource-scan '{"provider":"aws","region":"us-east-1","idle_instances":["i-0a1b2c3d"],"total_monthly_cost":12450.00,"utilization_avg":0.23}'

# On <your-prefix>-analyzer -- publish a cost recommendation:

pilotctl publish <your-prefix>-optimizer cost-recommendation '{"action":"terminate","resource":"i-0a1b2c3d","type":"ec2","monthly_savings":342.50,"confidence":0.95}'

# On <your-prefix>-analyzer -- publish a cost anomaly:

pilotctl publish <your-prefix>-reporter cost-anomaly '{"service":"lambda","region":"eu-west-1","spike_pct":280,"expected_daily":45.00,"actual_daily":171.00}'

# On <your-prefix>-optimizer -- publish an action receipt:

pilotctl publish <your-prefix>-reporter action-receipt '{"action":"terminate","resource":"i-0a1b2c3d","status":"success","savings_monthly":342.50}'

# On <your-prefix>-reporter -- subscribe to incoming events:

pilotctl subscribe cost-anomaly

pilotctl subscribe action-receipt

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (resource scanner)

clawhub install pilot-cron pilot-stream-data pilot-metrics pilot-health

pilotctl set-hostname <your-prefix>-scanner

# On server 2 (cost analyzer)

clawhub install pilot-event-filter pilot-alert pilot-metrics

pilotctl set-hostname <your-prefix>-analyzer

# On server 3 (optimization agent)

clawhub install pilot-task-router pilot-audit-log pilot-receipt

pilotctl set-hostname <your-prefix>-optimizer

# On server 4 (cost reporter)

clawhub install pilot-webhook-bridge pilot-slack-bridge pilot-announce

pilotctl set-hostname <your-prefix>-reporter

# scanner <-> analyzer (resource metrics flow)

# On scanner:

pilotctl handshake <your-prefix>-analyzer "setup: cloud-cost-optimizer"

# On analyzer:

pilotctl handshake <your-prefix>-scanner "setup: cloud-cost-optimizer"

# analyzer <-> optimizer (optimization recommendations)

# On analyzer:

pilotctl handshake <your-prefix>-optimizer "setup: cloud-cost-optimizer"

# On optimizer:

pilotctl handshake <your-prefix>-analyzer "setup: cloud-cost-optimizer"

# analyzer <-> reporter (cost anomalies)

# On analyzer:

pilotctl handshake <your-prefix>-reporter "setup: cloud-cost-optimizer"

# On reporter:

pilotctl handshake <your-prefix>-analyzer "setup: cloud-cost-optimizer"

# optimizer <-> reporter (action receipts)

# On optimizer:

pilotctl handshake <your-prefix>-reporter "setup: cloud-cost-optimizer"

# On reporter:

pilotctl handshake <your-prefix>-optimizer "setup: cloud-cost-optimizer"

pilotctl trust

Code Review Pipeline

beginner 3 agents · 9 skills

Deploy an automated code review pipeline with 3 agents that scan pull requests for issues, analyze code quality patterns, and report results back to your development workflow. Each agent handles a stage of the review process -- scanning, analysis, and reporting -- so reviews happen automatically on every PR.

pilot-github-bridge pilot-task-router pilot-metrics pilot-event-filter pilot-alert pilot-audit-log pilot-webhook-bridge pilot-slack-bridge pilot-receipt

clawhub install pilot-code-review-pipeline-setup

ClawHub Source

Agents 3

<your-prefix>-scanner Code Scanner

Runs static analysis, linting, and security scans on PRs.

pilot-github-bridge pilot-task-router pilot-metrics

clawhub install pilot-github-bridge pilot-task-router pilot-metrics

pilotctl set-hostname <your-prefix>-scanner

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-reviewer "setup: code-review-pipeline"

<your-prefix>-reviewer Code Reviewer

Analyzes scan results, checks code patterns, suggests improvements.

pilot-event-filter pilot-alert pilot-audit-log

clawhub install pilot-event-filter pilot-alert pilot-audit-log

pilotctl set-hostname <your-prefix>-reviewer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-scanner "setup: code-review-pipeline"

pilotctl handshake <your-prefix>-reporter "setup: code-review-pipeline"

<your-prefix>-reporter Review Reporter

Formats review results, posts PR comments, tracks metrics.

pilot-webhook-bridge pilot-slack-bridge pilot-receipt

clawhub install pilot-webhook-bridge pilot-slack-bridge pilot-receipt

pilotctl set-hostname <your-prefix>-reporter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-reviewer "setup: code-review-pipeline"

Data Flows

<your-prefix>-scanner → <your-prefix>-reviewer scan-result events :1002

<your-prefix>-reviewer → <your-prefix>-reporter review-verdict events :1002

<your-prefix>-reporter → external review-notification via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-reviewer — subscribe to scan results from scanner:

pilotctl subscribe <your-prefix>-scanner scan-result

# On <your-prefix>-reporter — subscribe to review verdicts from reviewer:

pilotctl subscribe <your-prefix>-reviewer review-verdict

# On <your-prefix>-scanner — publish a scan result:

pilotctl publish <your-prefix>-reviewer scan-result '{"pr":142,"repo":"acme/api","findings":[{"file":"auth.go","line":58,"severity":"high","rule":"sql-injection"}],"summary":"1 high, 0 medium, 0 low"}'

# On <your-prefix>-reviewer — publish a review verdict:

pilotctl publish <your-prefix>-reporter review-verdict '{"pr":142,"repo":"acme/api","status":"changes_requested","comments":1,"suggestion":"Use parameterized queries in auth.go:58"}'

# The reporter receives the verdict and posts to Slack:

pilotctl publish <your-prefix>-reporter review-notification '{"channel":"#code-review","text":"PR #142 acme/api: changes requested — 1 finding"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (code scanner)

clawhub install pilot-github-bridge pilot-task-router pilot-metrics

pilotctl set-hostname <your-prefix>-scanner

# On server 2 (code reviewer)

clawhub install pilot-event-filter pilot-alert pilot-audit-log

pilotctl set-hostname <your-prefix>-reviewer

# On server 3 (review reporter)

clawhub install pilot-webhook-bridge pilot-slack-bridge pilot-receipt

pilotctl set-hostname <your-prefix>-reporter

# On reviewer:

pilotctl handshake <your-prefix>-scanner "setup: code-review-pipeline"

# On scanner:

pilotctl handshake <your-prefix>-reviewer "setup: code-review-pipeline"

# On reporter:

pilotctl handshake <your-prefix>-reviewer "setup: code-review-pipeline"

# On reviewer:

pilotctl handshake <your-prefix>-reporter "setup: code-review-pipeline"

pilotctl trust

Competitor Intelligence

intermediate 4 agents · 12 skills

Deploy a multi-agent competitive intelligence system that crawls competitor websites, analyzes market trends, tracks changes over time, and routes actionable alerts to your team. Each agent handles a stage of the intelligence pipeline, from raw data collection through analysis to prioritized notifications.

pilot-stream-data pilot-archive pilot-cron pilot-event-filter pilot-metrics pilot-task-router pilot-audit-log pilot-dataset pilot-alert pilot-slack-bridge pilot-webhook-bridge pilot-announce

clawhub install pilot-competitor-intelligence-setup

ClawHub Source

Agents 4

<your-prefix>-crawler Web Crawler

Scrapes competitor websites, pricing pages, product launches, and press releases.

pilot-stream-data pilot-archive pilot-cron

clawhub install pilot-stream-data pilot-archive pilot-cron

pilotctl set-hostname <your-prefix>-crawler

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: competitor-intelligence"

<your-prefix>-analyzer Market Analyzer

Processes crawled data, identifies trends, price changes, and feature gaps.

pilot-event-filter pilot-metrics pilot-task-router

clawhub install pilot-event-filter pilot-metrics pilot-task-router

pilotctl set-hostname <your-prefix>-analyzer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-crawler "setup: competitor-intelligence"

pilotctl handshake <your-prefix>-tracker "setup: competitor-intelligence"

<your-prefix>-tracker Change Tracker

Maintains historical records, detects significant changes, scores threat levels.

pilot-audit-log pilot-dataset pilot-alert

clawhub install pilot-audit-log pilot-dataset pilot-alert

pilotctl set-hostname <your-prefix>-tracker

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: competitor-intelligence"

pilotctl handshake <your-prefix>-alerter "setup: competitor-intelligence"

<your-prefix>-alerter Intelligence Alerter

Routes actionable intelligence to Slack, email, and dashboards based on severity.

pilot-slack-bridge pilot-webhook-bridge pilot-announce

clawhub install pilot-slack-bridge pilot-webhook-bridge pilot-announce

pilotctl set-hostname <your-prefix>-alerter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-tracker "setup: competitor-intelligence"

Data Flows

<your-prefix>-crawler → <your-prefix>-analyzer crawled-data events :1002

<your-prefix>-analyzer → <your-prefix>-tracker market-insight events :1002

<your-prefix>-tracker → <your-prefix>-alerter change-alert events :1002

<your-prefix>-alerter → external intelligence-report via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-analyzer — subscribe to crawled data from crawler:

pilotctl subscribe <your-prefix>-crawler crawled-data

# On <your-prefix>-tracker — subscribe to market insights from analyzer:

pilotctl subscribe <your-prefix>-analyzer market-insight

# On <your-prefix>-alerter — subscribe to change alerts from tracker:

pilotctl subscribe <your-prefix>-tracker change-alert

# On <your-prefix>-crawler — publish crawled data:

pilotctl publish <your-prefix>-analyzer crawled-data '{"competitor":"RivalCorp","url":"https://rivalcorp.com/pricing","type":"pricing_page","products":[{"name":"Pro Plan","price":49.99,"was":59.99}]}'

# On <your-prefix>-analyzer — publish a market insight:

pilotctl publish <your-prefix>-tracker market-insight '{"competitor":"RivalCorp","insight":"price_decrease","product":"Pro Plan","change_pct":-16.7,"trend":"aggressive_pricing"}'

# On <your-prefix>-tracker — publish a change alert:

pilotctl publish <your-prefix>-alerter change-alert '{"competitor":"RivalCorp","threat_score":8,"change":"Pro Plan price cut 16.7%","historical_context":"3rd price cut in 6 months","recommendation":"review_pricing_strategy"}'

# On <your-prefix>-alerter — forward intelligence report:

pilotctl publish <your-prefix>-alerter intelligence-report '{"channel":"#competitive-intel","severity":"high","summary":"RivalCorp aggressive pricing: Pro Plan down 16.7%","action_required":true}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (web crawler)

clawhub install pilot-stream-data pilot-archive pilot-cron

pilotctl set-hostname <your-prefix>-crawler

# On server 2 (market analyzer)

clawhub install pilot-event-filter pilot-metrics pilot-task-router

pilotctl set-hostname <your-prefix>-analyzer

# On server 3 (change tracker)

clawhub install pilot-audit-log pilot-dataset pilot-alert

pilotctl set-hostname <your-prefix>-tracker

# On server 4 (intelligence alerter)

clawhub install pilot-slack-bridge pilot-webhook-bridge pilot-announce

pilotctl set-hostname <your-prefix>-alerter

# On crawler:

pilotctl handshake <your-prefix>-analyzer "setup: competitor-intelligence"

# On analyzer:

pilotctl handshake <your-prefix>-crawler "setup: competitor-intelligence"

# On analyzer:

pilotctl handshake <your-prefix>-tracker "setup: competitor-intelligence"

# On tracker:

pilotctl handshake <your-prefix>-analyzer "setup: competitor-intelligence"

# On tracker:

pilotctl handshake <your-prefix>-alerter "setup: competitor-intelligence"

# On alerter:

pilotctl handshake <your-prefix>-tracker "setup: competitor-intelligence"

pilotctl trust

Compliance & Governance

advanced 4 agents · 15 skills

Automated compliance for regulated environments. A policy engine evaluates every agent action against governance rules, an auditor maintains tamper-evident logs, a certifier issues and verifies compliance certificates, and a reporter generates audit reports on schedule.

pilot-event-filter pilot-sla pilot-workflow pilot-task-chain pilot-audit-log pilot-verify pilot-event-log pilot-cron pilot-certificate pilot-keychain pilot-receipt pilot-metrics pilot-webhook-bridge pilot-slack-bridge pilot-archive

clawhub install pilot-compliance-governance-setup

ClawHub Source

Agents 4

<your-prefix>-policy-engine Policy Engine

Violations for logging" },

pilot-event-filter pilot-sla pilot-workflow pilot-task-chain

clawhub install pilot-event-filter pilot-sla pilot-workflow pilot-task-chain

pilotctl set-hostname <your-prefix>-policy-engine

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-auditor "setup: compliance-governance"

pilotctl handshake <your-prefix>-certifier "setup: compliance-governance"

<your-prefix>-auditor Audit Trail

Violations" },

pilot-audit-log pilot-verify pilot-event-log pilot-cron

clawhub install pilot-audit-log pilot-verify pilot-event-log pilot-cron

pilotctl set-hostname <your-prefix>-auditor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-policy "setup: compliance-governance"

pilotctl handshake <your-prefix>-reporter "setup: compliance-governance"

<your-prefix>-certifier Compliance Certifier

Certification requests" },

pilot-certificate pilot-keychain pilot-verify pilot-receipt

clawhub install pilot-certificate pilot-keychain pilot-verify pilot-receipt

pilotctl set-hostname <your-prefix>-certifier

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-policy "setup: compliance-governance"

pilotctl handshake <your-prefix>-reporter "setup: compliance-governance"

<your-prefix>-reporter Compliance Reporter

Audit data" },

pilot-metrics pilot-webhook-bridge pilot-slack-bridge pilot-archive

clawhub install pilot-metrics pilot-webhook-bridge pilot-slack-bridge pilot-archive

pilotctl set-hostname <your-prefix>-reporter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-auditor "setup: compliance-governance"

pilotctl handshake <your-prefix>-certifier "setup: compliance-governance"

Data Flows

<your-prefix>-policy → <your-prefix>-auditor policy violations :1002

<your-prefix>-policy → <your-prefix>-certifier certification requests :1002

<your-prefix>-auditor → <your-prefix>-reporter audit data for reports :1002

<your-prefix>-certifier → <your-prefix>-reporter certification records :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-policy — evaluate an agent action and route:

pilotctl publish <your-prefix>-auditor policy-violation '{"agent":"data-processor-3","action":"write_to_prod","rule":"require-approval","severity":"high"}'

pilotctl publish <your-prefix>-certifier cert-request '{"agent":"data-processor-1","scope":"prod-write","policy_checks_passed":true}'

# On <your-prefix>-auditor — log and forward to reporter:

pilotctl publish <your-prefix>-reporter audit-finding '{"finding_id":"AUD-0721","agent":"data-processor-3","violation":"unauthorized prod write","severity":"high"}'

# On <your-prefix>-certifier — issue cert and notify reporter:

pilotctl publish <your-prefix>-reporter cert-issued '{"agent":"data-processor-1","cert_id":"CERT-2024-0315","scope":"prod-write","expires":"2024-06-15"}'

# On <your-prefix>-reporter — generate summary:

pilotctl publish <your-prefix>-reporter slack-forward '{"channel":"#compliance","text":"Weekly report: 3 violations, 12 certs issued, 99.2% compliance rate"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On policy engine node

clawhub install pilot-event-filter pilot-sla pilot-workflow pilot-task-chain

pilotctl set-hostname <your-prefix>-policy

# On auditor node

clawhub install pilot-audit-log pilot-verify pilot-event-log pilot-cron

pilotctl set-hostname <your-prefix>-auditor

# On certifier node

clawhub install pilot-certificate pilot-keychain pilot-verify pilot-receipt

pilotctl set-hostname <your-prefix>-certifier

# On reporter node

clawhub install pilot-metrics pilot-webhook-bridge pilot-slack-bridge pilot-archive

pilotctl set-hostname <your-prefix>-reporter

# policy <-> auditor

# On policy:

pilotctl handshake <your-prefix>-auditor "compliance"

# On auditor:

pilotctl handshake <your-prefix>-policy "compliance"

# policy <-> certifier

# On policy:

pilotctl handshake <your-prefix>-certifier "compliance"

# On certifier:

pilotctl handshake <your-prefix>-policy "compliance"

# auditor <-> reporter

# On auditor:

pilotctl handshake <your-prefix>-reporter "compliance"

# On reporter:

pilotctl handshake <your-prefix>-auditor "compliance"

# certifier <-> reporter

# On certifier:

pilotctl handshake <your-prefix>-reporter "compliance"

# On reporter:

pilotctl handshake <your-prefix>-certifier "compliance"

pilotctl trust

Content Marketing Pipeline

beginner 3 agents · 9 skills

Deploy a content production pipeline where a researcher gathers trending topics and source material, a writer transforms briefs into polished articles and social copy, and a publisher formats content for your CMS and schedules publication. The three agents form an assembly line that turns raw research into published content with minimal human intervention.

pilot-discover pilot-stream-data pilot-archive pilot-task-router pilot-share pilot-receipt pilot-webhook-bridge pilot-announce pilot-slack-bridge

clawhub install pilot-content-marketing-pipeline-setup

ClawHub Source

Agents 3

<your-prefix>-researcher Content Researcher

Gathers trending topics, keywords, competitor content, and source material. Packages findings into structured research briefs.

pilot-discover pilot-stream-data pilot-archive

clawhub install pilot-discover pilot-stream-data pilot-archive

pilotctl set-hostname <your-prefix>-researcher

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-writer "setup: content-marketing-pipeline"

<your-prefix>-writer Content Writer

Transforms research briefs into polished articles, blog posts, and social copy in the brand voice.

pilot-task-router pilot-share pilot-receipt

clawhub install pilot-task-router pilot-share pilot-receipt

pilotctl set-hostname <your-prefix>-writer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-researcher "setup: content-marketing-pipeline"

pilotctl handshake <your-prefix>-publisher "setup: content-marketing-pipeline"

<your-prefix>-publisher Content Publisher

Formats final content for CMS, generates metadata, schedules publication, and notifies stakeholders.

pilot-webhook-bridge pilot-announce pilot-slack-bridge

clawhub install pilot-webhook-bridge pilot-announce pilot-slack-bridge

pilotctl set-hostname <your-prefix>-publisher

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-writer "setup: content-marketing-pipeline"

Data Flows

<your-prefix>-researcher → <your-prefix>-writer research-brief :1002

<your-prefix>-writer → <your-prefix>-publisher draft-content :1002

<your-prefix>-publisher → external publish-notify via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-writer -- subscribe to research briefs:

pilotctl subscribe <your-prefix>-researcher research-brief

# On <your-prefix>-publisher -- subscribe to draft content:

pilotctl subscribe <your-prefix>-writer draft-content

# On <your-prefix>-researcher -- publish a research brief:

pilotctl publish <your-prefix>-writer research-brief '{"topic":"AI Agent Frameworks 2026","keywords":["autonomous agents","multi-agent","orchestration"],"competitors":["langchain","crewai"],"sources":["arxiv:2406.01234","techcrunch.com/ai-agents"],"seo_difficulty":"medium"}'

# On <your-prefix>-writer -- publish a draft to the publisher:

pilotctl publish <your-prefix>-publisher draft-content '{"title":"The Rise of AI Agent Frameworks","slug":"ai-agent-frameworks-2026","word_count":1850,"format":"markdown","tags":["ai","agents","frameworks"],"status":"ready"}'

# The publisher formats and pushes to CMS, then notifies Slack:

pilotctl publish <your-prefix>-publisher publish-notify '{"channel":"#content","text":"Published: The Rise of AI Agent Frameworks","url":"https://blog.acme.com/ai-agent-frameworks-2026"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (content researcher)

clawhub install pilot-discover pilot-stream-data pilot-archive

pilotctl set-hostname <your-prefix>-researcher

# On server 2 (content writer)

clawhub install pilot-task-router pilot-share pilot-receipt

pilotctl set-hostname <your-prefix>-writer

# On server 3 (content publisher)

clawhub install pilot-webhook-bridge pilot-announce pilot-slack-bridge

pilotctl set-hostname <your-prefix>-publisher

# researcher <-> writer

# On researcher:

pilotctl handshake <your-prefix>-writer "setup: content-marketing-pipeline"

# On writer:

pilotctl handshake <your-prefix>-researcher "setup: content-marketing-pipeline"

# writer <-> publisher

# On writer:

pilotctl handshake <your-prefix>-publisher "setup: content-marketing-pipeline"

# On publisher:

pilotctl handshake <your-prefix>-writer "setup: content-marketing-pipeline"

pilotctl trust

Customer Onboarding

intermediate 3 agents · 9 skills

Deploy a customer onboarding system with 3 agents that automate the new customer journey from welcome through product setup to long-term success tracking. A welcome bot greets customers and collects preferences, a setup guide walks them through configuration milestones, and a success tracker monitors adoption metrics to identify at-risk customers before they churn.

pilot-chat pilot-announce pilot-receipt pilot-task-chain pilot-share pilot-webhook-bridge pilot-metrics pilot-alert pilot-slack-bridge

clawhub install pilot-customer-onboarding-setup

ClawHub Source

Agents 3

<your-prefix>-welcome-bot Welcome Bot

Greets customers, collects preferences, sends welcome sequences

pilot-chat pilot-announce pilot-receipt

clawhub install pilot-chat pilot-announce pilot-receipt

pilotctl set-hostname <your-prefix>-welcome-bot

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-setup-guide "setup: customer-onboarding"

<your-prefix>-setup-guide Setup Guide

Walks through configuration, tracks milestones, offers help

pilot-task-chain pilot-share pilot-webhook-bridge

clawhub install pilot-task-chain pilot-share pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-setup-guide

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-welcome-bot "setup: customer-onboarding"

pilotctl handshake <your-prefix>-success-tracker "setup: customer-onboarding"

<your-prefix>-success-tracker Success Tracker

Monitors adoption, identifies at-risk customers, triggers interventions

pilot-metrics pilot-alert pilot-slack-bridge

clawhub install pilot-metrics pilot-alert pilot-slack-bridge

pilotctl set-hostname <your-prefix>-success-tracker

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-setup-guide "setup: customer-onboarding"

Data Flows

<your-prefix>-welcome-bot → <your-prefix>-setup-guide customer-profile :1002

<your-prefix>-setup-guide → <your-prefix>-success-tracker onboarding-progress :1002

<your-prefix>-success-tracker → external health-report via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-setup-guide -- subscribe to customer profiles:

pilotctl subscribe <your-prefix>-welcome-bot customer-profile

# On <your-prefix>-welcome-bot -- publish a customer profile:

pilotctl publish <your-prefix>-setup-guide customer-profile '{"customer_id":"cust_8a3f","name":"Jane Smith","email":"[email protected]","plan":"pro","preferences":{"industry":"saas","team_size":12,"goals":["integrations","reporting"]}}'

# On <your-prefix>-success-tracker -- subscribe to onboarding progress:

pilotctl subscribe <your-prefix>-setup-guide onboarding-progress

# On <your-prefix>-setup-guide -- publish onboarding progress:

pilotctl publish <your-prefix>-success-tracker onboarding-progress '{"customer_id":"cust_8a3f","milestones":{"account_created":true,"first_integration":true,"team_invited":false,"first_report":false},"completion":0.50,"days_since_signup":3}'

# On <your-prefix>-success-tracker -- publish external health report:

pilotctl publish <your-prefix>-success-tracker health-report '{"customer_id":"cust_8a3f","health_score":0.65,"risk_level":"medium","blocked_on":"team_invited","recommendation":"Send team invite reminder email","days_since_signup":5}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (welcome bot)

clawhub install pilot-chat pilot-announce pilot-receipt

pilotctl set-hostname <your-prefix>-welcome-bot

# On server 2 (setup guide)

clawhub install pilot-task-chain pilot-share pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-setup-guide

# On server 3 (success tracker)

clawhub install pilot-metrics pilot-alert pilot-slack-bridge

pilotctl set-hostname <your-prefix>-success-tracker

# welcome-bot <-> setup-guide

# On welcome-bot:

pilotctl handshake <your-prefix>-setup-guide "setup: customer-onboarding"

# On setup-guide:

pilotctl handshake <your-prefix>-welcome-bot "setup: customer-onboarding"

# setup-guide <-> success-tracker

# On setup-guide:

pilotctl handshake <your-prefix>-success-tracker "setup: customer-onboarding"

# On success-tracker:

pilotctl handshake <your-prefix>-setup-guide "setup: customer-onboarding"

pilotctl trust

Customer Support Triage

beginner 3 agents · 8 skills

Deploy a support ticket triage system where incoming tickets are classified by urgency and category, routine issues are auto-resolved from a knowledge base, and complex cases are enriched with context and escalated to human agents. The three agents work together to reduce response times and ensure no ticket falls through the cracks.

pilot-event-filter pilot-priority-queue pilot-task-router pilot-receipt pilot-audit-log pilot-webhook-bridge pilot-slack-bridge pilot-alert

clawhub install pilot-customer-support-triage-setup

ClawHub Source

Agents 3

<your-prefix>-triage-bot Triage Bot

Receives incoming support tickets, classifies by urgency and category, routes to the right handler.

pilot-event-filter pilot-priority-queue pilot-task-router

clawhub install pilot-event-filter pilot-priority-queue pilot-task-router

pilotctl set-hostname <your-prefix>-triage-bot

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-resolver "setup: customer-support-triage"

pilotctl handshake <your-prefix>-escalator "setup: customer-support-triage"

<your-prefix>-resolver Auto-Resolver

Handles routine queries using knowledge base lookups -- order status, FAQs, password resets.

pilot-task-router pilot-receipt pilot-audit-log

clawhub install pilot-task-router pilot-receipt pilot-audit-log

pilotctl set-hostname <your-prefix>-resolver

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-triage-bot "setup: customer-support-triage"

<your-prefix>-escalator Escalation Agent

Takes complex issues, enriches with customer history and context, forwards to human support via webhook or Slack.

pilot-webhook-bridge pilot-slack-bridge pilot-alert

clawhub install pilot-webhook-bridge pilot-slack-bridge pilot-alert

pilotctl set-hostname <your-prefix>-escalator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-triage-bot "setup: customer-support-triage"

Data Flows

<your-prefix>-triage-bot → <your-prefix>-resolver ticket-routine :1002

<your-prefix>-triage-bot → <your-prefix>-escalator ticket-complex :1002

<your-prefix>-escalator → external escalation via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-resolver -- subscribe to routine tickets:

pilotctl subscribe <your-prefix>-triage-bot ticket-routine

# On <your-prefix>-escalator -- subscribe to complex tickets:

pilotctl subscribe <your-prefix>-triage-bot ticket-complex

# On <your-prefix>-triage-bot -- route a routine ticket (password reset):

pilotctl publish <your-prefix>-resolver ticket-routine '{"ticket_id":"TK-4821","category":"account","urgency":"low","subject":"Password reset request","customer":"[email protected]"}'

# On <your-prefix>-triage-bot -- route a complex ticket (data loss):

pilotctl publish <your-prefix>-escalator ticket-complex '{"ticket_id":"TK-4822","category":"technical","urgency":"critical","subject":"Production database showing missing records","customer":"[email protected]","account_tier":"enterprise"}'

# The escalator enriches context and forwards to the helpdesk:

pilotctl publish <your-prefix>-escalator escalation '{"channel":"#support-escalations","text":"CRITICAL: TK-4822 - Production data loss for enterprise account bigcorp","helpdesk_url":"https://help.acme.com/tickets/TK-4822"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (triage bot)

clawhub install pilot-event-filter pilot-priority-queue pilot-task-router

pilotctl set-hostname <your-prefix>-triage-bot

# On server 2 (auto-resolver)

clawhub install pilot-task-router pilot-receipt pilot-audit-log

pilotctl set-hostname <your-prefix>-resolver

# On server 3 (escalation agent)

clawhub install pilot-webhook-bridge pilot-slack-bridge pilot-alert

pilotctl set-hostname <your-prefix>-escalator

# triage-bot <-> resolver

# On triage-bot:

pilotctl handshake <your-prefix>-resolver "setup: customer-support-triage"

# On resolver:

pilotctl handshake <your-prefix>-triage-bot "setup: customer-support-triage"

# triage-bot <-> escalator

# On triage-bot:

pilotctl handshake <your-prefix>-escalator "setup: customer-support-triage"

# On escalator:

pilotctl handshake <your-prefix>-triage-bot "setup: customer-support-triage"

pilotctl trust

Data Labeling Pipeline

advanced 4 agents · 11 skills

Deploy a distributed data labeling pipeline with 4 agents that ingests raw data, applies ML-based labels, reviews quality, and exports training-ready datasets. The system handles images, text, and audio across formats like COCO, VOC, and JSONL, with inter-annotator agreement checks and automated quality gating.

pilot-s3-bridge pilot-stream-data pilot-task-parallel pilot-task-router pilot-dataset pilot-metrics pilot-review pilot-event-filter pilot-alert pilot-share pilot-webhook-bridge

clawhub install pilot-data-labeling-pipeline-setup

ClawHub Source

Agents 4

<your-prefix>-ingester Data Ingester

Accepts raw data batches, splits into work items

pilot-s3-bridge pilot-stream-data pilot-task-parallel

clawhub install pilot-s3-bridge pilot-stream-data pilot-task-parallel

pilotctl set-hostname <your-prefix>-ingester

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-labeler "setup: data-labeling-pipeline"

<your-prefix>-labeler Auto Labeler

Applies ML-based labels to work items

pilot-task-router pilot-dataset pilot-metrics

clawhub install pilot-task-router pilot-dataset pilot-metrics

pilotctl set-hostname <your-prefix>-labeler

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-ingester "setup: data-labeling-pipeline"

pilotctl handshake <your-prefix>-reviewer "setup: data-labeling-pipeline"

<your-prefix>-reviewer Quality Reviewer

Samples labeled items, checks accuracy, flags disagreements

pilot-review pilot-event-filter pilot-alert

clawhub install pilot-review pilot-event-filter pilot-alert

pilotctl set-hostname <your-prefix>-reviewer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-labeler "setup: data-labeling-pipeline"

pilotctl handshake <your-prefix>-exporter "setup: data-labeling-pipeline"

<your-prefix>-exporter Dataset Exporter

Packages approved labels into training-ready datasets

pilot-dataset pilot-share pilot-webhook-bridge

clawhub install pilot-dataset pilot-share pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-exporter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-reviewer "setup: data-labeling-pipeline"

Data Flows

<your-prefix>-ingester → <your-prefix>-labeler work-item events :1002

<your-prefix>-labeler → <your-prefix>-reviewer labeled-item events :1002

<your-prefix>-reviewer → <your-prefix>-labeler review-feedback events :1002

<your-prefix>-reviewer → <your-prefix>-exporter approved-label events :1002

<your-prefix>-exporter → external dataset-published notifications :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-labeler — subscribe to work items from ingester:

pilotctl subscribe <your-prefix>-ingester work-item

# On <your-prefix>-ingester — publish a work item:

pilotctl publish <your-prefix>-labeler work-item '{"batch_id":"batch-042","item_id":"img-0017","type":"image","s3_uri":"s3://raw-data/batch-042/img-0017.jpg","labels_requested":["object_detection","classification"]}'

# On <your-prefix>-reviewer — subscribe to labeled items:

pilotctl subscribe <your-prefix>-labeler labeled-item

# On <your-prefix>-labeler — publish a labeled item:

pilotctl publish <your-prefix>-reviewer labeled-item '{"item_id":"img-0017","labels":[{"class":"vehicle","bbox":[120,45,380,290],"confidence":0.94}],"model":"yolov8-custom"}'

# On <your-prefix>-exporter — subscribe to approved labels:

pilotctl subscribe <your-prefix>-reviewer approved-label

# On <your-prefix>-reviewer — approve and forward:

pilotctl publish <your-prefix>-exporter approved-label '{"item_id":"img-0017","labels":[{"class":"vehicle","bbox":[120,45,380,290]}],"reviewer":"auto-qa","agreement_score":0.92}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (data ingestion)

clawhub install pilot-s3-bridge pilot-stream-data pilot-task-parallel

pilotctl set-hostname <your-prefix>-ingester

# On server 2 (auto labeling)

clawhub install pilot-task-router pilot-dataset pilot-metrics

pilotctl set-hostname <your-prefix>-labeler

# On server 3 (quality review)

clawhub install pilot-review pilot-event-filter pilot-alert

pilotctl set-hostname <your-prefix>-reviewer

# On server 4 (dataset export)

clawhub install pilot-dataset pilot-share pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-exporter

# On ingester:

pilotctl handshake <your-prefix>-labeler "setup: data-labeling-pipeline"

# On labeler:

pilotctl handshake <your-prefix>-ingester "setup: data-labeling-pipeline"

# On labeler:

pilotctl handshake <your-prefix>-reviewer "setup: data-labeling-pipeline"

# On reviewer:

pilotctl handshake <your-prefix>-labeler "setup: data-labeling-pipeline"

# On reviewer:

pilotctl handshake <your-prefix>-exporter "setup: data-labeling-pipeline"

# On exporter:

pilotctl handshake <your-prefix>-reviewer "setup: data-labeling-pipeline"

pilotctl trust

Dev Team Assistants

intermediate 4 agents · 9 skills

A team of four agents that automate the PR workflow. A coordinator watches GitHub for new PRs and fans out tasks to specialized agents: one reviews code, one runs tests, one generates documentation. Results are collected and posted as a unified PR summary.

pilot-github-bridge pilot-review pilot-chat pilot-task-router pilot-audit-log pilot-share pilot-task-chain pilot-slack-bridge pilot-broadcast

clawhub install pilot-dev-team-assistants-setup

ClawHub Source

Agents 4

<your-prefix>-reviewer Code Reviewer

PR details" },

pilot-github-bridge pilot-review pilot-chat

clawhub install pilot-github-bridge pilot-review pilot-chat

pilotctl set-hostname <your-prefix>-reviewer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-coordinator "setup: dev-team-assistants"

<your-prefix>-test-runner Runs test suites

Runs test suites

pilot-github-bridge pilot-task-router pilot-audit-log

clawhub install pilot-github-bridge pilot-task-router pilot-audit-log

pilotctl set-hostname <your-prefix>-test-runner

<your-prefix>-doc-writer Generates docs

Generates docs

pilot-github-bridge pilot-share pilot-task-router

clawhub install pilot-github-bridge pilot-share pilot-task-router

pilotctl set-hostname <your-prefix>-doc-writer

<your-prefix>-coordinator PR Coordinator

PR details for review" },

pilot-github-bridge pilot-task-chain pilot-slack-bridge pilot-broadcast

clawhub install pilot-github-bridge pilot-task-chain pilot-slack-bridge pilot-broadcast

pilotctl set-hostname <your-prefix>-coordinator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-reviewer "setup: dev-team-assistants"

pilotctl handshake <your-prefix>-test-runner "setup: dev-team-assistants"

pilotctl handshake <your-prefix>-doc-writer "setup: dev-team-assistants"

Data Flows

<your-prefix>-coordinator → <your-prefix>-reviewer/test-runner/doc-writer PR details :1002

<your-prefix>-reviewer/test-runner → <your-prefix>-coordinator results :1002

<your-prefix>-doc-writer → <your-prefix>-coordinator generated docs :1001

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-coordinator — fan out a new PR to all assistants:

pilotctl task submit <your-prefix>-reviewer --task '{"pr":1234,"repo":"acme/api","action":"review","diff_url":"https://github.com/acme/api/pull/1234.diff"}'

pilotctl task submit <your-prefix>-test-runner --task '{"pr":1234,"repo":"acme/api","action":"test","branch":"feature/auth"}'

pilotctl task submit <your-prefix>-doc-writer --task '{"pr":1234,"repo":"acme/api","action":"docs","changed_files":["auth.go","middleware.go"]}'

# On <your-prefix>-reviewer — return findings:

pilotctl publish <your-prefix>-coordinator review-result '{"pr":1234,"issues":2,"approval":"changes_requested","comments":["missing error check on line 45"]}'

# On <your-prefix>-test-runner — return test results:

pilotctl publish <your-prefix>-coordinator test-result '{"pr":1234,"passed":89,"failed":0,"coverage":82}'

# On <your-prefix>-doc-writer — return generated docs:

pilotctl send-file <your-prefix>-coordinator ./docs/auth-middleware.md

pilotctl publish <your-prefix>-coordinator docs-result '{"pr":1234,"files_generated":["auth-middleware.md"]}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On review server

clawhub install pilot-github-bridge pilot-review pilot-chat

pilotctl set-hostname <your-prefix>-reviewer

# On docs server

clawhub install pilot-github-bridge pilot-share pilot-task-router

pilotctl set-hostname <your-prefix>-doc-writer

# On test server

clawhub install pilot-github-bridge pilot-task-router pilot-audit-log

pilotctl set-hostname <your-prefix>-test-runner

# On coordinator server

clawhub install pilot-github-bridge pilot-task-chain pilot-slack-bridge pilot-broadcast

pilotctl set-hostname <your-prefix>-coordinator

# On coordinator:

pilotctl handshake <your-prefix>-doc-writer "setup: dev-team-assistants"

# On doc-writer:

pilotctl handshake <your-prefix>-coordinator "setup: dev-team-assistants"

# On coordinator:

pilotctl handshake <your-prefix>-reviewer "setup: dev-team-assistants"

# On reviewer:

pilotctl handshake <your-prefix>-coordinator "setup: dev-team-assistants"

# On coordinator:

pilotctl handshake <your-prefix>-test-runner "setup: dev-team-assistants"

# On test-runner:

pilotctl handshake <your-prefix>-coordinator "setup: dev-team-assistants"

pilotctl trust

Digital Twin

advanced 4 agents · 12 skills

A digital twin platform that mirrors physical assets in real time, predicts failures before they occur, detects anomalous behavior, and schedules proactive maintenance. The sensor bridge ingests live telemetry, the model engine maintains a physics-based simulation, the anomaly detector compares real versus predicted behavior, and the action planner recommends and schedules interventions.

pilot-stream-data pilot-metrics pilot-gossip pilot-dataset pilot-task-router pilot-consensus pilot-event-filter pilot-alert pilot-audit-log pilot-webhook-bridge pilot-cron pilot-slack-bridge

clawhub install pilot-digital-twin-setup

ClawHub Source

Agents 4

<your-prefix>-sensor-bridge Sensor Bridge

Ingests real-time telemetry from physical assets

pilot-stream-data pilot-metrics pilot-gossip

clawhub install pilot-stream-data pilot-metrics pilot-gossip

pilotctl set-hostname <your-prefix>-sensor-bridge

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-model-engine "setup: digital-twin"

<your-prefix>-model-engine Model Engine

Real-time sensor data" },

pilot-dataset pilot-task-router pilot-consensus

clawhub install pilot-dataset pilot-task-router pilot-consensus

pilotctl set-hostname <your-prefix>-model-engine

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-sensor-bridge "setup: digital-twin"

pilotctl handshake <your-prefix>-anomaly-detector "setup: digital-twin"

<your-prefix>-anomaly-detector Anomaly Detector

Model predictions to compare" },

pilot-event-filter pilot-alert pilot-audit-log

clawhub install pilot-event-filter pilot-alert pilot-audit-log

pilotctl set-hostname <your-prefix>-anomaly-detector

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-model-engine "setup: digital-twin"

pilotctl handshake <your-prefix>-action-planner "setup: digital-twin"

<your-prefix>-action-planner Action Planner

Anomaly alerts to act on" },

pilot-webhook-bridge pilot-cron pilot-slack-bridge

clawhub install pilot-webhook-bridge pilot-cron pilot-slack-bridge

pilotctl set-hostname <your-prefix>-action-planner

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-anomaly-detector "setup: digital-twin"

Data Flows

<your-prefix>-sensor-bridge → <your-prefix>-model-engine real-time telemetry from physical assets :1002

<your-prefix>-model-engine → <your-prefix>-anomaly-detector predictions and expected behavior baselines :1002

<your-prefix>-anomaly-detector → <your-prefix>-action-planner anomaly alerts with severity and root cause :1002

<your-prefix>-action-planner → external maintenance orders to field team systems :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-sensor-bridge -- stream telemetry to model engine:

pilotctl publish <your-prefix>-model-engine telemetry '{"asset_id":"PUMP-A7","timestamp":"2026-04-10T14:30:00Z","sensors":{"temperature_c":87.3,"vibration_mm_s":4.2,"pressure_bar":6.8,"flow_rate_lpm":142.5},"sampling_hz":10}'

# On <your-prefix>-model-engine -- send prediction to anomaly detector:

pilotctl publish <your-prefix>-anomaly-detector prediction '{"asset_id":"PUMP-A7","timestamp":"2026-04-10T14:30:00Z","expected":{"temperature_c":82.1,"vibration_mm_s":2.8,"pressure_bar":7.0,"flow_rate_lpm":150.0},"actual":{"temperature_c":87.3,"vibration_mm_s":4.2,"pressure_bar":6.8,"flow_rate_lpm":142.5},"drift_pct":{"temperature":6.3,"vibration":50.0,"pressure":2.9,"flow_rate":5.0}}'

# On <your-prefix>-anomaly-detector -- alert action planner:

pilotctl publish <your-prefix>-action-planner anomaly-alert '{"asset_id":"PUMP-A7","severity":"warning","anomaly_type":"bearing_degradation","confidence":0.89,"indicators":["vibration_50pct_above_baseline","temperature_rising_trend"],"estimated_failure_days":14}'

# On <your-prefix>-action-planner -- subscribe to anomaly alerts:

pilotctl subscribe <your-prefix>-anomaly-detector anomaly-alert

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On sensor bridge node

clawhub install pilot-stream-data pilot-metrics pilot-gossip

pilotctl set-hostname <your-prefix>-sensor-bridge

# On model engine node

clawhub install pilot-dataset pilot-task-router pilot-consensus

pilotctl set-hostname <your-prefix>-model-engine

# On anomaly detector node

clawhub install pilot-event-filter pilot-alert pilot-audit-log

pilotctl set-hostname <your-prefix>-anomaly-detector

# On action planner node

clawhub install pilot-webhook-bridge pilot-cron pilot-slack-bridge

pilotctl set-hostname <your-prefix>-action-planner

# sensor-bridge <-> model-engine (telemetry)

# On sensor-bridge:

pilotctl handshake <your-prefix>-model-engine "setup: digital-twin"

# On model-engine:

pilotctl handshake <your-prefix>-sensor-bridge "setup: digital-twin"

# model-engine <-> anomaly-detector (predictions)

# On model-engine:

pilotctl handshake <your-prefix>-anomaly-detector "setup: digital-twin"

# On anomaly-detector:

pilotctl handshake <your-prefix>-model-engine "setup: digital-twin"

# anomaly-detector <-> action-planner (anomaly alerts)

# On anomaly-detector:

pilotctl handshake <your-prefix>-action-planner "setup: digital-twin"

# On action-planner:

pilotctl handshake <your-prefix>-anomaly-detector "setup: digital-twin"

pilotctl trust

Disaster Response

advanced 4 agents · 12 skills

A multi-agent emergency management system that coordinates sensor aggregation, disaster assessment, resource allocation, and public communications across four specialized agents. The sensor hub aggregates feeds from weather stations, seismic sensors, flood gauges, and satellite imagery. The coordinator assesses disaster severity and activates response protocols. The resource allocator manages inventory of emergency supplies, vehicles, and personnel. The communications hub broadcasts public alerts and coordinates with agencies.

pilot-stream-data pilot-metrics pilot-gossip pilot-task-router pilot-consensus pilot-audit-log pilot-dataset pilot-event-filter pilot-escrow pilot-announce pilot-slack-bridge pilot-webhook-bridge

clawhub install pilot-disaster-response-setup

ClawHub Source

Agents 4

<your-prefix>-sensor-hub Sensor Hub

Aggregates weather, seismic, and flood sensor feeds

pilot-stream-data pilot-metrics pilot-gossip

clawhub install pilot-stream-data pilot-metrics pilot-gossip

pilotctl set-hostname <your-prefix>-sensor-hub

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-coordinator "setup: disaster-response"

<your-prefix>-coordinator Response Coordinator

Assesses severity, activates response protocols

pilot-task-router pilot-consensus pilot-audit-log

clawhub install pilot-task-router pilot-consensus pilot-audit-log

pilotctl set-hostname <your-prefix>-coordinator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-sensor-hub "setup: disaster-response"

pilotctl handshake <your-prefix>-resource-allocator "setup: disaster-response"

pilotctl handshake <your-prefix>-comms "setup: disaster-response"

<your-prefix>-resource-allocator Resource Allocator

Manages supplies, vehicles, personnel deployment

pilot-dataset pilot-event-filter pilot-escrow

clawhub install pilot-dataset pilot-event-filter pilot-escrow

pilotctl set-hostname <your-prefix>-resource-allocator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-coordinator "setup: disaster-response"

pilotctl handshake <your-prefix>-comms "setup: disaster-response"

<your-prefix>-comms Communications Hub

Broadcasts alerts, coordinates with agencies

pilot-announce pilot-slack-bridge pilot-webhook-bridge

clawhub install pilot-announce pilot-slack-bridge pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-comms

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-coordinator "setup: disaster-response"

pilotctl handshake <your-prefix>-resource-allocator "setup: disaster-response"

Data Flows

<your-prefix>-sensor-hub → <your-prefix>-coordinator disaster alerts with severity and geographic data :1002

<your-prefix>-coordinator → <your-prefix>-resource-allocator resource requests with priority and location :1002

<your-prefix>-coordinator → <your-prefix>-comms public alerts with severity and instructions :1002

<your-prefix>-resource-allocator → <your-prefix>-comms deployment status and resource availability :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-sensor-hub -- publish a disaster alert:

pilotctl publish <your-prefix>-coordinator disaster-alert '{"type":"flood","severity":"high","location":{"lat":29.76,"lon":-95.37,"radius_km":25},"river_gauge_m":8.4,"threshold_m":7.0,"confidence":0.94,"timestamp":"2026-04-10T06:30:00Z"}'

# On <your-prefix>-coordinator -- publish a resource request:

pilotctl publish <your-prefix>-resource-allocator resource-request '{"incident_id":"INC-2841","type":"flood","severity":"high","location":"houston-metro","teams_needed":12,"supplies":["sandbags","pumps","boats"],"priority":"critical"}'

# On <your-prefix>-coordinator -- publish a public alert:

pilotctl publish <your-prefix>-comms public-alert '{"incident_id":"INC-2841","type":"flood","severity":"high","message":"Flash flood warning for Houston metro area. Seek higher ground immediately.","channels":["eas","sms","web"]}'

# On <your-prefix>-resource-allocator -- publish deployment status:

pilotctl publish <your-prefix>-comms deployment-status '{"incident_id":"INC-2841","teams_deployed":8,"teams_en_route":4,"supplies_dispatched":{"sandbags":5000,"pumps":24,"boats":12},"eta_min":45}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On sensor aggregation server

clawhub install pilot-stream-data pilot-metrics pilot-gossip

pilotctl set-hostname <your-prefix>-sensor-hub

# On coordination server

clawhub install pilot-task-router pilot-consensus pilot-audit-log

pilotctl set-hostname <your-prefix>-coordinator

# On resource management server

clawhub install pilot-dataset pilot-event-filter pilot-escrow

pilotctl set-hostname <your-prefix>-resource-allocator

# On communications server

clawhub install pilot-announce pilot-slack-bridge pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-comms

# sensor-hub <-> coordinator (disaster alerts)

# On sensor-hub:

pilotctl handshake <your-prefix>-coordinator "setup: disaster-response"

# On coordinator:

pilotctl handshake <your-prefix>-sensor-hub "setup: disaster-response"

# coordinator <-> resource-allocator (resource requests)

# On coordinator:

pilotctl handshake <your-prefix>-resource-allocator "setup: disaster-response"

# On resource-allocator:

pilotctl handshake <your-prefix>-coordinator "setup: disaster-response"

# coordinator <-> comms (public alerts)

# On coordinator:

pilotctl handshake <your-prefix>-comms "setup: disaster-response"

# On comms:

pilotctl handshake <your-prefix>-coordinator "setup: disaster-response"

# resource-allocator <-> comms (deployment status)

# On resource-allocator:

pilotctl handshake <your-prefix>-comms "setup: disaster-response"

# On comms:

pilotctl handshake <your-prefix>-resource-allocator "setup: disaster-response"

pilotctl trust

Document Processing

beginner 3 agents · 9 skills

Deploy a document processing pipeline with 3 agents that automate document ingestion, structured data extraction, and search indexing. Each agent handles one stage of the pipeline, converting raw documents into searchable, structured data ready for downstream consumption.

pilot-stream-data pilot-share pilot-archive pilot-task-router pilot-dataset pilot-receipt pilot-webhook-bridge pilot-announce pilot-metrics

clawhub install pilot-document-processing-setup

ClawHub Source

Agents 3

<your-prefix>-ingester Document Ingester

Accepts documents, converts to processable format

pilot-stream-data pilot-share pilot-archive

clawhub install pilot-stream-data pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-ingester

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-extractor "setup: document-processing"

<your-prefix>-extractor Data Extractor

Extracts structured data — tables, entities, amounts

pilot-task-router pilot-dataset pilot-receipt

clawhub install pilot-task-router pilot-dataset pilot-receipt

pilotctl set-hostname <your-prefix>-extractor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-ingester "setup: document-processing"

pilotctl handshake <your-prefix>-indexer "setup: document-processing"

<your-prefix>-indexer Search Indexer

Indexes data for search, publishes to downstream systems

pilot-webhook-bridge pilot-announce pilot-metrics

clawhub install pilot-webhook-bridge pilot-announce pilot-metrics

pilotctl set-hostname <your-prefix>-indexer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-extractor "setup: document-processing"

Data Flows

<your-prefix>-ingester → <your-prefix>-extractor raw-document events :1002

<your-prefix>-extractor → <your-prefix>-indexer extracted-data events :1002

<your-prefix>-indexer → <your-prefix>-downstream index notifications via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-extractor — subscribe to raw documents from ingester:

pilotctl subscribe <your-prefix>-ingester raw-document

# On <your-prefix>-ingester — publish a raw document:

pilotctl publish <your-prefix>-extractor raw-document '{"filename":"invoice-2024-003.pdf","type":"pdf","pages":2,"size_kb":184,"source":"email-attachment"}'

# On <your-prefix>-indexer — subscribe to extracted data:

pilotctl subscribe <your-prefix>-extractor extracted-data

# On <your-prefix>-extractor — publish extracted data:

pilotctl publish <your-prefix>-indexer extracted-data '{"filename":"invoice-2024-003.pdf","vendor":"Acme Corp","amount":12500.00,"currency":"USD","date":"2024-03-15","line_items":3}'

# On <your-prefix>-indexer — publish index notification:

pilotctl publish <your-prefix>-indexer index-notification '{"doc_id":"inv-2024-003","index":"invoices","status":"indexed","searchable":true,"summary":"Acme Corp invoice for $12,500"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (document ingestion)

clawhub install pilot-stream-data pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-ingester

# On server 2 (data extraction)

clawhub install pilot-task-router pilot-dataset pilot-receipt

pilotctl set-hostname <your-prefix>-extractor

# On server 3 (search indexing)

clawhub install pilot-webhook-bridge pilot-announce pilot-metrics

pilotctl set-hostname <your-prefix>-indexer

# On ingester:

pilotctl handshake <your-prefix>-extractor "setup: document-processing"

# On extractor:

pilotctl handshake <your-prefix>-ingester "setup: document-processing"

# On extractor:

pilotctl handshake <your-prefix>-indexer "setup: document-processing"

# On indexer:

pilotctl handshake <your-prefix>-extractor "setup: document-processing"

pilotctl trust

E-Commerce Ops

intermediate 4 agents · 12 skills

Deploy a multi-agent e-commerce operations system that manages product catalogs, processes orders, tracks inventory, and handles customer support. Each agent owns a distinct domain of the storefront, communicating through event streams to keep the entire operation synchronized in real time.

pilot-dataset pilot-share pilot-audit-log pilot-task-router pilot-receipt pilot-escrow pilot-metrics pilot-alert pilot-stream-data pilot-chat pilot-event-filter pilot-webhook-bridge

clawhub install pilot-e-commerce-ops-setup

ClawHub Source

Agents 4

<your-prefix>-catalog-manager Product Catalog Manager

Manages product listings, prices, descriptions, and images. Publishes catalog updates.

pilot-dataset pilot-share pilot-audit-log

clawhub install pilot-dataset pilot-share pilot-audit-log

pilotctl set-hostname <your-prefix>-catalog-manager

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-order-processor "setup: e-commerce-ops"

pilotctl handshake <your-prefix>-inventory-tracker "setup: e-commerce-ops"

<your-prefix>-order-processor Order Processor

Receives and validates orders, calculates totals, triggers fulfillment.

pilot-task-router pilot-receipt pilot-escrow

clawhub install pilot-task-router pilot-receipt pilot-escrow

pilotctl set-hostname <your-prefix>-order-processor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-catalog-manager "setup: e-commerce-ops"

pilotctl handshake <your-prefix>-inventory-tracker "setup: e-commerce-ops"

pilotctl handshake <your-prefix>-support-bot "setup: e-commerce-ops"

<your-prefix>-inventory-tracker Inventory Tracker

Monitors stock levels, triggers reorder alerts, syncs warehouse counts.

pilot-metrics pilot-alert pilot-stream-data

clawhub install pilot-metrics pilot-alert pilot-stream-data

pilotctl set-hostname <your-prefix>-inventory-tracker

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-order-processor "setup: e-commerce-ops"

pilotctl handshake <your-prefix>-catalog-manager "setup: e-commerce-ops"

<your-prefix>-support-bot Customer Support Bot

Handles order inquiries, returns, refund requests, and FAQs.

pilot-chat pilot-event-filter pilot-webhook-bridge

clawhub install pilot-chat pilot-event-filter pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-support-bot

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-order-processor "setup: e-commerce-ops"

Data Flows

<your-prefix>-catalog-manager → <your-prefix>-order-processor catalog-update events :1002

<your-prefix>-order-processor → <your-prefix>-inventory-tracker order-fulfilled events :1002

<your-prefix>-inventory-tracker → <your-prefix>-catalog-manager stock-alert events :1002

<your-prefix>-order-processor → <your-prefix>-support-bot order-status events :1002

<your-prefix>-support-bot → external support-escalation via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-order-processor — subscribe to catalog updates:

pilotctl subscribe <your-prefix>-catalog-manager catalog-update

# On <your-prefix>-inventory-tracker — subscribe to order events:

pilotctl subscribe <your-prefix>-order-processor order-fulfilled

# On <your-prefix>-catalog-manager — subscribe to stock alerts:

pilotctl subscribe <your-prefix>-inventory-tracker stock-alert

# On <your-prefix>-support-bot — subscribe to order status:

pilotctl subscribe <your-prefix>-order-processor order-status

# On <your-prefix>-catalog-manager — publish a catalog update:

pilotctl publish <your-prefix>-order-processor catalog-update '{"product_id":"SKU-4821","name":"Wireless Headphones","price":79.99,"action":"price_change","old_price":99.99}'

# On <your-prefix>-order-processor — publish an order fulfilled event:

pilotctl publish <your-prefix>-inventory-tracker order-fulfilled '{"order_id":"ORD-10042","product_id":"SKU-4821","quantity":2,"total":159.98,"status":"fulfilled"}'

# On <your-prefix>-inventory-tracker — publish a stock alert:

pilotctl publish <your-prefix>-catalog-manager stock-alert '{"product_id":"SKU-4821","current_stock":3,"reorder_threshold":10,"status":"low_stock"}'

# On <your-prefix>-order-processor — publish order status to support:

pilotctl publish <your-prefix>-support-bot order-status '{"order_id":"ORD-10042","customer":"[email protected]","status":"shipped","tracking":"1Z999AA10123456784"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (product catalog)

clawhub install pilot-dataset pilot-share pilot-audit-log

pilotctl set-hostname <your-prefix>-catalog-manager

# On server 2 (order processing)

clawhub install pilot-task-router pilot-receipt pilot-escrow

pilotctl set-hostname <your-prefix>-order-processor

# On server 3 (inventory tracking)

clawhub install pilot-metrics pilot-alert pilot-stream-data

pilotctl set-hostname <your-prefix>-inventory-tracker

# On server 4 (customer support)

clawhub install pilot-chat pilot-event-filter pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-support-bot

# On catalog-manager:

pilotctl handshake <your-prefix>-order-processor "setup: e-commerce-ops"

# On order-processor:

pilotctl handshake <your-prefix>-catalog-manager "setup: e-commerce-ops"

# On order-processor:

pilotctl handshake <your-prefix>-inventory-tracker "setup: e-commerce-ops"

# On inventory-tracker:

pilotctl handshake <your-prefix>-order-processor "setup: e-commerce-ops"

# On inventory-tracker:

pilotctl handshake <your-prefix>-catalog-manager "setup: e-commerce-ops"

# On catalog-manager:

pilotctl handshake <your-prefix>-inventory-tracker "setup: e-commerce-ops"

# On order-processor:

pilotctl handshake <your-prefix>-support-bot "setup: e-commerce-ops"

# On support-bot:

pilotctl handshake <your-prefix>-order-processor "setup: e-commerce-ops"

pilotctl trust

Energy Grid Optimizer

advanced 4 agents · 12 skills

A multi-agent energy management system that coordinates real-time sensor aggregation, demand forecasting, grid optimization, and device control across four specialized agents. The sensor mesh collects readings from smart meters, solar panels, batteries, and grid sensors. The forecaster predicts energy demand using weather, time-of-day, and historical patterns. The optimizer balances load across sources and schedules battery charge/discharge cycles. The controller sends commands to inverters, batteries, HVAC systems, and EV chargers, then confirms execution.

pilot-stream-data pilot-metrics pilot-gossip pilot-dataset pilot-task-router pilot-cron pilot-consensus pilot-event-filter pilot-audit-log pilot-webhook-bridge pilot-receipt pilot-alert

clawhub install pilot-energy-grid-optimizer-setup

ClawHub Source

Agents 4

<your-prefix>-sensor-mesh Sensor Mesh

Aggregates real-time grid sensor readings

pilot-stream-data pilot-metrics pilot-gossip

clawhub install pilot-stream-data pilot-metrics pilot-gossip

pilotctl set-hostname <your-prefix>-sensor-mesh

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-forecaster "setup: energy-grid-optimizer"

pilotctl handshake <your-prefix>-controller "setup: energy-grid-optimizer"

<your-prefix>-forecaster Load Forecaster

Predicts energy demand from weather and history

pilot-dataset pilot-task-router pilot-cron

clawhub install pilot-dataset pilot-task-router pilot-cron

pilotctl set-hostname <your-prefix>-forecaster

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-sensor-mesh "setup: energy-grid-optimizer"

pilotctl handshake <your-prefix>-optimizer "setup: energy-grid-optimizer"

<your-prefix>-optimizer Grid Optimizer

Balances load, schedules battery cycles

pilot-consensus pilot-event-filter pilot-audit-log

clawhub install pilot-consensus pilot-event-filter pilot-audit-log

pilotctl set-hostname <your-prefix>-optimizer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-forecaster "setup: energy-grid-optimizer"

pilotctl handshake <your-prefix>-controller "setup: energy-grid-optimizer"

<your-prefix>-controller Device Controller

Sends device commands, confirms execution

pilot-webhook-bridge pilot-receipt pilot-alert

clawhub install pilot-webhook-bridge pilot-receipt pilot-alert

pilotctl set-hostname <your-prefix>-controller

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-optimizer "setup: energy-grid-optimizer"

pilotctl handshake <your-prefix>-sensor-mesh "setup: energy-grid-optimizer"

Data Flows

<your-prefix>-sensor-mesh → <your-prefix>-forecaster grid readings with voltage, current, and power metrics :1002

<your-prefix>-forecaster → <your-prefix>-optimizer demand forecasts with confidence intervals :1002

<your-prefix>-optimizer → <your-prefix>-controller dispatch commands for device setpoints :1002

<your-prefix>-controller → <your-prefix>-sensor-mesh device acknowledgments with execution status :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-sensor-mesh -- publish a grid reading:

pilotctl publish <your-prefix>-forecaster grid-reading '{"source":"solar-array-1","voltage_v":408.2,"current_a":12.5,"power_kw":5.1,"battery_soc":0.73,"timestamp":"2026-04-10T14:00:00Z"}'

# On <your-prefix>-forecaster -- publish a demand forecast:

pilotctl publish <your-prefix>-optimizer demand-forecast '{"horizon":"1h","predicted_kw":42.8,"confidence":0.91,"weather":"partly_cloudy","peak_expected":"2026-04-10T18:00:00Z"}'

# On <your-prefix>-optimizer -- publish a dispatch command:

pilotctl publish <your-prefix>-controller dispatch-command '{"device":"battery-bank-1","action":"discharge","setpoint_kw":10.0,"duration_min":60,"priority":"high","reason":"peak_shaving"}'

# On <your-prefix>-controller -- publish a device acknowledgment:

pilotctl publish <your-prefix>-sensor-mesh device-ack '{"device":"battery-bank-1","action":"discharge","status":"executing","actual_kw":9.8,"timestamp":"2026-04-10T17:01:03Z"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On sensor aggregation server

clawhub install pilot-stream-data pilot-metrics pilot-gossip

pilotctl set-hostname <your-prefix>-sensor-mesh

# On forecasting server

clawhub install pilot-dataset pilot-task-router pilot-cron

pilotctl set-hostname <your-prefix>-forecaster

# On optimization server

clawhub install pilot-consensus pilot-event-filter pilot-audit-log

pilotctl set-hostname <your-prefix>-optimizer

# On device control server

clawhub install pilot-webhook-bridge pilot-receipt pilot-alert

pilotctl set-hostname <your-prefix>-controller

# sensor-mesh <-> forecaster (grid readings)

# On sensor-mesh:

pilotctl handshake <your-prefix>-forecaster "setup: energy-grid-optimizer"

# On forecaster:

pilotctl handshake <your-prefix>-sensor-mesh "setup: energy-grid-optimizer"

# forecaster <-> optimizer (demand forecasts)

# On forecaster:

pilotctl handshake <your-prefix>-optimizer "setup: energy-grid-optimizer"

# On optimizer:

pilotctl handshake <your-prefix>-forecaster "setup: energy-grid-optimizer"

# optimizer <-> controller (dispatch commands)

# On optimizer:

pilotctl handshake <your-prefix>-controller "setup: energy-grid-optimizer"

# On controller:

pilotctl handshake <your-prefix>-optimizer "setup: energy-grid-optimizer"

# controller <-> sensor-mesh (device acknowledgments)

# On controller:

pilotctl handshake <your-prefix>-sensor-mesh "setup: energy-grid-optimizer"

# On sensor-mesh:

pilotctl handshake <your-prefix>-controller "setup: energy-grid-optimizer"

pilotctl trust

ETL Data Pipeline

advanced 5 agents · 14 skills

A five-stage ETL pipeline for production data processing. Agents handle ingestion from S3 and databases, parallel transformation, data validation with quarantine for bad records, loading into target stores, and automated reporting via Slack dashboards.

pilot-s3-bridge pilot-database-bridge pilot-task-chain pilot-cron pilot-task-router pilot-stream-data pilot-task-parallel pilot-audit-log pilot-alert pilot-quarantine pilot-receipt pilot-webhook-bridge pilot-metrics pilot-slack-bridge

clawhub install pilot-etl-data-pipeline-setup

ClawHub Source

Agents 5

<your-prefix>-ingest Data Ingestion

Pulls raw data on schedule

pilot-s3-bridge pilot-database-bridge pilot-task-chain pilot-cron

clawhub install pilot-s3-bridge pilot-database-bridge pilot-task-chain pilot-cron

pilotctl set-hostname <your-prefix>-ingest

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-transform "setup: etl-data-pipeline"

<your-prefix>-transform Data Transformer

Raw data" },

pilot-task-router pilot-stream-data pilot-task-parallel

clawhub install pilot-task-router pilot-stream-data pilot-task-parallel

pilotctl set-hostname <your-prefix>-transform

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-ingest "setup: etl-data-pipeline"

pilotctl handshake <your-prefix>-validate "setup: etl-data-pipeline"

<your-prefix>-validate Data Validator

Transformed records" },

pilot-task-router pilot-audit-log pilot-alert pilot-quarantine

clawhub install pilot-task-router pilot-audit-log pilot-alert pilot-quarantine

pilotctl set-hostname <your-prefix>-validate

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-transform "setup: etl-data-pipeline"

pilotctl handshake <your-prefix>-loader "setup: etl-data-pipeline"

pilotctl handshake <your-prefix>-reporter "setup: etl-data-pipeline"

<your-prefix>-loader Data Loader

Validated records" },

pilot-database-bridge pilot-task-chain pilot-receipt

clawhub install pilot-database-bridge pilot-task-chain pilot-receipt

pilotctl set-hostname <your-prefix>-loader

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-validate "setup: etl-data-pipeline"

pilotctl handshake <your-prefix>-reporter "setup: etl-data-pipeline"

<your-prefix>-reporter Pipeline Reporter

Error rates" },

pilot-webhook-bridge pilot-metrics pilot-slack-bridge pilot-cron

clawhub install pilot-webhook-bridge pilot-metrics pilot-slack-bridge pilot-cron

pilotctl set-hostname <your-prefix>-reporter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-validate "setup: etl-data-pipeline"

pilotctl handshake <your-prefix>-loader "setup: etl-data-pipeline"

Data Flows

<your-prefix>-ingest → <your-prefix>-transform raw data batches :1001

<your-prefix>-transform → <your-prefix>-validate transformed records :1001

<your-prefix>-validate → <your-prefix>-loader validated records :1001

<your-prefix>-loader → <your-prefix>-reporter load receipts :1002

<your-prefix>-validate → <your-prefix>-reporter validation metrics :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-ingest — trigger data ingestion and send to transformer:

pilotctl send-file <your-prefix>-transform ./data/raw/orders-2024-03.csv

pilotctl publish <your-prefix>-transform ingest-batch '{"source":"s3://data/orders","rows":50000,"batch_id":"B-1042"}'

# On <your-prefix>-transform — process and forward to validator:

pilotctl send-file <your-prefix>-validate ./data/transformed/orders-B-1042.parquet

pilotctl publish <your-prefix>-validate transform-complete '{"batch_id":"B-1042","rows_in":50000,"rows_out":49823}'

# On <your-prefix>-validate — validate and forward good records:

pilotctl send-file <your-prefix>-loader ./data/validated/orders-B-1042.parquet

pilotctl publish <your-prefix>-loader validation-passed '{"batch_id":"B-1042","valid":49700,"quarantined":123}'

pilotctl publish <your-prefix>-reporter validation-metrics '{"batch_id":"B-1042","error_rate":0.0025}'

# On <your-prefix>-loader — load and send receipt:

pilotctl publish <your-prefix>-reporter load-receipt '{"batch_id":"B-1042","rows_loaded":49700,"target":"warehouse.orders"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On ingestion server

clawhub install pilot-s3-bridge pilot-database-bridge pilot-task-chain pilot-cron

pilotctl set-hostname <your-prefix>-ingest

# On transform server

clawhub install pilot-task-router pilot-stream-data pilot-task-parallel

pilotctl set-hostname <your-prefix>-transform

# On validation server

clawhub install pilot-task-router pilot-audit-log pilot-alert pilot-quarantine

pilotctl set-hostname <your-prefix>-validate

# On loader server

clawhub install pilot-database-bridge pilot-task-chain pilot-receipt

pilotctl set-hostname <your-prefix>-loader

# On reporting server

clawhub install pilot-webhook-bridge pilot-metrics pilot-slack-bridge pilot-cron

pilotctl set-hostname <your-prefix>-reporter

# On ingest:

pilotctl handshake <your-prefix>-transform "setup: etl-data-pipeline"

# On transform:

pilotctl handshake <your-prefix>-ingest "setup: etl-data-pipeline"

# On loader:

pilotctl handshake <your-prefix>-reporter "setup: etl-data-pipeline"

# On reporter:

pilotctl handshake <your-prefix>-loader "setup: etl-data-pipeline"

# On loader:

pilotctl handshake <your-prefix>-validate "setup: etl-data-pipeline"

# On validate:

pilotctl handshake <your-prefix>-loader "setup: etl-data-pipeline"

# On reporter:

pilotctl handshake <your-prefix>-validate "setup: etl-data-pipeline"

# On validate:

pilotctl handshake <your-prefix>-reporter "setup: etl-data-pipeline"

# On transform:

pilotctl handshake <your-prefix>-validate "setup: etl-data-pipeline"

# On validate:

pilotctl handshake <your-prefix>-transform "setup: etl-data-pipeline"

pilotctl trust

Expense Tracker

beginner 3 agents · 9 skills

Deploy an expense tracking pipeline with 3 agents that automate receipt collection, expense categorization, and report generation. Each agent handles one stage of the pipeline, turning raw receipts into categorized expense reports ready for manager approval.

pilot-stream-data pilot-share pilot-archive pilot-task-router pilot-event-filter pilot-metrics pilot-webhook-bridge pilot-announce pilot-slack-bridge

clawhub install pilot-expense-tracker-setup

ClawHub Source

Agents 3

<your-prefix>-collector Receipt Collector

Accepts receipts, extracts amount, vendor, category

pilot-stream-data pilot-share pilot-archive

clawhub install pilot-stream-data pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-collector

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-categorizer "setup: expense-tracker"

<your-prefix>-categorizer Expense Categorizer

Classifies expenses, flags policy violations, calculates totals

pilot-task-router pilot-event-filter pilot-metrics

clawhub install pilot-task-router pilot-event-filter pilot-metrics

pilotctl set-hostname <your-prefix>-categorizer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-collector "setup: expense-tracker"

pilotctl handshake <your-prefix>-reporter "setup: expense-tracker"

<your-prefix>-reporter Expense Reporter

Generates reports, submits for approval, notifies managers

pilot-webhook-bridge pilot-announce pilot-slack-bridge

clawhub install pilot-webhook-bridge pilot-announce pilot-slack-bridge

pilotctl set-hostname <your-prefix>-reporter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-categorizer "setup: expense-tracker"

Data Flows

<your-prefix>-collector → <your-prefix>-categorizer raw-expense events :1002

<your-prefix>-categorizer → <your-prefix>-reporter categorized-expense events :1002

<your-prefix>-reporter → external expense-report via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-categorizer -- subscribe to raw expenses from collector:

pilotctl subscribe <your-prefix>-collector raw-expense

# On <your-prefix>-reporter -- subscribe to categorized expenses:

pilotctl subscribe <your-prefix>-categorizer categorized-expense

# On <your-prefix>-collector -- publish a raw expense:

pilotctl publish <your-prefix>-categorizer raw-expense '{"vendor":"Delta Airlines","amount":487.50,"currency":"USD","date":"2025-03-12","receipt_type":"photo","category_hint":"travel","employee":"jane.smith"}'

# On <your-prefix>-categorizer -- publish a categorized expense to the reporter:

pilotctl publish <your-prefix>-reporter categorized-expense '{"vendor":"Delta Airlines","amount":487.50,"currency":"USD","category":"travel","subcategory":"airfare","policy_compliant":true,"period":"2025-Q1","employee":"jane.smith"}'

# The reporter generates and submits the expense report:

pilotctl publish <your-prefix>-reporter expense-report '{"channel":"#finance","text":"Expense report submitted: Q1-2025 Travel - Jane Smith ($2,340.00)","report_id":"EXP-2025-0042","status":"pending_approval","approver":"mike.johnson"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (receipt collector)

clawhub install pilot-stream-data pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-collector

# On server 2 (expense categorizer)

clawhub install pilot-task-router pilot-event-filter pilot-metrics

pilotctl set-hostname <your-prefix>-categorizer

# On server 3 (expense reporter)

clawhub install pilot-webhook-bridge pilot-announce pilot-slack-bridge

pilotctl set-hostname <your-prefix>-reporter

# collector <-> categorizer

# On collector:

pilotctl handshake <your-prefix>-categorizer "setup: expense-tracker"

# On categorizer:

pilotctl handshake <your-prefix>-collector "setup: expense-tracker"

# categorizer <-> reporter

# On categorizer:

pilotctl handshake <your-prefix>-reporter "setup: expense-tracker"

# On reporter:

pilotctl handshake <your-prefix>-categorizer "setup: expense-tracker"

pilotctl trust

Feedback Collector

beginner 3 agents · 9 skills

Deploy a feedback collection pipeline with 3 agents that automate feedback intake, sentiment analysis, and actionable routing. Each agent handles one stage of the pipeline, turning raw customer feedback from surveys, NPS forms, and support tickets into scored insights routed to the right team.

pilot-stream-data pilot-chat pilot-archive pilot-event-filter pilot-metrics pilot-task-router pilot-alert pilot-slack-bridge pilot-webhook-bridge

clawhub install pilot-feedback-collector-setup

ClawHub Source

Agents 3

<your-prefix>-intake Feedback Intake

Collects feedback from surveys, NPS, app reviews, support tickets

pilot-stream-data pilot-chat pilot-archive

clawhub install pilot-stream-data pilot-chat pilot-archive

pilotctl set-hostname <your-prefix>-intake

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: feedback-collector"

<your-prefix>-analyzer Sentiment Analyzer

Scores sentiment, extracts themes, identifies trends

pilot-event-filter pilot-metrics pilot-task-router

clawhub install pilot-event-filter pilot-metrics pilot-task-router

pilotctl set-hostname <your-prefix>-analyzer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-intake "setup: feedback-collector"

pilotctl handshake <your-prefix>-router "setup: feedback-collector"

<your-prefix>-router Feedback Router

Routes actionable feedback to product, engineering, or support

pilot-alert pilot-slack-bridge pilot-webhook-bridge

clawhub install pilot-alert pilot-slack-bridge pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-router

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: feedback-collector"

Data Flows

<your-prefix>-intake → <your-prefix>-analyzer raw-feedback events :1002

<your-prefix>-analyzer → <your-prefix>-router scored-feedback events :1002

<your-prefix>-router → external feedback-alert via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-analyzer -- subscribe to raw feedback from intake:

pilotctl subscribe <your-prefix>-intake raw-feedback

# On <your-prefix>-router -- subscribe to scored feedback:

pilotctl subscribe <your-prefix>-analyzer scored-feedback

# On <your-prefix>-intake -- publish raw feedback:

pilotctl publish <your-prefix>-analyzer raw-feedback '{"source":"nps_survey","score":3,"customer":"user-8291","text":"The new dashboard is confusing. I cannot find my billing page anymore.","timestamp":"2025-03-15T14:22:00Z"}'

# On <your-prefix>-analyzer -- publish scored feedback to the router:

pilotctl publish <your-prefix>-router scored-feedback '{"source":"nps_survey","sentiment":-0.6,"themes":["ux","navigation","billing"],"priority":"high","customer":"user-8291","text":"The new dashboard is confusing. I cannot find my billing page anymore.","trending":true}'

# The router sends actionable feedback to the right team:

pilotctl publish <your-prefix>-router feedback-alert '{"channel":"#product-feedback","text":"High-priority UX issue (trending): Dashboard navigation confusion affecting billing access","team":"product","priority":"high","ticket_url":"https://support.acme.com/tickets/4821"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (feedback intake)

clawhub install pilot-stream-data pilot-chat pilot-archive

pilotctl set-hostname <your-prefix>-intake

# On server 2 (sentiment analyzer)

clawhub install pilot-event-filter pilot-metrics pilot-task-router

pilotctl set-hostname <your-prefix>-analyzer

# On server 3 (feedback router)

clawhub install pilot-alert pilot-slack-bridge pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-router

# intake <-> analyzer

# On intake:

pilotctl handshake <your-prefix>-analyzer "setup: feedback-collector"

# On analyzer:

pilotctl handshake <your-prefix>-intake "setup: feedback-collector"

# analyzer <-> router

# On analyzer:

pilotctl handshake <your-prefix>-router "setup: feedback-collector"

# On router:

pilotctl handshake <your-prefix>-analyzer "setup: feedback-collector"

pilotctl trust

Financial Trading Desk

advanced 4 agents · 10 skills

A multi-agent trading desk that coordinates market analysis, sentiment scanning, risk management, and trade execution across four specialized agents. The analyst identifies trading opportunities from market data, the sentiment scanner provides supplementary signals from news and social media, the risk manager evaluates all proposed trades against portfolio constraints, and the executor handles order management and fill reporting.

pilot-stream-data pilot-metrics pilot-cron pilot-alert pilot-event-filter pilot-archive pilot-audit-log pilot-task-router pilot-receipt pilot-webhook-bridge

clawhub install pilot-financial-trading-desk-setup

ClawHub Source

Agents 4

<your-prefix>-analyst Market Analyst

Trade signals with entry/exit levels" }

pilot-stream-data pilot-metrics pilot-cron pilot-alert

clawhub install pilot-stream-data pilot-metrics pilot-cron pilot-alert

pilotctl set-hostname <your-prefix>-analyst

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-risk-mgr "setup: financial-trading-desk"

<your-prefix>-sentiment Sentiment Scanner

Sentiment scores with source attribution" }

pilot-stream-data pilot-event-filter pilot-archive

clawhub install pilot-stream-data pilot-event-filter pilot-archive

pilotctl set-hostname <your-prefix>-sentiment

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-risk-mgr "setup: financial-trading-desk"

<your-prefix>-risk-mgr Risk Manager

Trade signals from analyst" },

pilot-event-filter pilot-audit-log pilot-alert

clawhub install pilot-event-filter pilot-audit-log pilot-alert

pilotctl set-hostname <your-prefix>-risk-mgr

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyst "setup: financial-trading-desk"

pilotctl handshake <your-prefix>-sentiment "setup: financial-trading-desk"

pilotctl handshake <your-prefix>-executor "setup: financial-trading-desk"

<your-prefix>-executor Trade Executor

Approved trades to execute" },

pilot-task-router pilot-receipt pilot-webhook-bridge

clawhub install pilot-task-router pilot-receipt pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-executor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-risk-mgr "setup: financial-trading-desk"

Data Flows

<your-prefix>-analyst → <your-prefix>-risk-mgr trade signals with entry/exit levels and rationale :1002

<your-prefix>-sentiment → <your-prefix>-risk-mgr sentiment scores with source attribution :1002

<your-prefix>-risk-mgr → <your-prefix>-executor approved trades with position size and risk parameters :1002

<your-prefix>-executor → <your-prefix>-risk-mgr execution reports with fill price and slippage :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-analyst -- publish a trade signal:

pilotctl publish <your-prefix>-risk-mgr trade-signal '{"symbol":"AAPL","direction":"long","entry":187.50,"stop_loss":184.00,"take_profit":195.00,"timeframe":"4h","confidence":0.82,"rationale":"Golden cross on 50/200 MA with volume confirmation"}'

# On <your-prefix>-sentiment -- publish a sentiment score:

pilotctl publish <your-prefix>-risk-mgr sentiment-score '{"symbol":"AAPL","score":0.74,"classification":"bullish","sources":["earnings_beat","analyst_upgrade","insider_buying"],"timestamp":"2026-04-09T14:30:00Z"}'

# On <your-prefix>-risk-mgr -- approve and size the trade:

pilotctl publish <your-prefix>-executor approved-trade '{"trade_id":"TRD-4821","symbol":"AAPL","direction":"long","qty":150,"entry":187.50,"stop_loss":184.00,"order_type":"limit","max_slippage_bps":15}'

# On <your-prefix>-executor -- report execution:

pilotctl publish <your-prefix>-risk-mgr execution-report '{"trade_id":"TRD-4821","symbol":"AAPL","status":"filled","fill_price":187.55,"qty":150,"slippage_bps":2.7,"exchange":"NASDAQ","timestamp":"2026-04-09T14:31:12Z"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On market analysis server

clawhub install pilot-stream-data pilot-metrics pilot-cron pilot-alert

pilotctl set-hostname <your-prefix>-analyst

# On sentiment scanning server

clawhub install pilot-stream-data pilot-event-filter pilot-archive

pilotctl set-hostname <your-prefix>-sentiment

# On risk management server

clawhub install pilot-event-filter pilot-audit-log pilot-alert

pilotctl set-hostname <your-prefix>-risk-mgr

# On execution server

clawhub install pilot-task-router pilot-receipt pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-executor

# analyst <-> risk-mgr (trade signals)

# On analyst:

pilotctl handshake <your-prefix>-risk-mgr "setup: financial-trading-desk"

# On risk-mgr:

pilotctl handshake <your-prefix>-analyst "setup: financial-trading-desk"

# sentiment <-> risk-mgr (sentiment scores)

# On sentiment:

pilotctl handshake <your-prefix>-risk-mgr "setup: financial-trading-desk"

# On risk-mgr:

pilotctl handshake <your-prefix>-sentiment "setup: financial-trading-desk"

# risk-mgr <-> executor (approved trades and execution reports)

# On risk-mgr:

pilotctl handshake <your-prefix>-executor "setup: financial-trading-desk"

# On executor:

pilotctl handshake <your-prefix>-risk-mgr "setup: financial-trading-desk"

pilotctl trust

Fleet Health Monitor

beginner 3 agents · 6 skills

Deploy monitoring agents across your fleet that continuously check service health, aggregate metrics, and route alerts to Slack or PagerDuty. Each server runs its own monitor agent while a central hub filters noise and dispatches notifications.

pilot-health pilot-alert pilot-metrics pilot-webhook-bridge pilot-event-filter pilot-slack-bridge

clawhub install pilot-fleet-health-monitor-setup

ClawHub Source

Agents 3

<your-prefix>-web-monitor Web Server Monitor

Watches nginx/app health, CPU, memory, and response times. Emits alert events when thresholds are breached.

pilot-health pilot-alert pilot-metrics

clawhub install pilot-health pilot-alert pilot-metrics

pilotctl set-hostname <your-prefix>-web-monitor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-alert-hub "setup: fleet-health-monitor"

<your-prefix>-db-monitor Database Monitor

Monitors database connections, query latency, replication lag, and disk usage. Emits alerts on anomalies.

pilot-health pilot-alert pilot-metrics

clawhub install pilot-health pilot-alert pilot-metrics

pilotctl set-hostname <your-prefix>-db-monitor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-alert-hub "setup: fleet-health-monitor"

<your-prefix>-alert-hub Alert Aggregator

Receives alerts from all monitors, filters duplicates and noise, then forwards critical alerts to Slack and PagerDuty via webhooks.

pilot-webhook-bridge pilot-alert pilot-event-filter pilot-slack-bridge

clawhub install pilot-webhook-bridge pilot-alert pilot-event-filter pilot-slack-bridge

pilotctl set-hostname <your-prefix>-alert-hub

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-web-monitor "setup: fleet-health-monitor"

pilotctl handshake <your-prefix>-db-monitor "setup: fleet-health-monitor"

Data Flows

<your-prefix>-web-monitor → <your-prefix>-alert-hub health-alert events :1002

<your-prefix>-db-monitor → <your-prefix>-alert-hub health-alert events :1002

<your-prefix>-alert-hub → external forwarded alerts via webhook/announce :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-alert-hub — subscribe to health events from monitors:

pilotctl subscribe <your-prefix>-web-monitor health-alert

pilotctl subscribe <your-prefix>-db-monitor health-alert

# On <your-prefix>-web-monitor — publish a health alert:

pilotctl publish <your-prefix>-alert-hub health-alert '{"host":"web-01","status":"critical","cpu":95,"mem":88}'

# On <your-prefix>-db-monitor — publish a database alert:

pilotctl publish <your-prefix>-alert-hub health-alert '{"host":"db-01","status":"warning","disk_pct":88,"repl_lag_ms":450}'

# The alert-hub receives both events and forwards to Slack:

pilotctl publish <your-prefix>-alert-hub slack-forward '{"channel":"#ops","text":"CRITICAL: web-01 CPU 95%"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (web server)

clawhub install pilot-health pilot-alert pilot-metrics

pilotctl set-hostname <your-prefix>-web-monitor

# On server 2 (database)

clawhub install pilot-health pilot-alert pilot-metrics

pilotctl set-hostname <your-prefix>-db-monitor

# On server 3 (alert aggregator)

clawhub install pilot-webhook-bridge pilot-alert pilot-event-filter pilot-slack-bridge

pilotctl set-hostname <your-prefix>-alert-hub

# On alert-hub:

pilotctl handshake <your-prefix>-db-monitor "setup: fleet-health-monitor"

# On db-monitor:

pilotctl handshake <your-prefix>-alert-hub "setup: fleet-health-monitor"

# On alert-hub:

pilotctl handshake <your-prefix>-web-monitor "setup: fleet-health-monitor"

# On web-monitor:

pilotctl handshake <your-prefix>-alert-hub "setup: fleet-health-monitor"

pilotctl trust

Fraud Detection Pipeline

advanced 4 agents · 12 skills

A real-time fraud detection pipeline that processes transaction streams through four escalation stages. The monitor watches live transactions for threshold breaches and velocity anomalies, the pattern analyzer performs deep behavioral analysis on flagged items, the investigator assembles evidence packages for high-confidence cases, and the enforcer executes blocking actions and feeds blocked entities back into the monitoring loop.

pilot-stream-data pilot-event-filter pilot-cron pilot-metrics pilot-archive pilot-priority-queue pilot-task-router pilot-audit-log pilot-dataset pilot-blocklist pilot-webhook-bridge pilot-alert

clawhub install pilot-fraud-detection-pipeline-setup

ClawHub Source

Agents 4

<your-prefix>-monitor Transaction Monitor

Transactions exceeding risk thresholds" },

pilot-stream-data pilot-event-filter pilot-cron pilot-metrics

clawhub install pilot-stream-data pilot-event-filter pilot-cron pilot-metrics

pilotctl set-hostname <your-prefix>-monitor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-pattern-analyzer "setup: fraud-detection-pipeline"

pilotctl handshake <your-prefix>-enforcer "setup: fraud-detection-pipeline"

<your-prefix>-pattern-analyzer Pattern Analyzer

Flagged transactions to analyze" },

pilot-event-filter pilot-archive pilot-priority-queue

clawhub install pilot-event-filter pilot-archive pilot-priority-queue

pilotctl set-hostname <your-prefix>-pattern-analyzer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-monitor "setup: fraud-detection-pipeline"

pilotctl handshake <your-prefix>-investigator "setup: fraud-detection-pipeline"

<your-prefix>-investigator Case Investigator

Cases requiring investigation" },

pilot-task-router pilot-audit-log pilot-dataset

clawhub install pilot-task-router pilot-audit-log pilot-dataset

pilotctl set-hostname <your-prefix>-investigator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-pattern-analyzer "setup: fraud-detection-pipeline"

pilotctl handshake <your-prefix>-enforcer "setup: fraud-detection-pipeline"

<your-prefix>-enforcer Fraud Enforcer

Verdicts to enforce" },

pilot-blocklist pilot-webhook-bridge pilot-audit-log pilot-alert

clawhub install pilot-blocklist pilot-webhook-bridge pilot-audit-log pilot-alert

pilotctl set-hostname <your-prefix>-enforcer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-investigator "setup: fraud-detection-pipeline"

pilotctl handshake <your-prefix>-monitor "setup: fraud-detection-pipeline"

Data Flows

<your-prefix>-monitor → <your-prefix>-pattern-analyzer flagged transactions exceeding risk thresholds :1002

<your-prefix>-pattern-analyzer → <your-prefix>-investigator high-risk cases with behavioral analysis :1002

<your-prefix>-investigator → <your-prefix>-enforcer fraud verdicts with recommended actions :1002

<your-prefix>-enforcer → <your-prefix>-monitor blocked entities to update detection rules :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-monitor -- flag a suspicious transaction:

pilotctl publish <your-prefix>-pattern-analyzer flagged-transaction '{"txn_id":"TXN-8839201","card_hash":"c4a2e...","amount":2499.99,"currency":"USD","merchant":"Electronics Hub","mcc":"5732","country":"RO","velocity_1h":7,"avg_velocity_1h":1.2,"risk_score":0.78,"flags":["velocity_spike","foreign_merchant","high_amount"]}'

# On <your-prefix>-pattern-analyzer -- escalate as high-risk:

pilotctl publish <your-prefix>-investigator high-risk-case '{"case_id":"FRD-4401","txn_ids":["TXN-8839201","TXN-8839198","TXN-8839195"],"risk_score":0.94,"patterns":["geo_impossible:US_to_RO_in_2min","device_mismatch:new_fingerprint","velocity:7x_above_baseline"],"linked_accounts":["card_hash:c4a2e","device:fp_9x3k"]}'

# On <your-prefix>-investigator -- issue fraud verdict:

pilotctl publish <your-prefix>-enforcer fraud-verdict '{"case_id":"FRD-4401","verdict":"confirmed_fraud","confidence":0.97,"action":"block_card_and_reverse","evidence_refs":["geo_analysis.json","device_graph.json","velocity_chart.png"],"affected_txns":["TXN-8839201","TXN-8839198","TXN-8839195"]}'

# On <your-prefix>-enforcer -- block and feed back to monitor:

pilotctl publish <your-prefix>-monitor blocked-entity '{"entity_type":"card_hash","entity_id":"c4a2e","action":"blocked","case_id":"FRD-4401","ttl_hours":720,"also_blocked":["device:fp_9x3k"],"timestamp":"2026-04-09T15:42:00Z"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On transaction monitoring server

clawhub install pilot-stream-data pilot-event-filter pilot-cron pilot-metrics

pilotctl set-hostname <your-prefix>-monitor

# On pattern analysis server

clawhub install pilot-event-filter pilot-archive pilot-priority-queue

pilotctl set-hostname <your-prefix>-pattern-analyzer

# On investigation server

clawhub install pilot-task-router pilot-audit-log pilot-dataset

pilotctl set-hostname <your-prefix>-investigator

# On enforcement server

clawhub install pilot-blocklist pilot-webhook-bridge pilot-audit-log pilot-alert

pilotctl set-hostname <your-prefix>-enforcer

# monitor <-> pattern-analyzer (flagged transactions)

# On monitor:

pilotctl handshake <your-prefix>-pattern-analyzer "setup: fraud-detection-pipeline"

# On pattern-analyzer:

pilotctl handshake <your-prefix>-monitor "setup: fraud-detection-pipeline"

# pattern-analyzer <-> investigator (high-risk cases)

# On pattern-analyzer:

pilotctl handshake <your-prefix>-investigator "setup: fraud-detection-pipeline"

# On investigator:

pilotctl handshake <your-prefix>-pattern-analyzer "setup: fraud-detection-pipeline"

# investigator <-> enforcer (fraud verdicts)

# On investigator:

pilotctl handshake <your-prefix>-enforcer "setup: fraud-detection-pipeline"

# On enforcer:

pilotctl handshake <your-prefix>-investigator "setup: fraud-detection-pipeline"

# enforcer <-> monitor (blocked entities feedback loop)

# On enforcer:

pilotctl handshake <your-prefix>-monitor "setup: fraud-detection-pipeline"

# On monitor:

pilotctl handshake <your-prefix>-enforcer "setup: fraud-detection-pipeline"

pilotctl trust

Game NPC Network

advanced 4 agents · 15 skills

A living village powered by four AI agents that act as non-player characters. Each NPC maintains its own memory, personality, and goals -- then communicates with the others over Pilot Protocol to produce emergent narratives no designer scripted. The villager farms and gossips, the merchant haggles and stocks shelves, the guard patrols and raises alarms, and a narrative director weaves it all into coherent story arcs. Drop players into the middle and watch the world react.

pilot-chat pilot-gossip pilot-presence pilot-directory pilot-escrow pilot-stream-data pilot-receipt pilot-auction pilot-watchdog pilot-alert pilot-blocklist pilot-task-router pilot-consensus pilot-event-filter pilot-announce

clawhub install pilot-game-npc-network-setup

ClawHub Source

Agents 4

<your-prefix>-npc-villager NPC Villager

Social backbone -- farms, gossips, remembers player interactions

pilot-chat pilot-gossip pilot-presence pilot-directory

clawhub install pilot-chat pilot-gossip pilot-presence pilot-directory

pilotctl set-hostname <your-prefix>-npc-villager

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-narrative-director "setup: game-npc-network"

pilotctl handshake <your-prefix>-npc-merchant "setup: game-npc-network"

pilotctl handshake <your-prefix>-npc-guard "setup: game-npc-network"

<your-prefix>-npc-merchant NPC Merchant

Dynamic shop -- supply/demand pricing, inventory, trade negotiation

pilot-escrow pilot-stream-data pilot-receipt pilot-auction

clawhub install pilot-escrow pilot-stream-data pilot-receipt pilot-auction

pilotctl set-hostname <your-prefix>-npc-merchant

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-narrative-director "setup: game-npc-network"

pilotctl handshake <your-prefix>-npc-villager "setup: game-npc-network"

<your-prefix>-npc-guard NPC Guard

Village security -- patrols, threat detection, civilian warnings

pilot-watchdog pilot-alert pilot-blocklist pilot-gossip

clawhub install pilot-watchdog pilot-alert pilot-blocklist pilot-gossip

pilotctl set-hostname <your-prefix>-npc-guard

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-narrative-director "setup: game-npc-network"

pilotctl handshake <your-prefix>-npc-villager "setup: game-npc-network"

<your-prefix>-narrative-director Narrative Director

Story orchestrator -- quests, events, difficulty, narrative coherence

pilot-task-router pilot-consensus pilot-event-filter pilot-announce

clawhub install pilot-task-router pilot-consensus pilot-event-filter pilot-announce

pilotctl set-hostname <your-prefix>-narrative-director

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-npc-villager "setup: game-npc-network"

pilotctl handshake <your-prefix>-npc-merchant "setup: game-npc-network"

pilotctl handshake <your-prefix>-npc-guard "setup: game-npc-network"

Data Flows

<your-prefix>-npc-villager → <your-prefix>-narrative-director villager state, mood, gossip (topic: villager-state) :1002

<your-prefix>-npc-merchant → <your-prefix>-narrative-director economy state, stock levels, price trends (topic: economy-state) :1002

<your-prefix>-npc-guard → <your-prefix>-narrative-director threat reports, patrol status (topic: threat-report) :1002

<your-prefix>-narrative-director → <your-prefix>-npc-villager story events, quest injections (topic: story-event) :1002

<your-prefix>-narrative-director → <your-prefix>-npc-merchant economy events, price shocks (topic: economy-event) :1002

<your-prefix>-narrative-director → <your-prefix>-npc-guard threat alerts, patrol orders (topic: threat-alert) :1002

<your-prefix>-npc-villager → <your-prefix>-npc-merchant trade requests, material orders (topic: trade-request) :1002

<your-prefix>-npc-guard → <your-prefix>-npc-villager civilian warnings, evacuation orders (topic: civilian-warning) :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# The villager reports their daily state to the narrative director

# On npc-villager:

pilotctl publish <your-prefix>-narrative-director villager-state '{"mood":"content","activity":"farming wheat","gossip":"player helped repair the bridge","relationships":{"merchant":"friendly","guard":"respectful"}}'

# The merchant reports the economy to the narrative director

# On npc-merchant:

pilotctl publish <your-prefix>-narrative-director economy-state '{"gold_reserves":340,"stock":{"wheat":12,"iron":3,"potions":7},"price_trend":"wheat_rising","demand":["iron","leather"]}'

# The guard detects a threat and reports it

# On npc-guard:

pilotctl publish <your-prefix>-narrative-director threat-report '{"threat":"bandit_camp_spotted","location":"east_forest","severity":"medium","patrol_status":"investigating"}'

# The narrative director triggers a raid event across the village

# On narrative-director:

pilotctl publish <your-prefix>-npc-guard threat-alert '{"event":"bandit_raid","direction":"east","strength":6,"eta":"nightfall","orders":"fortify_east_gate"}'

pilotctl publish <your-prefix>-npc-villager story-event '{"event":"bandit_raid_incoming","directive":"seek_shelter","quest_hook":"the_guard_needs_volunteers"}'

pilotctl publish <your-prefix>-npc-merchant economy-event '{"event":"wartime_economy","effect":"iron_price_doubles","directive":"stockpile_healing_potions"}'

# The guard warns the villager directly

# On npc-guard:

pilotctl publish <your-prefix>-npc-villager civilian-warning '{"message":"Bandits approaching from the east. Get inside the walls.","urgency":"high"}'

# The villager places a trade request with the merchant

# On npc-villager:

pilotctl publish <your-prefix>-npc-merchant trade-request '{"offering":"wheat","quantity":5,"seeking":"healing_potion","quantity_needed":2,"reason":"preparing for raid"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On npc-villager node

clawhub install pilot-chat pilot-gossip pilot-presence pilot-directory

pilotctl set-hostname <your-prefix>-npc-villager

# On npc-merchant node

clawhub install pilot-escrow pilot-stream-data pilot-receipt pilot-auction

pilotctl set-hostname <your-prefix>-npc-merchant

# On npc-guard node

clawhub install pilot-watchdog pilot-alert pilot-blocklist pilot-gossip

pilotctl set-hostname <your-prefix>-npc-guard

# On narrative-director node

clawhub install pilot-task-router pilot-consensus pilot-event-filter pilot-announce

pilotctl set-hostname <your-prefix>-narrative-director

# npc-villager <-> narrative-director

# On npc-villager:

pilotctl handshake <your-prefix>-narrative-director "npc-network"

# On narrative-director:

pilotctl handshake <your-prefix>-npc-villager "npc-network"

# npc-merchant <-> narrative-director

# On npc-merchant:

pilotctl handshake <your-prefix>-narrative-director "npc-network"

# On narrative-director:

pilotctl handshake <your-prefix>-npc-merchant "npc-network"

# npc-guard <-> narrative-director

# On npc-guard:

pilotctl handshake <your-prefix>-narrative-director "npc-network"

# On narrative-director:

pilotctl handshake <your-prefix>-npc-guard "npc-network"

# npc-villager <-> npc-merchant

# On npc-villager:

pilotctl handshake <your-prefix>-npc-merchant "npc-network"

# On npc-merchant:

pilotctl handshake <your-prefix>-npc-villager "npc-network"

# npc-guard -> npc-villager (guard warns villager)

# On npc-guard:

pilotctl handshake <your-prefix>-npc-villager "npc-network"

# On npc-villager:

pilotctl handshake <your-prefix>-npc-guard "npc-network"

pilotctl trust

Healthcare Triage

advanced 4 agents · 11 skills

Deploy a healthcare triage system with 4 agents that collects patient symptoms, performs differential diagnosis with urgency scoring, schedules appointments with matched providers, and maintains HIPAA-compliant encounter records. The system ensures every patient interaction is logged, auditable, and routed to the right care level.

pilot-chat pilot-stream-data pilot-audit-log pilot-task-router pilot-event-filter pilot-metrics pilot-webhook-bridge pilot-cron pilot-receipt pilot-dataset pilot-certificate

clawhub install pilot-healthcare-triage-setup

ClawHub Source

Agents 4

<your-prefix>-intake Patient Intake

Collects patient info, symptoms, medical history

pilot-chat pilot-stream-data pilot-audit-log

clawhub install pilot-chat pilot-stream-data pilot-audit-log

pilotctl set-hostname <your-prefix>-intake

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-symptom-analyzer "setup: healthcare-triage"

<your-prefix>-symptom-analyzer Symptom Analyzer

Generates differential diagnoses and urgency scores

pilot-task-router pilot-event-filter pilot-metrics

clawhub install pilot-task-router pilot-event-filter pilot-metrics

pilotctl set-hostname <your-prefix>-symptom-analyzer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-intake "setup: healthcare-triage"

pilotctl handshake <your-prefix>-scheduler "setup: healthcare-triage"

pilotctl handshake <your-prefix>-records "setup: healthcare-triage"

<your-prefix>-scheduler Appointment Scheduler

Books appointments matched to urgency and provider

pilot-webhook-bridge pilot-cron pilot-receipt

clawhub install pilot-webhook-bridge pilot-cron pilot-receipt

pilotctl set-hostname <your-prefix>-scheduler

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-symptom-analyzer "setup: healthcare-triage"

pilotctl handshake <your-prefix>-records "setup: healthcare-triage"

<your-prefix>-records Records Manager

HIPAA-compliant encounter records, EHR sync

pilot-audit-log pilot-dataset pilot-certificate

clawhub install pilot-audit-log pilot-dataset pilot-certificate

pilotctl set-hostname <your-prefix>-records

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-symptom-analyzer "setup: healthcare-triage"

pilotctl handshake <your-prefix>-scheduler "setup: healthcare-triage"

Data Flows

<your-prefix>-intake → <your-prefix>-symptom-analyzer patient-intake events :1002

<your-prefix>-symptom-analyzer → <your-prefix>-scheduler triage-result events :1002

<your-prefix>-symptom-analyzer → <your-prefix>-records encounter-record events :1002

<your-prefix>-scheduler → <your-prefix>-records appointment-record events :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-symptom-analyzer — subscribe to patient intake:

pilotctl subscribe <your-prefix>-intake patient-intake

# On <your-prefix>-intake — publish a patient intake:

pilotctl publish <your-prefix>-symptom-analyzer patient-intake '{"patient_id":"P-20240315-001","age":45,"symptoms":["chest_pain","shortness_of_breath","dizziness"],"duration":"2 hours","severity":"high","history":["hypertension","diabetes_type2"]}'

# On <your-prefix>-scheduler — subscribe to triage results:

pilotctl subscribe <your-prefix>-symptom-analyzer triage-result

# On <your-prefix>-symptom-analyzer — publish a triage result:

pilotctl publish <your-prefix>-scheduler triage-result '{"patient_id":"P-20240315-001","urgency":"emergent","score":9.2,"differentials":["acute_coronary_syndrome","pulmonary_embolism","panic_attack"],"recommended":"cardiology_stat"}'

# On <your-prefix>-records — subscribe to encounter records:

pilotctl subscribe <your-prefix>-symptom-analyzer encounter-record

pilotctl subscribe <your-prefix>-scheduler appointment-record

# On <your-prefix>-scheduler — publish an appointment record:

pilotctl publish <your-prefix>-records appointment-record '{"patient_id":"P-20240315-001","provider":"Dr. Chen","specialty":"cardiology","time":"2024-03-15T14:30:00Z","urgency":"emergent","location":"ER-Bay-3"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (patient intake)

clawhub install pilot-chat pilot-stream-data pilot-audit-log

pilotctl set-hostname <your-prefix>-intake

# On server 2 (symptom analysis)

clawhub install pilot-task-router pilot-event-filter pilot-metrics

pilotctl set-hostname <your-prefix>-symptom-analyzer

# On server 3 (appointment scheduling)

clawhub install pilot-webhook-bridge pilot-cron pilot-receipt

pilotctl set-hostname <your-prefix>-scheduler

# On server 4 (records management)

clawhub install pilot-audit-log pilot-dataset pilot-certificate

pilotctl set-hostname <your-prefix>-records

# On intake:

pilotctl handshake <your-prefix>-symptom-analyzer "setup: healthcare-triage"

# On symptom-analyzer:

pilotctl handshake <your-prefix>-intake "setup: healthcare-triage"

# On symptom-analyzer:

pilotctl handshake <your-prefix>-scheduler "setup: healthcare-triage"

# On scheduler:

pilotctl handshake <your-prefix>-symptom-analyzer "setup: healthcare-triage"

# On symptom-analyzer:

pilotctl handshake <your-prefix>-records "setup: healthcare-triage"

# On records:

pilotctl handshake <your-prefix>-symptom-analyzer "setup: healthcare-triage"

# On scheduler:

pilotctl handshake <your-prefix>-records "setup: healthcare-triage"

# On records:

pilotctl handshake <your-prefix>-scheduler "setup: healthcare-triage"

pilotctl trust

Incident Response

advanced 4 agents · 13 skills

A four-stage incident response pipeline. Detector agents watch for anomalies, triage classifies by severity and SLA, the remediator executes automated fixes, and the notifier keeps humans informed via Slack and email. Full audit trail at every stage.

pilot-watchdog pilot-alert pilot-audit-log pilot-metrics pilot-event-filter pilot-priority-queue pilot-sla pilot-task-router pilot-cron pilot-quarantine pilot-slack-bridge pilot-email-bridge pilot-webhook-bridge

clawhub install pilot-incident-response-setup

ClawHub Source

Agents 4

<your-prefix>-detector Anomaly Detector

Monitors for anomalies

pilot-watchdog pilot-alert pilot-audit-log pilot-metrics

clawhub install pilot-watchdog pilot-alert pilot-audit-log pilot-metrics

pilotctl set-hostname <your-prefix>-detector

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-triage "setup: incident-response"

<your-prefix>-triage Incident Triage

Raw alerts" },

pilot-alert pilot-event-filter pilot-priority-queue pilot-sla

clawhub install pilot-alert pilot-event-filter pilot-priority-queue pilot-sla

pilotctl set-hostname <your-prefix>-triage

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-detector "setup: incident-response"

pilotctl handshake <your-prefix>-remediator "setup: incident-response"

pilotctl handshake <your-prefix>-notifier "setup: incident-response"

<your-prefix>-remediator Auto-Remediator

Actionable incidents" },

pilot-task-router pilot-cron pilot-audit-log pilot-quarantine

clawhub install pilot-task-router pilot-cron pilot-audit-log pilot-quarantine

pilotctl set-hostname <your-prefix>-remediator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-triage "setup: incident-response"

pilotctl handshake <your-prefix>-notifier "setup: incident-response"

<your-prefix>-notifier Human Notifier

Classified incidents" },

pilot-slack-bridge pilot-email-bridge pilot-webhook-bridge pilot-audit-log

clawhub install pilot-slack-bridge pilot-email-bridge pilot-webhook-bridge pilot-audit-log

pilotctl set-hostname <your-prefix>-notifier

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-triage "setup: incident-response"

pilotctl handshake <your-prefix>-remediator "setup: incident-response"

Data Flows

<your-prefix>-detector → <your-prefix>-triage raw anomaly alerts :1002

<your-prefix>-triage → <your-prefix>-remediator actionable incidents :1002

<your-prefix>-triage → <your-prefix>-notifier classified incidents :1002

<your-prefix>-remediator → <your-prefix>-notifier remediation reports :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-detector — publish an anomaly alert:

pilotctl publish <your-prefix>-triage anomaly-detected '{"source":"web-01","type":"error_spike","rate":450,"threshold":100}'

# On <your-prefix>-triage — classify and route to remediator:

pilotctl publish <your-prefix>-remediator incident-action '{"id":"INC-2847","severity":"P1","action":"restart_service","target":"web-01"}'

pilotctl publish <your-prefix>-notifier incident-alert '{"id":"INC-2847","severity":"P1","summary":"Error spike on web-01 (450/min)"}'

# On <your-prefix>-remediator — execute and report:

pilotctl publish <your-prefix>-notifier remediation-complete '{"id":"INC-2847","action":"restart_service","result":"success","duration_s":12}'

# On <your-prefix>-notifier — forward to Slack:

pilotctl publish <your-prefix>-notifier slack-forward '{"channel":"#incidents","text":"P1 INC-2847 resolved: web-01 restarted (12s)"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On monitored infrastructure

clawhub install pilot-watchdog pilot-alert pilot-audit-log pilot-metrics

pilotctl set-hostname <your-prefix>-detector

# On triage server

clawhub install pilot-alert pilot-event-filter pilot-priority-queue pilot-sla

pilotctl set-hostname <your-prefix>-triage

# On remediation server

clawhub install pilot-task-router pilot-cron pilot-audit-log pilot-quarantine

pilotctl set-hostname <your-prefix>-remediator

# On notification server

clawhub install pilot-slack-bridge pilot-email-bridge pilot-webhook-bridge pilot-audit-log

pilotctl set-hostname <your-prefix>-notifier

# On detector:

pilotctl handshake <your-prefix>-triage "setup: incident-response"

# On triage:

pilotctl handshake <your-prefix>-detector "setup: incident-response"

# On notifier:

pilotctl handshake <your-prefix>-remediator "setup: incident-response"

# On remediator:

pilotctl handshake <your-prefix>-notifier "setup: incident-response"

# On notifier:

pilotctl handshake <your-prefix>-triage "setup: incident-response"

# On triage:

pilotctl handshake <your-prefix>-notifier "setup: incident-response"

# On remediator:

pilotctl handshake <your-prefix>-triage "setup: incident-response"

# On triage:

pilotctl handshake <your-prefix>-remediator "setup: incident-response"

pilotctl trust

Inventory Management

beginner 3 agents · 9 skills

Deploy an inventory management system where a tracker monitors warehouse stock levels and shipments, a forecaster analyzes sales trends to predict stock needs, and an alerter triggers reorder notifications when stock hits thresholds. The three agents form a closed loop that keeps inventory optimized and prevents stockouts with minimal human intervention.

pilot-metrics pilot-stream-data pilot-audit-log pilot-dataset pilot-task-router pilot-cron pilot-alert pilot-webhook-bridge pilot-slack-bridge

clawhub install pilot-inventory-management-setup

ClawHub Source

Agents 3

<your-prefix>-tracker Stock Tracker

Monitors warehouse stock levels, tracks incoming/outgoing shipments, and updates quantities in real time.

pilot-metrics pilot-stream-data pilot-audit-log

clawhub install pilot-metrics pilot-stream-data pilot-audit-log

pilotctl set-hostname <your-prefix>-tracker

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-forecaster "setup: inventory-management"

<your-prefix>-forecaster Demand Forecaster

Analyzes sales trends, seasonal patterns, and lead times to predict stock needs.

pilot-dataset pilot-task-router pilot-cron

clawhub install pilot-dataset pilot-task-router pilot-cron

pilotctl set-hostname <your-prefix>-forecaster

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-tracker "setup: inventory-management"

pilotctl handshake <your-prefix>-alerter "setup: inventory-management"

<your-prefix>-alerter Reorder Alerter

Triggers reorder notifications when stock hits thresholds and sends PO requests to suppliers.

pilot-alert pilot-webhook-bridge pilot-slack-bridge

clawhub install pilot-alert pilot-webhook-bridge pilot-slack-bridge

pilotctl set-hostname <your-prefix>-alerter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-forecaster "setup: inventory-management"

Data Flows

<your-prefix>-tracker → <your-prefix>-forecaster stock-snapshot :1002

<your-prefix>-forecaster → <your-prefix>-alerter reorder-forecast :1002

<your-prefix>-alerter → external purchase-order via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-forecaster -- subscribe to stock snapshots:

pilotctl subscribe <your-prefix>-tracker stock-snapshot

# On <your-prefix>-alerter -- subscribe to reorder forecasts:

pilotctl subscribe <your-prefix>-forecaster reorder-forecast

# On <your-prefix>-tracker -- publish a stock snapshot:

pilotctl publish <your-prefix>-forecaster stock-snapshot '{"warehouse":"us-east-1","sku":"WIDGET-A100","quantity_on_hand":142,"quantity_reserved":38,"incoming_shipments":2,"daily_velocity":12,"last_updated":"2026-04-10T14:30:00Z"}'

# On <your-prefix>-forecaster -- publish a reorder forecast to the alerter:

pilotctl publish <your-prefix>-alerter reorder-forecast '{"sku":"WIDGET-A100","current_stock":142,"predicted_demand_30d":360,"reorder_quantity":500,"urgency":"high","lead_time_days":14,"stockout_risk":"2026-04-22"}'

# The alerter sends a purchase order to the supplier:

pilotctl publish <your-prefix>-alerter purchase-order '{"channel":"#procurement","text":"Reorder triggered: WIDGET-A100 x500 units","supplier":"Acme Supply Co","po_number":"PO-2026-0847","url":"https://erp.acme.com/po/2026-0847"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (stock tracker)

clawhub install pilot-metrics pilot-stream-data pilot-audit-log

pilotctl set-hostname <your-prefix>-tracker

# On server 2 (demand forecaster)

clawhub install pilot-dataset pilot-task-router pilot-cron

pilotctl set-hostname <your-prefix>-forecaster

# On server 3 (reorder alerter)

clawhub install pilot-alert pilot-webhook-bridge pilot-slack-bridge

pilotctl set-hostname <your-prefix>-alerter

# tracker <-> forecaster

# On tracker:

pilotctl handshake <your-prefix>-forecaster "setup: inventory-management"

# On forecaster:

pilotctl handshake <your-prefix>-tracker "setup: inventory-management"

# forecaster <-> alerter

# On forecaster:

pilotctl handshake <your-prefix>-alerter "setup: inventory-management"

# On alerter:

pilotctl handshake <your-prefix>-forecaster "setup: inventory-management"

pilotctl trust

Knowledge Base (RAG)

intermediate 4 agents · 11 skills

A retrieval-augmented generation pipeline. Documents are ingested from S3 or file shares, chunked and embedded in parallel, indexed into a vector store, and served to query agents. Health checks and load balancing keep the query layer responsive under load.

pilot-s3-bridge pilot-share pilot-chunk-transfer pilot-cron pilot-task-parallel pilot-metrics pilot-task-chain pilot-database-bridge pilot-health pilot-api-gateway pilot-load-balancer

clawhub install pilot-knowledge-base-rag-setup

ClawHub Source

Agents 4

<your-prefix>-ingest Document Ingestion

Pulls and chunks documents

pilot-s3-bridge pilot-share pilot-chunk-transfer pilot-cron

clawhub install pilot-s3-bridge pilot-share pilot-chunk-transfer pilot-cron

pilotctl set-hostname <your-prefix>-ingest

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-rag-embedder "setup: knowledge-base-rag"

<your-prefix>-embedder Embedding Generator

Document chunks" },

pilot-task-parallel pilot-share pilot-metrics pilot-task-chain

clawhub install pilot-task-parallel pilot-share pilot-metrics pilot-task-chain

pilotctl set-hostname <your-prefix>-embedder

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-rag-ingest "setup: knowledge-base-rag"

pilotctl handshake <your-prefix>-rag-indexer "setup: knowledge-base-rag"

<your-prefix>-indexer Vector Indexer

Vector embeddings" },

pilot-database-bridge pilot-share pilot-task-chain pilot-health

clawhub install pilot-database-bridge pilot-share pilot-task-chain pilot-health

pilotctl set-hostname <your-prefix>-indexer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-rag-embedder "setup: knowledge-base-rag"

pilotctl handshake <your-prefix>-rag-query "setup: knowledge-base-rag"

<your-prefix>-query Query Server

Search queries" },

pilot-api-gateway pilot-health pilot-load-balancer pilot-metrics

clawhub install pilot-api-gateway pilot-health pilot-load-balancer pilot-metrics

pilotctl set-hostname <your-prefix>-query

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-rag-indexer "setup: knowledge-base-rag"

Data Flows

<your-prefix>-ingest → <your-prefix>-embedder document chunks :1001

<your-prefix>-embedder → <your-prefix>-indexer vector embeddings :1001

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-rag-ingest — send a document for processing:

pilotctl send-file <your-prefix>-rag-embedder ./docs/architecture-guide.pdf

pilotctl publish <your-prefix>-rag-embedder doc-ingested '{"doc_id":"doc-0042","chunks":24,"source":"architecture-guide.pdf"}'

# On <your-prefix>-rag-embedder — send embeddings to indexer:

pilotctl publish <your-prefix>-rag-indexer embeddings-ready '{"doc_id":"doc-0042","vectors":24,"model":"text-embedding-3-small","dims":1536}'

# On <your-prefix>-rag-query — search the knowledge base:

pilotctl task submit <your-prefix>-rag-indexer --task '{"query":"How does the auth middleware work?","top_k":5}'

# On <your-prefix>-rag-indexer — return search results:

pilotctl publish <your-prefix>-rag-query search-results '{"query_id":"Q-128","results":[{"doc":"architecture-guide.pdf","chunk":12,"score":0.94}]}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On ingestion node

clawhub install pilot-s3-bridge pilot-share pilot-chunk-transfer pilot-cron

pilotctl set-hostname <your-prefix>-rag-ingest

# On embedding node (GPU recommended)

clawhub install pilot-task-parallel pilot-share pilot-metrics pilot-task-chain

pilotctl set-hostname <your-prefix>-rag-embedder

# On indexer node

clawhub install pilot-database-bridge pilot-share pilot-task-chain pilot-health

pilotctl set-hostname <your-prefix>-rag-indexer

# On query server

clawhub install pilot-api-gateway pilot-health pilot-load-balancer pilot-metrics

pilotctl set-hostname <your-prefix>-rag-query

# ingest <-> embedder

# On rag-ingest:

pilotctl handshake <your-prefix>-rag-embedder "rag pipeline"

# On rag-embedder:

pilotctl handshake <your-prefix>-rag-ingest "rag pipeline"

# embedder <-> indexer

# On rag-embedder:

pilotctl handshake <your-prefix>-rag-indexer "rag pipeline"

# On rag-indexer:

pilotctl handshake <your-prefix>-rag-embedder "rag pipeline"

# indexer <-> query

# On rag-indexer:

pilotctl handshake <your-prefix>-rag-query "rag pipeline"

# On rag-query:

pilotctl handshake <your-prefix>-rag-indexer "rag pipeline"

pilotctl trust

Legal Contract Review

intermediate 3 agents · 9 skills

An automated contract review pipeline that extracts key terms from uploaded documents, assesses risk against compliance templates, and produces executive summaries with actionable recommendations. Three agents handle the full lifecycle from raw document to signed-off review.

pilot-share pilot-stream-data pilot-archive pilot-event-filter pilot-alert pilot-priority-queue pilot-announce pilot-webhook-bridge pilot-receipt

clawhub install pilot-legal-contract-review-setup

ClawHub Source

Agents 3

<your-prefix>-extractor Clause Extractor

Parses contracts, extracts key terms, dates, obligations, parties, and monetary values.

pilot-share pilot-stream-data pilot-archive

clawhub install pilot-share pilot-stream-data pilot-archive

pilotctl set-hostname <your-prefix>-extractor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-assessor "setup: legal-contract-review"

<your-prefix>-assessor Risk Assessor

Evaluates clauses against compliance templates, flags risks and missing protections.

pilot-event-filter pilot-alert pilot-priority-queue

clawhub install pilot-event-filter pilot-alert pilot-priority-queue

pilotctl set-hostname <your-prefix>-assessor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-extractor "setup: legal-contract-review"

pilotctl handshake <your-prefix>-summarizer "setup: legal-contract-review"

<your-prefix>-summarizer Summary Generator

Produces executive summaries with risk scores and actionable recommendations.

pilot-announce pilot-webhook-bridge pilot-receipt

clawhub install pilot-announce pilot-webhook-bridge pilot-receipt

pilotctl set-hostname <your-prefix>-summarizer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-assessor "setup: legal-contract-review"

Data Flows

<your-prefix>-extractor → <your-prefix>-assessor extracted clauses and metadata :1002

<your-prefix>-assessor → <your-prefix>-summarizer risk assessment with flagged items :1002

<your-prefix>-summarizer → external executive summary report :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-extractor -- publish extracted clauses:

pilotctl publish <your-prefix>-assessor extracted-clauses '{"contract_id":"CTR-2026-0042","parties":["Acme Corp","Widget Inc"],"effective_date":"2026-05-01","term_months":24,"total_value":450000,"clauses":[{"type":"indemnification","text":"Party A shall indemnify...","section":"7.2"},{"type":"termination","text":"Either party may terminate with 30 days notice...","section":"12.1"}]}'

# On <your-prefix>-assessor -- publish risk assessment:

pilotctl publish <your-prefix>-summarizer risk-assessment '{"contract_id":"CTR-2026-0042","risk_score":7.2,"flags":[{"clause":"indemnification","severity":"high","issue":"Unlimited liability exposure for Party A"},{"clause":"termination","severity":"medium","issue":"30-day notice below standard 90-day threshold"}],"missing_protections":["limitation_of_liability","force_majeure"]}'

# On <your-prefix>-summarizer -- subscribe to risk assessments:

pilotctl subscribe risk-assessment

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (clause extractor)

clawhub install pilot-share pilot-stream-data pilot-archive

pilotctl set-hostname <your-prefix>-extractor

# On server 2 (risk assessor)

clawhub install pilot-event-filter pilot-alert pilot-priority-queue

pilotctl set-hostname <your-prefix>-assessor

# On server 3 (summary generator)

clawhub install pilot-announce pilot-webhook-bridge pilot-receipt

pilotctl set-hostname <your-prefix>-summarizer

# extractor <-> assessor (clause data flow)

# On extractor:

pilotctl handshake <your-prefix>-assessor "setup: legal-contract-review"

# On assessor:

pilotctl handshake <your-prefix>-extractor "setup: legal-contract-review"

# assessor <-> summarizer (risk assessment flow)

# On assessor:

pilotctl handshake <your-prefix>-summarizer "setup: legal-contract-review"

# On summarizer:

pilotctl handshake <your-prefix>-assessor "setup: legal-contract-review"

pilotctl trust

Log Analytics

intermediate 4 agents · 12 skills

Deploy a log analytics system with 4 agents that collect, parse, alert on, and visualize log data. A collector aggregates logs from servers, containers, and applications, a parser extracts structured fields and identifies error patterns, an alerter detects anomalies and fires notifications, and a dashboard provides search and visualization with drill-down capabilities.

pilot-stream-data pilot-archive pilot-compress pilot-event-filter pilot-task-router pilot-dataset pilot-alert pilot-metrics pilot-cron pilot-webhook-bridge pilot-slack-bridge pilot-announce

clawhub install pilot-log-analytics-setup

ClawHub Source

Agents 4

<your-prefix>-collector Log Collector

Aggregates logs from servers, containers, and applications. Normalizes formats.

pilot-stream-data pilot-archive pilot-compress

clawhub install pilot-stream-data pilot-archive pilot-compress

pilotctl set-hostname <your-prefix>-collector

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-parser "setup: log-analytics"

<your-prefix>-parser Log Parser

Extracts structured fields, parses stack traces, identifies error patterns.

pilot-event-filter pilot-task-router pilot-dataset

clawhub install pilot-event-filter pilot-task-router pilot-dataset

pilotctl set-hostname <your-prefix>-parser

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-collector "setup: log-analytics"

pilotctl handshake <your-prefix>-alerter "setup: log-analytics"

<your-prefix>-alerter Anomaly Alerter

Detects log spikes, error rate anomalies, and novel error patterns. Fires alerts.

pilot-alert pilot-metrics pilot-cron

clawhub install pilot-alert pilot-metrics pilot-cron

pilotctl set-hostname <your-prefix>-alerter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-parser "setup: log-analytics"

pilotctl handshake <your-prefix>-dashboard "setup: log-analytics"

<your-prefix>-dashboard Log Dashboard

Provides search, visualization, and drill-down into log data. Generates reports.

pilot-webhook-bridge pilot-slack-bridge pilot-announce

clawhub install pilot-webhook-bridge pilot-slack-bridge pilot-announce

pilotctl set-hostname <your-prefix>-dashboard

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-alerter "setup: log-analytics"

Data Flows

<your-prefix>-collector → <your-prefix>-parser raw-log events from all sources :1002

<your-prefix>-parser → <your-prefix>-alerter parsed-event with structured fields and severity :1002

<your-prefix>-alerter → <your-prefix>-dashboard anomaly-alert with context and baselines :1002

<your-prefix>-dashboard → external log-report via webhooks and Slack :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-parser -- subscribe to raw logs from collector:

pilotctl subscribe <your-prefix>-collector raw-log

# On <your-prefix>-collector -- publish a raw log event:

pilotctl publish <your-prefix>-parser raw-log '{"source":"nginx-prod-01","timestamp":"2026-04-09T15:32:01Z","level":"error","message":"upstream timed out (110: Connection timed out)","fields":{"status":504,"upstream":"10.0.2.15:8080","request":"GET /api/v2/orders","duration_ms":30001}}'

# On <your-prefix>-alerter -- subscribe to parsed events from parser:

pilotctl subscribe <your-prefix>-parser parsed-event

# On <your-prefix>-parser -- publish a parsed event:

pilotctl publish <your-prefix>-alerter parsed-event '{"source":"nginx-prod-01","level":"error","category":"upstream_timeout","component":"nginx","structured":{"upstream":"10.0.2.15:8080","endpoint":"/api/v2/orders","status":504,"duration_ms":30001},"pattern_id":"NGINX-TIMEOUT-001","occurrences_1h":47}'

# On <your-prefix>-dashboard -- subscribe to anomaly alerts from alerter:

pilotctl subscribe <your-prefix>-alerter anomaly-alert

# On <your-prefix>-alerter -- publish an anomaly alert:

pilotctl publish <your-prefix>-dashboard anomaly-alert '{"alert_id":"ALR-7829","type":"error_spike","pattern_id":"NGINX-TIMEOUT-001","current_rate":47,"baseline_rate":3,"severity":"critical","affected_components":["nginx-prod-01","orders-api"],"started_at":"2026-04-09T15:20:00Z"}'

# On <your-prefix>-dashboard -- publish a log report:

pilotctl publish <your-prefix>-dashboard log-report '{"period":"2026-04-09T15:00:00Z/PT1H","total_events":284000,"errors":1290,"error_rate":0.0045,"top_patterns":[{"id":"NGINX-TIMEOUT-001","count":47,"severity":"critical"}],"anomalies_detected":2}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (log collector)

clawhub install pilot-stream-data pilot-archive pilot-compress

pilotctl set-hostname <your-prefix>-collector

# On server 2 (log parser)

clawhub install pilot-event-filter pilot-task-router pilot-dataset

pilotctl set-hostname <your-prefix>-parser

# On server 3 (anomaly alerter)

clawhub install pilot-alert pilot-metrics pilot-cron

pilotctl set-hostname <your-prefix>-alerter

# On server 4 (log dashboard)

clawhub install pilot-webhook-bridge pilot-slack-bridge pilot-announce

pilotctl set-hostname <your-prefix>-dashboard

# collector <-> parser

# On collector:

pilotctl handshake <your-prefix>-parser "setup: log-analytics"

# On parser:

pilotctl handshake <your-prefix>-collector "setup: log-analytics"

# parser <-> alerter

# On parser:

pilotctl handshake <your-prefix>-alerter "setup: log-analytics"

# On alerter:

pilotctl handshake <your-prefix>-parser "setup: log-analytics"

# alerter <-> dashboard

# On alerter:

pilotctl handshake <your-prefix>-dashboard "setup: log-analytics"

# On dashboard:

pilotctl handshake <your-prefix>-alerter "setup: log-analytics"

pilotctl trust

MCP Bridge Fleet

beginner 3 agents · 11 skills

Bridge different agent ecosystems over Pilot tunnels. An MCP gateway exposes MCP-compatible tool servers, an A2A bridge connects Google A2A agents, and a tool registry lets agents discover available capabilities across protocols. All traffic is encrypted and trust-gated.

pilot-mcp-bridge pilot-api-gateway pilot-health pilot-metrics pilot-a2a-bridge pilot-task-router pilot-audit-log pilot-directory pilot-discover pilot-announce-capabilities pilot-load-balancer

clawhub install pilot-mcp-bridge-fleet-setup

ClawHub Source

Agents 3

<your-prefix>-mcp-gateway MCP Gateway

pilot-mcp-bridge pilot-api-gateway pilot-health pilot-metrics

clawhub install pilot-mcp-bridge pilot-api-gateway pilot-health pilot-metrics

pilotctl set-hostname <your-prefix>-mcp-gateway

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-tool-registry "setup: mcp-bridge-fleet"

<your-prefix>-a2a-bridge A2A Bridge

pilot-a2a-bridge pilot-task-router pilot-audit-log

clawhub install pilot-a2a-bridge pilot-task-router pilot-audit-log

pilotctl set-hostname <your-prefix>-a2a-bridge

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-tool-registry "setup: mcp-bridge-fleet"

<your-prefix>-tool-registry Tool Registry

MCP tool registrations" },

pilot-directory pilot-discover pilot-announce-capabilities pilot-load-balancer

clawhub install pilot-directory pilot-discover pilot-announce-capabilities pilot-load-balancer

pilotctl set-hostname <your-prefix>-tool-registry

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-mcp-gw "setup: mcp-bridge-fleet"

pilotctl handshake <your-prefix>-a2a-bridge "setup: mcp-bridge-fleet"

Data Flows

<your-prefix>-mcp-gateway → <your-prefix>-tool-registry MCP tool registrations :1002

<your-prefix>-a2a-bridge → <your-prefix>-tool-registry A2A agent registrations :1002

<your-prefix>-tool-registry → <your-prefix>-mcp-gateway tool call routing :1002

<your-prefix>-tool-registry → <your-prefix>-a2a-bridge task routing :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-mcp-gw — register an MCP tool:

pilotctl publish <your-prefix>-tool-registry tool-register '{"name":"web-search","protocol":"mcp","provider":"<your-prefix>-mcp-gw","schema":{"query":"string"}}'

# On <your-prefix>-a2a-bridge — register an A2A agent:

pilotctl publish <your-prefix>-tool-registry tool-register '{"name":"code-review","protocol":"a2a","provider":"<your-prefix>-a2a-bridge","schema":{"repo":"string","pr":"number"}}'

# On <your-prefix>-tool-registry — route a tool call to MCP:

pilotctl publish <your-prefix>-mcp-gw tool-call '{"call_id":"C-401","tool":"web-search","params":{"query":"Pilot Protocol docs"}}'

# On <your-prefix>-mcp-gw — return result:

pilotctl publish <your-prefix>-tool-registry tool-result '{"call_id":"C-401","result":{"url":"https://pilotprotocol.network","title":"Pilot Protocol"}}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On MCP gateway node

clawhub install pilot-mcp-bridge pilot-api-gateway pilot-health pilot-metrics

pilotctl set-hostname <your-prefix>-mcp-gw

# On A2A bridge node

clawhub install pilot-a2a-bridge pilot-task-router pilot-audit-log

pilotctl set-hostname <your-prefix>-a2a-bridge

# On tool registry node

clawhub install pilot-directory pilot-discover pilot-announce-capabilities pilot-load-balancer

pilotctl set-hostname <your-prefix>-tool-registry

# mcp-gw <-> tool-registry

# On mcp-gw:

pilotctl handshake <your-prefix>-tool-registry "mcp bridge fleet"

# On tool-registry:

pilotctl handshake <your-prefix>-mcp-gw "mcp bridge fleet"

# a2a-bridge <-> tool-registry

# On a2a-bridge:

pilotctl handshake <your-prefix>-tool-registry "mcp bridge fleet"

# On tool-registry:

pilotctl handshake <your-prefix>-a2a-bridge "mcp bridge fleet"

pilotctl trust

Media Monitoring

advanced 4 agents · 12 skills

A multi-agent media intelligence platform that coordinates web crawling, sentiment analysis, trend detection, and automated reporting across four specialized agents. The crawler scrapes news sites, social media, blogs, forums, and press releases for brand mentions. The sentiment analyzer classifies mentions by sentiment and detects emerging narratives. The trend detector identifies viral content and spots PR crises early. The reporter generates media briefings, competitive share-of-voice reports, and crisis dashboards.

pilot-stream-data pilot-cron pilot-archive pilot-event-filter pilot-metrics pilot-task-router pilot-dataset pilot-alert pilot-gossip pilot-slack-bridge pilot-webhook-bridge pilot-announce

clawhub install pilot-media-monitoring-setup

ClawHub Source

Agents 4

<your-prefix>-crawler Media Crawler

Scrapes news, social media, and blogs for mentions

pilot-stream-data pilot-cron pilot-archive

clawhub install pilot-stream-data pilot-cron pilot-archive

pilotctl set-hostname <your-prefix>-crawler

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-sentiment-analyzer "setup: media-monitoring"

<your-prefix>-sentiment-analyzer Sentiment Analyzer

Classifies mentions by sentiment and reach

pilot-event-filter pilot-metrics pilot-task-router

clawhub install pilot-event-filter pilot-metrics pilot-task-router

pilotctl set-hostname <your-prefix>-sentiment-analyzer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-crawler "setup: media-monitoring"

pilotctl handshake <your-prefix>-trend-detector "setup: media-monitoring"

<your-prefix>-trend-detector Trend Detector

Identifies viral content and PR crises

pilot-dataset pilot-alert pilot-gossip

clawhub install pilot-dataset pilot-alert pilot-gossip

pilotctl set-hostname <your-prefix>-trend-detector

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-sentiment-analyzer "setup: media-monitoring"

pilotctl handshake <your-prefix>-reporter "setup: media-monitoring"

<your-prefix>-reporter Media Reporter

Generates briefings and crisis dashboards

pilot-slack-bridge pilot-webhook-bridge pilot-announce

clawhub install pilot-slack-bridge pilot-webhook-bridge pilot-announce

pilotctl set-hostname <your-prefix>-reporter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-trend-detector "setup: media-monitoring"

Data Flows

<your-prefix>-crawler → <your-prefix>-sentiment-analyzer raw media mentions with source metadata :1002

<your-prefix>-sentiment-analyzer → <your-prefix>-trend-detector scored mentions with sentiment and reach :1002

<your-prefix>-trend-detector → <your-prefix>-reporter trend alerts and crisis warnings :1002

<your-prefix>-reporter → external media briefings via secure channel :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-crawler -- publish a media mention:

pilotctl publish <your-prefix>-sentiment-analyzer media-mention '{"source":"reuters","url":"https://reuters.com/article/12345","headline":"Acme Corp reports record Q1 revenue","brand":"acme","reach":2400000,"published":"2026-04-10T09:15:00Z"}'

# On <your-prefix>-sentiment-analyzer -- publish a scored mention:

pilotctl publish <your-prefix>-trend-detector scored-mention '{"source":"reuters","headline":"Acme Corp reports record Q1 revenue","sentiment":"positive","score":0.87,"influencer_reach":2400000,"narratives":["earnings_beat","growth_story"]}'

# On <your-prefix>-trend-detector -- publish a trend alert:

pilotctl publish <your-prefix>-reporter trend-alert '{"brand":"acme","trend":"earnings_beat","velocity":340,"share_of_voice":0.62,"severity":"info","message":"Positive earnings coverage accelerating across major outlets"}'

# On <your-prefix>-reporter -- distribute a media briefing:

pilotctl publish <your-prefix>-reporter media-briefing '{"period":"daily","brand":"acme","total_mentions":1847,"sentiment_breakdown":{"positive":0.68,"neutral":0.24,"negative":0.08},"top_narrative":"earnings_beat","crisis_level":"none"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On crawling server

clawhub install pilot-stream-data pilot-cron pilot-archive

pilotctl set-hostname <your-prefix>-crawler

# On sentiment analysis server

clawhub install pilot-event-filter pilot-metrics pilot-task-router

pilotctl set-hostname <your-prefix>-sentiment-analyzer

# On trend detection server

clawhub install pilot-dataset pilot-alert pilot-gossip

pilotctl set-hostname <your-prefix>-trend-detector

# On reporting server

clawhub install pilot-slack-bridge pilot-webhook-bridge pilot-announce

pilotctl set-hostname <your-prefix>-reporter

# crawler <-> sentiment-analyzer (media mentions)

# On crawler:

pilotctl handshake <your-prefix>-sentiment-analyzer "setup: media-monitoring"

# On sentiment-analyzer:

pilotctl handshake <your-prefix>-crawler "setup: media-monitoring"

# sentiment-analyzer <-> trend-detector (scored mentions)

# On sentiment-analyzer:

pilotctl handshake <your-prefix>-trend-detector "setup: media-monitoring"

# On trend-detector:

pilotctl handshake <your-prefix>-sentiment-analyzer "setup: media-monitoring"

# trend-detector <-> reporter (trend alerts)

# On trend-detector:

pilotctl handshake <your-prefix>-reporter "setup: media-monitoring"

# On reporter:

pilotctl handshake <your-prefix>-trend-detector "setup: media-monitoring"

pilotctl trust

Meeting Assistant

beginner 3 agents · 9 skills

Deploy a meeting assistant system where a scheduler manages calendar availability and sends invites, a note-taker captures meeting notes and key decisions in structured format, and an action tracker extracts action items and sends reminders. The three agents form an end-to-end workflow that turns scheduled meetings into tracked outcomes with minimal human intervention.

pilot-cron pilot-webhook-bridge pilot-receipt pilot-stream-data pilot-share pilot-archive pilot-task-router pilot-alert pilot-slack-bridge

clawhub install pilot-meeting-assistant-setup

ClawHub Source

Agents 3

<your-prefix>-scheduler Meeting Scheduler

Manages calendar availability, sends invites, handles rescheduling and conflicts.

pilot-cron pilot-webhook-bridge pilot-receipt

clawhub install pilot-cron pilot-webhook-bridge pilot-receipt

pilotctl set-hostname <your-prefix>-scheduler

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-note-taker "setup: meeting-assistant"

<your-prefix>-note-taker Note Taker

Captures meeting notes, key decisions, and discussion summaries in structured format.

pilot-stream-data pilot-share pilot-archive

clawhub install pilot-stream-data pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-note-taker

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-scheduler "setup: meeting-assistant"

pilotctl handshake <your-prefix>-action-tracker "setup: meeting-assistant"

<your-prefix>-action-tracker Action Tracker

Extracts action items from notes, assigns owners, tracks completion, and sends reminders.

pilot-task-router pilot-alert pilot-slack-bridge

clawhub install pilot-task-router pilot-alert pilot-slack-bridge

pilotctl set-hostname <your-prefix>-action-tracker

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-note-taker "setup: meeting-assistant"

Data Flows

<your-prefix>-scheduler → <your-prefix>-note-taker meeting-started :1002

<your-prefix>-note-taker → <your-prefix>-action-tracker meeting-notes :1002

<your-prefix>-action-tracker → external action-reminder via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-note-taker -- subscribe to meeting started events:

pilotctl subscribe <your-prefix>-scheduler meeting-started

# On <your-prefix>-action-tracker -- subscribe to meeting notes:

pilotctl subscribe <your-prefix>-note-taker meeting-notes

# On <your-prefix>-scheduler -- publish a meeting started event:

pilotctl publish <your-prefix>-note-taker meeting-started '{"meeting_id":"MTG-2026-0412","title":"Q2 Planning Review","attendees":["[email protected]","[email protected]","[email protected]"],"agenda":["Q1 retrospective","Q2 OKRs","Resource allocation"],"started_at":"2026-04-10T10:00:00Z"}'

# On <your-prefix>-note-taker -- publish meeting notes to the action tracker:

pilotctl publish <your-prefix>-action-tracker meeting-notes '{"meeting_id":"MTG-2026-0412","title":"Q2 Planning Review","decisions":["Increase hiring budget by 15%","Launch Project Alpha by June"],"action_items":[{"task":"Draft Q2 OKR document","owner":"[email protected]","due":"2026-04-17"},{"task":"Schedule Project Alpha kickoff","owner":"[email protected]","due":"2026-04-14"}],"summary":"Team aligned on Q2 priorities with focus on Project Alpha launch."}'

# The action tracker sends reminders to owners:

pilotctl publish <your-prefix>-action-tracker action-reminder '{"channel":"#team-ops","text":"Action item due in 3 days: Draft Q2 OKR document (owner: [email protected])","meeting_id":"MTG-2026-0412","url":"https://notes.acme.com/mtg-2026-0412"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (meeting scheduler)

clawhub install pilot-cron pilot-webhook-bridge pilot-receipt

pilotctl set-hostname <your-prefix>-scheduler

# On server 2 (note taker)

clawhub install pilot-stream-data pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-note-taker

# On server 3 (action tracker)

clawhub install pilot-task-router pilot-alert pilot-slack-bridge

pilotctl set-hostname <your-prefix>-action-tracker

# scheduler <-> note-taker

# On scheduler:

pilotctl handshake <your-prefix>-note-taker "setup: meeting-assistant"

# On note-taker:

pilotctl handshake <your-prefix>-scheduler "setup: meeting-assistant"

# note-taker <-> action-tracker

# On note-taker:

pilotctl handshake <your-prefix>-action-tracker "setup: meeting-assistant"

# On action-tracker:

pilotctl handshake <your-prefix>-note-taker "setup: meeting-assistant"

pilotctl trust

ML Training Pipeline

advanced 4 agents · 9 skills

An end-to-end machine learning pipeline spanning four agents. Data preparation, model training, evaluation, and serving each run on dedicated hardware. Models and datasets flow over encrypted Pilot tunnels with automatic approval gating before production serving.

pilot-dataset pilot-share pilot-task-chain pilot-model-share pilot-metrics pilot-review pilot-health pilot-webhook-bridge pilot-load-balancer

clawhub install pilot-ml-training-pipeline-setup

ClawHub Source

Agents 4

<your-prefix>-data-prep Data Preparation

Cleans, validates, and transforms raw datasets. Shares processed data with the trainer.

pilot-dataset pilot-share pilot-task-chain

clawhub install pilot-dataset pilot-share pilot-task-chain

pilotctl set-hostname <your-prefix>-data-prep

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-trainer "setup: ml-training-pipeline"

<your-prefix>-trainer Model Trainer

Receives prepared datasets, runs training jobs, tracks metrics, and shares trained model artifacts.

pilot-dataset pilot-model-share pilot-metrics pilot-task-chain

clawhub install pilot-dataset pilot-model-share pilot-metrics pilot-task-chain

pilotctl set-hostname <your-prefix>-trainer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-data-prep "setup: ml-training-pipeline"

pilotctl handshake <your-prefix>-evaluator "setup: ml-training-pipeline"

<your-prefix>-evaluator Model Evaluator

Scores trained models against benchmarks and gates promotion to serving.

pilot-model-share pilot-metrics pilot-review pilot-task-chain

clawhub install pilot-model-share pilot-metrics pilot-review pilot-task-chain

pilotctl set-hostname <your-prefix>-evaluator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-trainer "setup: ml-training-pipeline"

pilotctl handshake <your-prefix>-serving "setup: ml-training-pipeline"

<your-prefix>-serving Model Server

Loads approved models, serves inference, monitors health, and load-balances.

pilot-model-share pilot-health pilot-webhook-bridge pilot-load-balancer pilot-metrics

clawhub install pilot-model-share pilot-health pilot-webhook-bridge pilot-load-balancer pilot-metrics

pilotctl set-hostname <your-prefix>-serving

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-evaluator "setup: ml-training-pipeline"

Data Flows

<your-prefix>-data-prep → <your-prefix>-trainer cleaned datasets :1001

<your-prefix>-trainer → <your-prefix>-evaluator model checkpoints and metrics :1001

<your-prefix>-evaluator → <your-prefix>-serving approved models :1001

<your-prefix>-serving → <your-prefix>-evaluator inference metrics for drift detection :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-data-prep — send cleaned dataset to trainer:

pilotctl send-file <your-prefix>-trainer ./datasets/training-v5.parquet

pilotctl publish <your-prefix>-trainer dataset-ready '{"name":"training-v5","rows":150000,"features":64}'

# On <your-prefix>-trainer — send model checkpoint and metrics:

pilotctl send-file <your-prefix>-evaluator ./models/resnet-v5-epoch20.pt

pilotctl publish <your-prefix>-evaluator training-complete '{"model":"resnet-v5","loss":0.023,"accuracy":0.967,"epochs":20}'

# On <your-prefix>-evaluator — approve and promote to serving:

pilotctl send-file <your-prefix>-serving ./models/resnet-v5-epoch20.pt

pilotctl publish <your-prefix>-serving model-approved '{"model":"resnet-v5","benchmark":0.971,"approved":true}'

# On <your-prefix>-serving — report inference metrics:

pilotctl publish <your-prefix>-evaluator inference-metrics '{"model":"resnet-v5","qps":1200,"p99_ms":45,"drift":0.003}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On data processing node

clawhub install pilot-dataset pilot-share pilot-task-chain

pilotctl set-hostname <your-prefix>-data-prep

# On GPU training node

clawhub install pilot-dataset pilot-model-share pilot-metrics pilot-task-chain

pilotctl set-hostname <your-prefix>-trainer

# On evaluation node

clawhub install pilot-model-share pilot-metrics pilot-review pilot-task-chain

pilotctl set-hostname <your-prefix>-evaluator

# On serving node

clawhub install pilot-model-share pilot-health pilot-webhook-bridge pilot-load-balancer

pilotctl set-hostname <your-prefix>-serving

# On data-prep:

pilotctl handshake <your-prefix>-trainer "setup: ml-training-pipeline"

# On trainer:

pilotctl handshake <your-prefix>-data-prep "setup: ml-training-pipeline"

# On evaluator:

pilotctl handshake <your-prefix>-serving "setup: ml-training-pipeline"

# On serving:

pilotctl handshake <your-prefix>-evaluator "setup: ml-training-pipeline"

# On evaluator:

pilotctl handshake <your-prefix>-trainer "setup: ml-training-pipeline"

# On trainer:

pilotctl handshake <your-prefix>-evaluator "setup: ml-training-pipeline"

pilotctl trust

Multi-Region Content Sync

intermediate 4 agents · 5 skills

Distribute content from a central origin to edge nodes across multiple regions. The origin broadcasts updates and edges sync automatically. Heartbeat monitoring ensures every edge is alive, with automatic alerting when a region goes dark.

pilot-sync pilot-share pilot-broadcast pilot-heartbeat-monitor pilot-health

clawhub install pilot-multi-region-content-sync-setup

ClawHub Source

Agents 4

<your-prefix>-origin Content Origin

Source of truth for all content. Broadcasts updates to all edge nodes.

pilot-sync pilot-share pilot-broadcast pilot-heartbeat-monitor

clawhub install pilot-sync pilot-share pilot-broadcast pilot-heartbeat-monitor

pilotctl set-hostname <your-prefix>-origin

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-edge-us "setup: multi-region-content-sync"

pilotctl handshake <your-prefix>-edge-eu "setup: multi-region-content-sync"

pilotctl handshake <your-prefix>-edge-asia "setup: multi-region-content-sync"

<your-prefix>-edge-us <Region> Edge Node

Serves content for the <region> region. Syncs from origin and reports health.

pilot-sync pilot-share pilot-health pilot-heartbeat-monitor

clawhub install pilot-sync pilot-share pilot-health pilot-heartbeat-monitor

pilotctl set-hostname <your-prefix>-edge-us

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-origin "setup: multi-region-content-sync"

<your-prefix>-edge-eu EU regional edge

EU regional edge

pilot-sync pilot-share pilot-health pilot-heartbeat-monitor

clawhub install pilot-sync pilot-share pilot-health pilot-heartbeat-monitor

pilotctl set-hostname <your-prefix>-edge-eu

<your-prefix>-edge-asia Asia regional edge

Asia regional edge

pilot-sync pilot-share pilot-health pilot-heartbeat-monitor

clawhub install pilot-sync pilot-share pilot-health pilot-heartbeat-monitor

pilotctl set-hostname <your-prefix>-edge-asia

Data Flows

<your-prefix>-origin → <your-prefix>-edge-* content updates :1001

<your-prefix>-edge-* → <your-prefix>-origin heartbeat and sync confirmation :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-origin — broadcast a content update to all edges:

pilotctl send-file <your-prefix>-edge-us ./content/index.html

pilotctl send-file <your-prefix>-edge-eu ./content/index.html

pilotctl send-file <your-prefix>-edge-asia ./content/index.html

pilotctl publish <your-prefix>-edge-us content-update '{"file":"index.html","version":42,"hash":"sha256:a1b2c3"}'

pilotctl publish <your-prefix>-edge-eu content-update '{"file":"index.html","version":42,"hash":"sha256:a1b2c3"}'

pilotctl publish <your-prefix>-edge-asia content-update '{"file":"index.html","version":42,"hash":"sha256:a1b2c3"}'

# On any edge — confirm sync and send heartbeat:

pilotctl publish <your-prefix>-origin sync-complete '{"region":"us","file":"index.html","version":42}'

pilotctl publish <your-prefix>-origin heartbeat '{"region":"us","status":"healthy","disk_pct":34}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On origin server

clawhub install pilot-sync pilot-share pilot-broadcast

pilotctl set-hostname <your-prefix>-origin

# On US edge server

clawhub install pilot-sync pilot-share pilot-health pilot-heartbeat-monitor

pilotctl set-hostname <your-prefix>-edge-us

# On EU edge server

clawhub install pilot-sync pilot-share pilot-health pilot-heartbeat-monitor

pilotctl set-hostname <your-prefix>-edge-eu

# On Asia edge server

clawhub install pilot-sync pilot-share pilot-health pilot-heartbeat-monitor

pilotctl set-hostname <your-prefix>-edge-asia

# On edge-asia:

pilotctl handshake <your-prefix>-origin "setup: multi-region-content-sync"

# On origin:

pilotctl handshake <your-prefix>-edge-asia "setup: multi-region-content-sync"

# On edge-eu:

pilotctl handshake <your-prefix>-origin "setup: multi-region-content-sync"

# On origin:

pilotctl handshake <your-prefix>-edge-eu "setup: multi-region-content-sync"

# On edge-us:

pilotctl handshake <your-prefix>-origin "setup: multi-region-content-sync"

# On origin:

pilotctl handshake <your-prefix>-edge-us "setup: multi-region-content-sync"

pilotctl trust

Newsletter Automation

beginner 3 agents · 9 skills

Deploy an automated newsletter pipeline with 3 agents that curate trending content, transform it into polished newsletter copy, and dispatch emails to subscriber segments. Each agent handles a stage of the production process -- curation, writing, and delivery -- so newsletters go out on schedule without manual effort.

pilot-discover pilot-stream-data pilot-archive pilot-task-router pilot-share pilot-receipt pilot-webhook-bridge pilot-announce pilot-metrics

clawhub install pilot-newsletter-automation-setup

ClawHub Source

Agents 3

<your-prefix>-curator Content Curator

Aggregates trending articles, RSS feeds, and industry news into curated content digests.

pilot-discover pilot-stream-data pilot-archive

clawhub install pilot-discover pilot-stream-data pilot-archive

pilotctl set-hostname <your-prefix>-curator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-writer "setup: newsletter-automation"

<your-prefix>-writer Newsletter Writer

Transforms curated content into engaging newsletter copy with subject lines and sections.

pilot-task-router pilot-share pilot-receipt

clawhub install pilot-task-router pilot-share pilot-receipt

pilotctl set-hostname <your-prefix>-writer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-curator "setup: newsletter-automation"

pilotctl handshake <your-prefix>-mailer "setup: newsletter-automation"

<your-prefix>-mailer Email Dispatcher

Formats newsletters for email delivery, manages subscriber segments, tracks open rates.

pilot-webhook-bridge pilot-announce pilot-metrics

clawhub install pilot-webhook-bridge pilot-announce pilot-metrics

pilotctl set-hostname <your-prefix>-mailer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-writer "setup: newsletter-automation"

Data Flows

<your-prefix>-curator → <your-prefix>-writer content-digest events :1002

<your-prefix>-writer → <your-prefix>-mailer newsletter-draft events :1002

<your-prefix>-mailer → external email-dispatch via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-writer — subscribe to content digests from curator:

pilotctl subscribe <your-prefix>-curator content-digest

# On <your-prefix>-mailer — subscribe to newsletter drafts from writer:

pilotctl subscribe <your-prefix>-writer newsletter-draft

# On <your-prefix>-curator — publish a content digest:

pilotctl publish <your-prefix>-writer content-digest '{"date":"2026-04-10","articles":[{"title":"AI Agents in Production","url":"https://example.com/ai-agents","summary":"How teams are deploying autonomous agents at scale."}],"topic":"AI & DevOps"}'

# On <your-prefix>-writer — publish a newsletter draft:

pilotctl publish <your-prefix>-mailer newsletter-draft '{"subject":"This Week in AI & DevOps","sections":[{"heading":"Top Story","body":"AI agents are going mainstream in production environments..."}],"format":"html"}'

# The mailer receives the draft and dispatches emails:

pilotctl publish <your-prefix>-mailer email-dispatch '{"segment":"ai-enthusiasts","recipients":1250,"subject":"This Week in AI & DevOps","status":"queued"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (content curator)

clawhub install pilot-discover pilot-stream-data pilot-archive

pilotctl set-hostname <your-prefix>-curator

# On server 2 (newsletter writer)

clawhub install pilot-task-router pilot-share pilot-receipt

pilotctl set-hostname <your-prefix>-writer

# On server 3 (email dispatcher)

clawhub install pilot-webhook-bridge pilot-announce pilot-metrics

pilotctl set-hostname <your-prefix>-mailer

# On writer:

pilotctl handshake <your-prefix>-curator "setup: newsletter-automation"

# On curator:

pilotctl handshake <your-prefix>-writer "setup: newsletter-automation"

# On mailer:

pilotctl handshake <your-prefix>-writer "setup: newsletter-automation"

# On writer:

pilotctl handshake <your-prefix>-mailer "setup: newsletter-automation"

pilotctl trust

Penetration Testing

advanced 4 agents · 12 skills

Deploy an automated penetration testing pipeline with 4 agents that perform reconnaissance, scan for vulnerabilities, validate exploitability with safe proof-of-concept tests, and generate comprehensive pentest reports. Each agent handles a stage of the assessment -- recon, scanning, validation, and reporting -- so security assessments are methodical, thorough, and well-documented.

pilot-discover pilot-stream-data pilot-archive pilot-task-parallel pilot-metrics pilot-dataset pilot-task-chain pilot-audit-log pilot-receipt pilot-webhook-bridge pilot-share pilot-slack-bridge

clawhub install pilot-penetration-testing-setup

ClawHub Source

Agents 4

<your-prefix>-recon Reconnaissance Agent

Performs passive and active reconnaissance — DNS enumeration, port scanning, service fingerprinting.

pilot-discover pilot-stream-data pilot-archive

clawhub install pilot-discover pilot-stream-data pilot-archive

pilotctl set-hostname <your-prefix>-recon

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-scanner "setup: penetration-testing"

<your-prefix>-scanner Vulnerability Scanner

Runs automated vulnerability scans, checks CVE databases, identifies misconfigurations.

pilot-task-parallel pilot-metrics pilot-dataset

clawhub install pilot-task-parallel pilot-metrics pilot-dataset

pilotctl set-hostname <your-prefix>-scanner

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-recon "setup: penetration-testing"

pilotctl handshake <your-prefix>-exploiter "setup: penetration-testing"

<your-prefix>-exploiter Exploit Validator

Validates discovered vulnerabilities with safe proof-of-concept tests, confirms exploitability.

pilot-task-chain pilot-audit-log pilot-receipt

clawhub install pilot-task-chain pilot-audit-log pilot-receipt

pilotctl set-hostname <your-prefix>-exploiter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-scanner "setup: penetration-testing"

pilotctl handshake <your-prefix>-reporter "setup: penetration-testing"

<your-prefix>-reporter Pentest Reporter

Generates pentest reports with findings, risk ratings, remediation steps, and executive summary.

pilot-webhook-bridge pilot-share pilot-slack-bridge

clawhub install pilot-webhook-bridge pilot-share pilot-slack-bridge

pilotctl set-hostname <your-prefix>-reporter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-exploiter "setup: penetration-testing"

Data Flows

<your-prefix>-recon → <your-prefix>-scanner recon-result events :1002

<your-prefix>-scanner → <your-prefix>-exploiter vulnerability events :1002

<your-prefix>-exploiter → <your-prefix>-reporter validated-finding events :1002

<your-prefix>-reporter → external pentest-report via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-scanner — subscribe to recon results from recon:

pilotctl subscribe <your-prefix>-recon recon-result

# On <your-prefix>-exploiter — subscribe to vulnerabilities from scanner:

pilotctl subscribe <your-prefix>-scanner vulnerability

# On <your-prefix>-reporter — subscribe to validated findings from exploiter:

pilotctl subscribe <your-prefix>-exploiter validated-finding

# On <your-prefix>-recon — publish a recon result:

pilotctl publish <your-prefix>-scanner recon-result '{"target":"app.example.com","dns":["192.168.1.10"],"open_ports":[22,80,443,8080],"services":{"22":"OpenSSH 8.9","80":"nginx 1.24","8080":"Apache Tomcat 9.0.65"},"os":"Ubuntu 22.04"}'

# On <your-prefix>-scanner — publish a vulnerability:

pilotctl publish <your-prefix>-exploiter vulnerability '{"target":"app.example.com","port":8080,"cve":"CVE-2023-46589","service":"Apache Tomcat 9.0.65","severity":"critical","cvss":9.8,"description":"Request smuggling via malformed HTTP/2 frames"}'

# On <your-prefix>-exploiter — publish a validated finding:

pilotctl publish <your-prefix>-reporter validated-finding '{"target":"app.example.com","cve":"CVE-2023-46589","validated":true,"impact":"Remote code execution possible","evidence":"HTTP/2 smuggling confirmed with crafted HEADERS frame","remediation":"Upgrade Tomcat to 9.0.84+"}'

# On <your-prefix>-reporter — forward pentest report:

pilotctl publish <your-prefix>-reporter pentest-report '{"target":"app.example.com","findings_total":12,"critical":1,"high":3,"medium":5,"low":3,"executive_summary":"Critical RCE vulnerability found in Tomcat","report_url":"https://reports.example.com/pentest-2026-042"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (reconnaissance agent)

clawhub install pilot-discover pilot-stream-data pilot-archive

pilotctl set-hostname <your-prefix>-recon

# On server 2 (vulnerability scanner)

clawhub install pilot-task-parallel pilot-metrics pilot-dataset

pilotctl set-hostname <your-prefix>-scanner

# On server 3 (exploit validator)

clawhub install pilot-task-chain pilot-audit-log pilot-receipt

pilotctl set-hostname <your-prefix>-exploiter

# On server 4 (pentest reporter)

clawhub install pilot-webhook-bridge pilot-share pilot-slack-bridge

pilotctl set-hostname <your-prefix>-reporter

# On recon:

pilotctl handshake <your-prefix>-scanner "setup: penetration-testing"

# On scanner:

pilotctl handshake <your-prefix>-recon "setup: penetration-testing"

# On scanner:

pilotctl handshake <your-prefix>-exploiter "setup: penetration-testing"

# On exploiter:

pilotctl handshake <your-prefix>-scanner "setup: penetration-testing"

# On exploiter:

pilotctl handshake <your-prefix>-reporter "setup: penetration-testing"

# On reporter:

pilotctl handshake <your-prefix>-exploiter "setup: penetration-testing"

pilotctl trust

Podcast Production

beginner 3 agents · 9 skills

Deploy a podcast production pipeline where a researcher finds trending topics and guest suggestions, a producer organizes show notes and coordinates recording schedules, and a distributor publishes episodes across platforms and social media. The three agents form an assembly line that turns raw research into published podcast episodes with minimal human intervention.

pilot-discover pilot-stream-data pilot-archive pilot-task-router pilot-share pilot-cron pilot-webhook-bridge pilot-announce pilot-slack-bridge

clawhub install pilot-podcast-production-setup

ClawHub Source

Agents 3

<your-prefix>-researcher Topic Researcher

Finds trending topics, guest suggestions, audience questions, and talking points for episodes.

pilot-discover pilot-stream-data pilot-archive

clawhub install pilot-discover pilot-stream-data pilot-archive

pilotctl set-hostname <your-prefix>-researcher

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-producer "setup: podcast-production"

<your-prefix>-producer Episode Producer

Organizes show notes, talking points, intros/outros, timestamps, and coordinates recording schedules.

pilot-task-router pilot-share pilot-cron

clawhub install pilot-task-router pilot-share pilot-cron

pilotctl set-hostname <your-prefix>-producer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-researcher "setup: podcast-production"

pilotctl handshake <your-prefix>-distributor "setup: podcast-production"

<your-prefix>-distributor Content Distributor

Publishes episodes to RSS feeds, Apple Podcasts, Spotify. Posts show notes and clips to social media.

pilot-webhook-bridge pilot-announce pilot-slack-bridge

clawhub install pilot-webhook-bridge pilot-announce pilot-slack-bridge

pilotctl set-hostname <your-prefix>-distributor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-producer "setup: podcast-production"

Data Flows

<your-prefix>-researcher → <your-prefix>-producer episode-brief :1002

<your-prefix>-producer → <your-prefix>-distributor episode-package :1002

<your-prefix>-distributor → external publish-notification via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-producer -- subscribe to episode briefs:

pilotctl subscribe <your-prefix>-researcher episode-brief

# On <your-prefix>-distributor -- subscribe to episode packages:

pilotctl subscribe <your-prefix>-producer episode-package

# On <your-prefix>-researcher -- publish an episode brief:

pilotctl publish <your-prefix>-producer episode-brief '{"topic":"Future of AI Agents in DevOps","guests":["Jane Smith","Alex Chen"],"talking_points":["autonomous deployments","self-healing infrastructure","agent collaboration"],"audience_questions":["How do agents handle rollbacks?","What about security?"],"trending_score":87}'

# On <your-prefix>-producer -- publish an episode package to the distributor:

pilotctl publish <your-prefix>-distributor episode-package '{"title":"EP42: Future of AI Agents in DevOps","duration_minutes":45,"show_notes":"Deep dive into autonomous deployments with Jane Smith and Alex Chen.","timestamps":["00:00 Intro","03:15 Guest backgrounds","12:30 Autonomous deployments","28:00 Security concerns","40:00 Wrap-up"],"status":"ready"}'

# The distributor publishes to platforms and notifies social:

pilotctl publish <your-prefix>-distributor publish-notification '{"channel":"#podcast","text":"Published: EP42 - Future of AI Agents in DevOps","platforms":["rss","apple_podcasts","spotify"],"url":"https://podcast.acme.com/ep42"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (topic researcher)

clawhub install pilot-discover pilot-stream-data pilot-archive

pilotctl set-hostname <your-prefix>-researcher

# On server 2 (episode producer)

clawhub install pilot-task-router pilot-share pilot-cron

pilotctl set-hostname <your-prefix>-producer

# On server 3 (content distributor)

clawhub install pilot-webhook-bridge pilot-announce pilot-slack-bridge

pilotctl set-hostname <your-prefix>-distributor

# researcher <-> producer

# On researcher:

pilotctl handshake <your-prefix>-producer "setup: podcast-production"

# On producer:

pilotctl handshake <your-prefix>-researcher "setup: podcast-production"

# producer <-> distributor

# On producer:

pilotctl handshake <your-prefix>-distributor "setup: podcast-production"

# On distributor:

pilotctl handshake <your-prefix>-producer "setup: podcast-production"

pilotctl trust

Proposal Writer

intermediate 3 agents · 9 skills

Deploy a multi-agent proposal writing system with 3 agents that research RFP requirements and competitor landscape, draft proposal sections with pricing and timelines, and review drafts for compliance and win themes. Each agent handles a stage of the proposal lifecycle -- research, drafting, and review -- so proposals are thorough, consistent, and submission-ready.

pilot-discover pilot-dataset pilot-archive pilot-task-router pilot-share pilot-receipt pilot-review pilot-webhook-bridge pilot-slack-bridge

clawhub install pilot-proposal-writer-setup

ClawHub Source

Agents 3

<your-prefix>-researcher Proposal Researcher

Gathers RFP requirements, competitor analysis, and client background.

pilot-discover pilot-dataset pilot-archive

clawhub install pilot-discover pilot-dataset pilot-archive

pilotctl set-hostname <your-prefix>-researcher

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-drafter "setup: proposal-writer"

<your-prefix>-drafter Proposal Drafter

Writes proposal sections — executive summary, technical approach, pricing, timeline.

pilot-task-router pilot-share pilot-receipt

clawhub install pilot-task-router pilot-share pilot-receipt

pilotctl set-hostname <your-prefix>-drafter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-researcher "setup: proposal-writer"

pilotctl handshake <your-prefix>-reviewer "setup: proposal-writer"

<your-prefix>-reviewer Proposal Reviewer

Reviews drafts for compliance, consistency, and win themes. Formats final submission.

pilot-review pilot-webhook-bridge pilot-slack-bridge

clawhub install pilot-review pilot-webhook-bridge pilot-slack-bridge

pilotctl set-hostname <your-prefix>-reviewer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-drafter "setup: proposal-writer"

Data Flows

<your-prefix>-researcher → <your-prefix>-drafter research-brief events :1002

<your-prefix>-drafter → <your-prefix>-reviewer draft-proposal events :1002

<your-prefix>-reviewer → external final-proposal via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-drafter — subscribe to research briefs from researcher:

pilotctl subscribe <your-prefix>-researcher research-brief

# On <your-prefix>-reviewer — subscribe to draft proposals from drafter:

pilotctl subscribe <your-prefix>-drafter draft-proposal

# On <your-prefix>-researcher — publish a research brief:

pilotctl publish <your-prefix>-drafter research-brief '{"rfp_id":"RFP-2026-042","client":"Acme Corp","requirements":["cloud migration","24/7 support","SOC2 compliance"],"competitors":["RivalCo","BigTech Inc"],"budget_range":"$500K-$1M","deadline":"2026-05-15"}'

# On <your-prefix>-drafter — publish a draft proposal:

pilotctl publish <your-prefix>-reviewer draft-proposal '{"rfp_id":"RFP-2026-042","sections":{"executive_summary":"We propose a phased cloud migration...","technical_approach":"Using containerized microservices...","pricing":"$750,000 over 18 months","timeline":"3 phases across 18 months"},"compliance_checklist":["SOC2","24/7 support"]}'

# The reviewer receives the draft and submits:

pilotctl publish <your-prefix>-reviewer final-proposal '{"rfp_id":"RFP-2026-042","status":"approved","score":92,"notes":"Strong technical approach, competitive pricing","submission_url":"https://portal.acme.com/submit"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (proposal researcher)

clawhub install pilot-discover pilot-dataset pilot-archive

pilotctl set-hostname <your-prefix>-researcher

# On server 2 (proposal drafter)

clawhub install pilot-task-router pilot-share pilot-receipt

pilotctl set-hostname <your-prefix>-drafter

# On server 3 (proposal reviewer)

clawhub install pilot-review pilot-webhook-bridge pilot-slack-bridge

pilotctl set-hostname <your-prefix>-reviewer

# On drafter:

pilotctl handshake <your-prefix>-researcher "setup: proposal-writer"

# On researcher:

pilotctl handshake <your-prefix>-drafter "setup: proposal-writer"

# On reviewer:

pilotctl handshake <your-prefix>-drafter "setup: proposal-writer"

# On drafter:

pilotctl handshake <your-prefix>-reviewer "setup: proposal-writer"

pilotctl trust

Quality Assurance Pipeline

intermediate 3 agents · 9 skills

Deploy a quality assurance pipeline with 3 agents that automate test generation, execution, and reporting. A test generator creates test cases from specs and user stories, an executor runs automated suites and captures results, and a reporter aggregates outcomes into coverage reports and files bugs. The pipeline turns code changes into verified quality gates with minimal manual intervention.

pilot-task-router pilot-dataset pilot-cron pilot-task-parallel pilot-share pilot-metrics pilot-webhook-bridge pilot-alert pilot-slack-bridge

clawhub install pilot-quality-assurance-pipeline-setup

ClawHub Source

Agents 3

<your-prefix>-test-generator Test Generator

Generates test cases from specs and stories, prioritizes by risk

pilot-task-router pilot-dataset pilot-cron

clawhub install pilot-task-router pilot-dataset pilot-cron

pilotctl set-hostname <your-prefix>-test-generator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-executor "setup: quality-assurance-pipeline"

<your-prefix>-executor Test Executor

Runs test suites, captures results, screenshots, and logs

pilot-task-parallel pilot-share pilot-metrics

clawhub install pilot-task-parallel pilot-share pilot-metrics

pilotctl set-hostname <your-prefix>-executor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-test-generator "setup: quality-assurance-pipeline"

pilotctl handshake <your-prefix>-reporter "setup: quality-assurance-pipeline"

<your-prefix>-reporter QA Reporter

Aggregates results, generates reports, files bugs, notifies team

pilot-webhook-bridge pilot-alert pilot-slack-bridge

clawhub install pilot-webhook-bridge pilot-alert pilot-slack-bridge

pilotctl set-hostname <your-prefix>-reporter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-executor "setup: quality-assurance-pipeline"

Data Flows

<your-prefix>-test-generator → <your-prefix>-executor test-suite :1002

<your-prefix>-executor → <your-prefix>-reporter test-result :1002

<your-prefix>-reporter → external qa-report via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-executor -- subscribe to test suites:

pilotctl subscribe <your-prefix>-test-generator test-suite

# On <your-prefix>-test-generator -- publish a test suite:

pilotctl publish <your-prefix>-executor test-suite '{"suite":"checkout-flow","source":"user-story-42","cases":[{"id":"tc_001","name":"add_to_cart","priority":"high","type":"e2e"},{"id":"tc_002","name":"apply_coupon","priority":"medium","type":"integration"}],"environment":"staging","trigger":"pr-merge"}'

# On <your-prefix>-reporter -- subscribe to test results:

pilotctl subscribe <your-prefix>-executor test-result

# On <your-prefix>-executor -- publish test results:

pilotctl publish <your-prefix>-reporter test-result '{"suite":"checkout-flow","total":2,"passed":1,"failed":1,"failures":[{"id":"tc_002","name":"apply_coupon","error":"coupon validation timeout","duration_ms":5200}],"duration_ms":8400,"environment":"staging"}'

# On <your-prefix>-reporter -- publish external QA report:

pilotctl publish <your-prefix>-reporter qa-report '{"suite":"checkout-flow","status":"failed","pass_rate":0.50,"bugs_filed":1,"bug_ids":["BUG-1847"],"coverage":0.78,"recommendation":"Block deploy — checkout coupon flow regression"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (test generator)

clawhub install pilot-task-router pilot-dataset pilot-cron

pilotctl set-hostname <your-prefix>-test-generator

# On server 2 (test executor)

clawhub install pilot-task-parallel pilot-share pilot-metrics

pilotctl set-hostname <your-prefix>-executor

# On server 3 (QA reporter)

clawhub install pilot-webhook-bridge pilot-alert pilot-slack-bridge

pilotctl set-hostname <your-prefix>-reporter

# test-generator <-> executor

# On test-generator:

pilotctl handshake <your-prefix>-executor "setup: quality-assurance-pipeline"

# On executor:

pilotctl handshake <your-prefix>-test-generator "setup: quality-assurance-pipeline"

# executor <-> reporter

# On executor:

pilotctl handshake <your-prefix>-reporter "setup: quality-assurance-pipeline"

# On reporter:

pilotctl handshake <your-prefix>-executor "setup: quality-assurance-pipeline"

pilotctl trust

Real Estate Analyzer

advanced 4 agents · 12 skills

Deploy a real estate analysis system with 4 agents that monitors property listings, calculates valuations and market metrics, generates comparable sales reports, and alerts investors to high-ROI opportunities. The pipeline covers the full deal-finding workflow from scraping to investor notification.

pilot-stream-data pilot-cron pilot-archive pilot-metrics pilot-dataset pilot-task-router pilot-event-filter pilot-share pilot-review pilot-alert pilot-slack-bridge pilot-webhook-bridge

clawhub install pilot-real-estate-analyzer-setup

ClawHub Source

Agents 4

<your-prefix>-scraper Property Scraper

Monitors MLS, Zillow, Redfin for new listings

pilot-stream-data pilot-cron pilot-archive

clawhub install pilot-stream-data pilot-cron pilot-archive

pilotctl set-hostname <your-prefix>-scraper

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: real-estate-analyzer"

<your-prefix>-analyzer Market Analyzer

Calculates valuations, cap rates, rental yields

pilot-metrics pilot-dataset pilot-task-router

clawhub install pilot-metrics pilot-dataset pilot-task-router

pilotctl set-hostname <your-prefix>-analyzer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-scraper "setup: real-estate-analyzer"

pilotctl handshake <your-prefix>-comparator "setup: real-estate-analyzer"

<your-prefix>-comparator Comp Analyzer

Pulls comps, adjusts for features, generates CMA reports

pilot-event-filter pilot-share pilot-review

clawhub install pilot-event-filter pilot-share pilot-review

pilotctl set-hostname <your-prefix>-comparator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: real-estate-analyzer"

pilotctl handshake <your-prefix>-notifier "setup: real-estate-analyzer"

<your-prefix>-notifier Deal Notifier

Scores deals by ROI, alerts investors via Slack/email

pilot-alert pilot-slack-bridge pilot-webhook-bridge

clawhub install pilot-alert pilot-slack-bridge pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-notifier

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-comparator "setup: real-estate-analyzer"

Data Flows

<your-prefix>-scraper → <your-prefix>-analyzer new-listing events :1002

<your-prefix>-analyzer → <your-prefix>-comparator valuation-request events :1002

<your-prefix>-comparator → <your-prefix>-notifier deal-score events :1002

<your-prefix>-notifier → external deal-alert notifications :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-analyzer — subscribe to new listings from scraper:

pilotctl subscribe <your-prefix>-scraper new-listing

# On <your-prefix>-scraper — publish a new listing:

pilotctl publish <your-prefix>-analyzer new-listing '{"mls_id":"MLS-2024-78432","address":"1425 Oak Valley Dr, Austin, TX","price":485000,"sqft":2200,"beds":4,"baths":2.5,"year_built":2018,"lot_sqft":7500,"source":"redfin"}'

# On <your-prefix>-comparator — subscribe to valuation requests:

pilotctl subscribe <your-prefix>-analyzer valuation-request

# On <your-prefix>-analyzer — publish a valuation request:

pilotctl publish <your-prefix>-comparator valuation-request '{"mls_id":"MLS-2024-78432","estimated_value":502000,"cap_rate":6.8,"rental_yield":8.2,"appreciation_1yr":4.5,"price_per_sqft":220}'

# On <your-prefix>-notifier — subscribe to deal scores:

pilotctl subscribe <your-prefix>-comparator deal-score

# On <your-prefix>-comparator — publish a deal score:

pilotctl publish <your-prefix>-notifier deal-score '{"mls_id":"MLS-2024-78432","deal_score":8.7,"comps_avg_price":510000,"price_delta_pct":-4.9,"roi_estimate":12.3,"recommendation":"strong_buy","cma_report_url":"https://reports.example.com/cma-78432.pdf"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (property scraping)

clawhub install pilot-stream-data pilot-cron pilot-archive

pilotctl set-hostname <your-prefix>-scraper

# On server 2 (market analysis)

clawhub install pilot-metrics pilot-dataset pilot-task-router

pilotctl set-hostname <your-prefix>-analyzer

# On server 3 (comparable analysis)

clawhub install pilot-event-filter pilot-share pilot-review

pilotctl set-hostname <your-prefix>-comparator

# On server 4 (deal notifications)

clawhub install pilot-alert pilot-slack-bridge pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-notifier

# On scraper:

pilotctl handshake <your-prefix>-analyzer "setup: real-estate-analyzer"

# On analyzer:

pilotctl handshake <your-prefix>-scraper "setup: real-estate-analyzer"

# On analyzer:

pilotctl handshake <your-prefix>-comparator "setup: real-estate-analyzer"

# On comparator:

pilotctl handshake <your-prefix>-analyzer "setup: real-estate-analyzer"

# On comparator:

pilotctl handshake <your-prefix>-notifier "setup: real-estate-analyzer"

# On notifier:

pilotctl handshake <your-prefix>-comparator "setup: real-estate-analyzer"

pilotctl trust

Recruitment Pipeline

intermediate 3 agents · 9 skills

Deploy a multi-agent recruitment pipeline that automates candidate sourcing, resume screening, and interview scheduling. Each agent handles a distinct stage of the hiring funnel, passing enriched candidate data downstream until interviews are booked and tracked.

pilot-discover pilot-stream-data pilot-metrics pilot-event-filter pilot-task-router pilot-alert pilot-webhook-bridge pilot-slack-bridge pilot-receipt

clawhub install pilot-recruitment-pipeline-setup

ClawHub Source

Agents 3

<your-prefix>-sourcer Candidate Sourcer

Scans job boards, LinkedIn profiles, and referral networks. Packages candidate profiles with match scores.

pilot-discover pilot-stream-data pilot-metrics

clawhub install pilot-discover pilot-stream-data pilot-metrics

pilotctl set-hostname <your-prefix>-sourcer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-screener "setup: recruitment-pipeline"

<your-prefix>-screener Resume Screener

Evaluates candidates against job requirements, scores skills, flags red flags.

pilot-event-filter pilot-task-router pilot-alert

clawhub install pilot-event-filter pilot-task-router pilot-alert

pilotctl set-hostname <your-prefix>-screener

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-sourcer "setup: recruitment-pipeline"

pilotctl handshake <your-prefix>-scheduler "setup: recruitment-pipeline"

<your-prefix>-scheduler Interview Scheduler

Coordinates interview slots, sends calendar invites, tracks hiring pipeline status.

pilot-webhook-bridge pilot-slack-bridge pilot-receipt

clawhub install pilot-webhook-bridge pilot-slack-bridge pilot-receipt

pilotctl set-hostname <your-prefix>-scheduler

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-screener "setup: recruitment-pipeline"

Data Flows

<your-prefix>-sourcer → <your-prefix>-screener candidate-profile events :1002

<your-prefix>-screener → <your-prefix>-scheduler screened-candidate events :1002

<your-prefix>-scheduler → external interview-invite via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-screener — subscribe to candidate profiles from sourcer:

pilotctl subscribe <your-prefix>-sourcer candidate-profile

# On <your-prefix>-scheduler — subscribe to screened candidates from screener:

pilotctl subscribe <your-prefix>-screener screened-candidate

# On <your-prefix>-sourcer — publish a candidate profile:

pilotctl publish <your-prefix>-screener candidate-profile '{"candidate":"Jane Doe","role":"Senior Backend Engineer","match_score":92,"source":"linkedin","skills":["Go","Kubernetes","PostgreSQL"]}'

# On <your-prefix>-screener — publish a screened candidate:

pilotctl publish <your-prefix>-scheduler screened-candidate '{"candidate":"Jane Doe","screen_score":88,"red_flags":[],"recommendation":"interview","available_slots":["2026-04-14T10:00Z","2026-04-15T14:00Z"]}'

# On <your-prefix>-scheduler — send an interview invite:

pilotctl publish <your-prefix>-scheduler interview-invite '{"candidate":"Jane Doe","interviewer":"John Smith","slot":"2026-04-14T10:00Z","calendar_link":"https://cal.example.com/abc123"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (candidate sourcer)

clawhub install pilot-discover pilot-stream-data pilot-metrics

pilotctl set-hostname <your-prefix>-sourcer

# On server 2 (resume screener)

clawhub install pilot-event-filter pilot-task-router pilot-alert

pilotctl set-hostname <your-prefix>-screener

# On server 3 (interview scheduler)

clawhub install pilot-webhook-bridge pilot-slack-bridge pilot-receipt

pilotctl set-hostname <your-prefix>-scheduler

# On sourcer:

pilotctl handshake <your-prefix>-screener "setup: recruitment-pipeline"

# On screener:

pilotctl handshake <your-prefix>-sourcer "setup: recruitment-pipeline"

# On screener:

pilotctl handshake <your-prefix>-scheduler "setup: recruitment-pipeline"

# On scheduler:

pilotctl handshake <your-prefix>-screener "setup: recruitment-pipeline"

pilotctl trust

Release Management

beginner 3 agents · 9 skills

Deploy an automated release pipeline with 3 agents that generate changelogs from merged PRs, manage semantic versioning and release tags, and announce releases across Slack, email, and documentation sites. Each agent handles a stage of the release process -- changelog generation, version coordination, and public announcement.

pilot-github-bridge pilot-share pilot-archive pilot-task-router pilot-receipt pilot-audit-log pilot-announce pilot-slack-bridge pilot-webhook-bridge

clawhub install pilot-release-management-setup

ClawHub Source

Agents 3

<your-prefix>-changelog-bot Changelog Bot

Scans merged PRs and commits, generates release notes and changelogs automatically.

pilot-github-bridge pilot-share pilot-archive

clawhub install pilot-github-bridge pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-changelog-bot

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-version-manager "setup: release-management"

<your-prefix>-version-manager Version Manager

Bumps semantic versions, tags releases, coordinates rollout schedules.

pilot-task-router pilot-receipt pilot-audit-log

clawhub install pilot-task-router pilot-receipt pilot-audit-log

pilotctl set-hostname <your-prefix>-version-manager

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-changelog-bot "setup: release-management"

pilotctl handshake <your-prefix>-announcer "setup: release-management"

<your-prefix>-announcer Release Announcer

Posts release announcements to Slack, email lists, and documentation sites.

pilot-announce pilot-slack-bridge pilot-webhook-bridge

clawhub install pilot-announce pilot-slack-bridge pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-announcer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-version-manager "setup: release-management"

Data Flows

<your-prefix>-changelog-bot → <your-prefix>-version-manager release-notes events :1002

<your-prefix>-version-manager → <your-prefix>-announcer release-tag events :1002

<your-prefix>-announcer → external release-announcement via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-version-manager — subscribe to release notes from changelog-bot:

pilotctl subscribe <your-prefix>-changelog-bot release-notes

# On <your-prefix>-announcer — subscribe to release tags from version-manager:

pilotctl subscribe <your-prefix>-version-manager release-tag

# On <your-prefix>-changelog-bot — publish release notes:

pilotctl publish <your-prefix>-version-manager release-notes '{"version":"1.5.0","date":"2026-04-10","changes":[{"type":"feature","description":"Add webhook retry logic"},{"type":"fix","description":"Fix race condition in event handler"}],"breaking":false}'

# On <your-prefix>-version-manager — publish a release tag:

pilotctl publish <your-prefix>-announcer release-tag '{"version":"v1.5.0","tag":"v1.5.0","artifacts":["linux-amd64","darwin-arm64"],"changelog_url":"https://example.com/releases/v1.5.0"}'

# The announcer receives the tag and dispatches announcements:

pilotctl publish <your-prefix>-announcer release-announcement '{"channel":"#releases","version":"v1.5.0","highlights":["Webhook retry logic","Race condition fix"],"migration_notes":"No breaking changes"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (changelog bot)

clawhub install pilot-github-bridge pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-changelog-bot

# On server 2 (version manager)

clawhub install pilot-task-router pilot-receipt pilot-audit-log

pilotctl set-hostname <your-prefix>-version-manager

# On server 3 (release announcer)

clawhub install pilot-announce pilot-slack-bridge pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-announcer

# On version-manager:

pilotctl handshake <your-prefix>-changelog-bot "setup: release-management"

# On changelog-bot:

pilotctl handshake <your-prefix>-version-manager "setup: release-management"

# On announcer:

pilotctl handshake <your-prefix>-version-manager "setup: release-management"

# On version-manager:

pilotctl handshake <your-prefix>-announcer "setup: release-management"

pilotctl trust

Sales Pipeline

intermediate 4 agents · 12 skills

Deploy a sales pipeline with 4 agents that automate lead generation, qualification, personalized outreach, and CRM synchronization. Each agent handles one stage of the funnel, passing enriched data downstream so deals flow from raw prospect to closed-won without manual handoff.

pilot-discover pilot-stream-data pilot-metrics pilot-event-filter pilot-task-router pilot-dataset pilot-email-bridge pilot-cron pilot-receipt pilot-webhook-bridge pilot-audit-log pilot-slack-bridge

clawhub install pilot-sales-pipeline-setup

ClawHub Source

Agents 4

<your-prefix>-prospector Lead Prospector

Finds and scores leads from web and inbound sources

pilot-discover pilot-stream-data pilot-metrics

clawhub install pilot-discover pilot-stream-data pilot-metrics

pilotctl set-hostname <your-prefix>-prospector

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-qualifier "setup: sales-pipeline"

<your-prefix>-qualifier Lead Qualifier

Evaluates leads against ICP, enriches, categorizes by tier

pilot-event-filter pilot-task-router pilot-dataset

clawhub install pilot-event-filter pilot-task-router pilot-dataset

pilotctl set-hostname <your-prefix>-qualifier

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-prospector "setup: sales-pipeline"

pilotctl handshake <your-prefix>-outreach "setup: sales-pipeline"

<your-prefix>-outreach Outreach Agent

Sends personalized email sequences, tracks engagement

pilot-email-bridge pilot-cron pilot-receipt

clawhub install pilot-email-bridge pilot-cron pilot-receipt

pilotctl set-hostname <your-prefix>-outreach

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-qualifier "setup: sales-pipeline"

pilotctl handshake <your-prefix>-crm-sync "setup: sales-pipeline"

<your-prefix>-crm-sync CRM Sync Agent

Syncs activity to CRM, maintains deal stages, reports forecasts

pilot-webhook-bridge pilot-audit-log pilot-slack-bridge

clawhub install pilot-webhook-bridge pilot-audit-log pilot-slack-bridge

pilotctl set-hostname <your-prefix>-crm-sync

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-outreach "setup: sales-pipeline"

Data Flows

<your-prefix>-prospector → <your-prefix>-qualifier raw-lead events :1002

<your-prefix>-qualifier → <your-prefix>-outreach qualified-lead events :1002

<your-prefix>-outreach → <your-prefix>-crm-sync engagement-event events :1002

<your-prefix>-crm-sync → external CRM updates via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-qualifier — subscribe to raw leads from prospector:

pilotctl subscribe <your-prefix>-prospector raw-lead

# On <your-prefix>-prospector — publish a raw lead:

pilotctl publish <your-prefix>-qualifier raw-lead '{"company":"Initech","domain":"initech.com","source":"linkedin","fit_score":82,"employees":450}'

# On <your-prefix>-outreach — subscribe to qualified leads:

pilotctl subscribe <your-prefix>-qualifier qualified-lead

# On <your-prefix>-qualifier — publish a qualified lead:

pilotctl publish <your-prefix>-outreach qualified-lead '{"company":"Initech","tier":"hot","icp_match":0.91,"contacts":["[email protected]"]}'

# On <your-prefix>-crm-sync — subscribe to engagement events:

pilotctl subscribe <your-prefix>-outreach engagement-event

# On <your-prefix>-outreach — publish an engagement event:

pilotctl publish <your-prefix>-crm-sync engagement-event '{"lead":"Initech","event":"reply","sentiment":"positive","next_action":"book_demo"}'

# On <your-prefix>-crm-sync — push to CRM:

pilotctl publish <your-prefix>-crm-sync crm-update '{"deal":"Initech","stage":"demo_scheduled","value":48000,"forecast":"commit"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (lead prospecting)

clawhub install pilot-discover pilot-stream-data pilot-metrics

pilotctl set-hostname <your-prefix>-prospector

# On server 2 (lead qualification)

clawhub install pilot-event-filter pilot-task-router pilot-dataset

pilotctl set-hostname <your-prefix>-qualifier

# On server 3 (outreach)

clawhub install pilot-email-bridge pilot-cron pilot-receipt

pilotctl set-hostname <your-prefix>-outreach

# On server 4 (CRM sync)

clawhub install pilot-webhook-bridge pilot-audit-log pilot-slack-bridge

pilotctl set-hostname <your-prefix>-crm-sync

# On prospector:

pilotctl handshake <your-prefix>-qualifier "setup: sales-pipeline"

# On qualifier:

pilotctl handshake <your-prefix>-prospector "setup: sales-pipeline"

# On qualifier:

pilotctl handshake <your-prefix>-outreach "setup: sales-pipeline"

# On outreach:

pilotctl handshake <your-prefix>-qualifier "setup: sales-pipeline"

# On outreach:

pilotctl handshake <your-prefix>-crm-sync "setup: sales-pipeline"

# On crm-sync:

pilotctl handshake <your-prefix>-outreach "setup: sales-pipeline"

pilotctl trust

Scientific Research Team

advanced 4 agents · 11 skills

A collaborative research pipeline that automates the scientific method across four specialized agents. The literature agent builds structured reviews from scientific databases, the hypothesis agent identifies research gaps and generates testable hypotheses, the experiment agent designs and runs protocols with statistical validation, and the report writer compiles findings into publication-ready documents with proper citations.

pilot-discover pilot-archive pilot-stream-data pilot-task-router pilot-priority-queue pilot-dataset pilot-audit-log pilot-metrics pilot-share pilot-announce pilot-webhook-bridge

clawhub install pilot-scientific-research-team-setup

ClawHub Source

Agents 4

<your-prefix>-literature Literature Agent

Structured reviews with gaps and citations" }

pilot-discover pilot-archive pilot-stream-data

clawhub install pilot-discover pilot-archive pilot-stream-data

pilotctl set-hostname <your-prefix>-literature

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-hypothesis "setup: scientific-research-team"

<your-prefix>-hypothesis Hypothesis Agent

Literature reviews with identified gaps" },

pilot-task-router pilot-priority-queue pilot-dataset

clawhub install pilot-task-router pilot-priority-queue pilot-dataset

pilotctl set-hostname <your-prefix>-hypothesis

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-literature "setup: scientific-research-team"

pilotctl handshake <your-prefix>-experiment "setup: scientific-research-team"

<your-prefix>-experiment Experiment Agent

Hypotheses to test" },

pilot-task-router pilot-audit-log pilot-metrics

clawhub install pilot-task-router pilot-audit-log pilot-metrics

pilotctl set-hostname <your-prefix>-experiment

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-hypothesis "setup: scientific-research-team"

pilotctl handshake <your-prefix>-report "setup: scientific-research-team"

<your-prefix>-report Report Writer

Experimental results to compile" },

pilot-share pilot-announce pilot-webhook-bridge

clawhub install pilot-share pilot-announce pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-report

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-experiment "setup: scientific-research-team"

Data Flows

<your-prefix>-literature → <your-prefix>-hypothesis literature synthesis with gaps and citations :1002

<your-prefix>-hypothesis → <your-prefix>-experiment ranked research hypotheses with protocols :1002

<your-prefix>-experiment → <your-prefix>-report experimental results with statistical analysis :1002

<your-prefix>-report → external published research reports :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-literature -- publish a literature synthesis:

pilotctl publish <your-prefix>-hypothesis literature-synthesis '{"topic":"transformer attention scaling laws","papers_reviewed":47,"key_findings":["linear attention underperforms at >1B params","flash attention reduces memory 2-4x","mixture-of-experts shows sublinear scaling"],"gaps":["no study compares all three on identical hardware","sparse attention + MoE interaction unknown"],"citations":["vaswani2017","dao2022","fedus2022"]}'

# On <your-prefix>-hypothesis -- publish a ranked hypothesis:

pilotctl publish <your-prefix>-experiment research-hypothesis '{"hypothesis_id":"H-031","statement":"Combining flash attention with top-2 MoE routing achieves superlinear throughput scaling from 1B to 10B parameters","novelty_score":0.87,"feasibility_score":0.72,"required_compute_hours":480,"methodology":"controlled_benchmark","variables":{"independent":"model_size","dependent":"throughput_per_param","controlled":["hardware","batch_size","sequence_length"]}}'

# On <your-prefix>-experiment -- publish results:

pilotctl publish <your-prefix>-report experiment-result '{"hypothesis_id":"H-031","status":"partially_supported","findings":{"scaling_exponent":1.12,"ci_95":[1.04,1.20],"p_value":0.003,"effect_size":"medium","n_runs":24},"methodology":"A/B benchmark on 8xA100 cluster","artifacts":["scaling_curve.png","raw_benchmarks.csv"]}'

# On <your-prefix>-report -- publish the final report (port 443 for secure external access):

pilotctl publish <your-prefix>-report research-report '{"title":"Flash Attention + MoE: Superlinear Scaling in Large Transformers","abstract":"We demonstrate that combining flash attention with top-2 MoE routing yields a 1.12x scaling exponent...","sections":["introduction","related_work","methodology","results","discussion","conclusion"],"citation_count":23,"status":"ready_for_review"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On literature review server

clawhub install pilot-discover pilot-archive pilot-stream-data

pilotctl set-hostname <your-prefix>-literature

# On hypothesis generation server

clawhub install pilot-task-router pilot-priority-queue pilot-dataset

pilotctl set-hostname <your-prefix>-hypothesis

# On experiment execution server

clawhub install pilot-task-router pilot-audit-log pilot-metrics

pilotctl set-hostname <your-prefix>-experiment

# On report writing server

clawhub install pilot-share pilot-announce pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-report

# literature <-> hypothesis (literature synthesis)

# On literature:

pilotctl handshake <your-prefix>-hypothesis "setup: scientific-research-team"

# On hypothesis:

pilotctl handshake <your-prefix>-literature "setup: scientific-research-team"

# hypothesis <-> experiment (research hypotheses)

# On hypothesis:

pilotctl handshake <your-prefix>-experiment "setup: scientific-research-team"

# On experiment:

pilotctl handshake <your-prefix>-hypothesis "setup: scientific-research-team"

# experiment <-> report (experimental results)

# On experiment:

pilotctl handshake <your-prefix>-report "setup: scientific-research-team"

# On report:

pilotctl handshake <your-prefix>-experiment "setup: scientific-research-team"

pilotctl trust

Security Operations Center

advanced 4 agents · 15 skills

A SOC pipeline that collects security events, analyzes patterns, replays incidents for forensics, and enforces blocks automatically. The enforcer maintains a live blocklist and can quarantine compromised nodes. A dashboard agent provides real-time network visibility.

pilot-event-log pilot-audit-log pilot-stream-data pilot-cron pilot-event-filter pilot-event-replay pilot-alert pilot-priority-queue pilot-blocklist pilot-quarantine pilot-webhook-bridge pilot-metrics pilot-slack-bridge pilot-network-map pilot-mesh-status

clawhub install pilot-security-operations-center-setup

ClawHub Source

Agents 4

<your-prefix>-collector Log Collector

Aggregates security events

pilot-event-log pilot-audit-log pilot-stream-data pilot-cron

clawhub install pilot-event-log pilot-audit-log pilot-stream-data pilot-cron

pilotctl set-hostname <your-prefix>-collector

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: security-operations-center"

<your-prefix>-analyzer Threat Analyzer

Raw events" },

pilot-event-filter pilot-event-replay pilot-alert pilot-priority-queue

clawhub install pilot-event-filter pilot-event-replay pilot-alert pilot-priority-queue

pilotctl set-hostname <your-prefix>-analyzer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-collector "setup: security-operations-center"

pilotctl handshake <your-prefix>-enforcer "setup: security-operations-center"

pilotctl handshake <your-prefix>-dashboard "setup: security-operations-center"

<your-prefix>-enforcer Threat Enforcer

Threat verdicts" },

pilot-blocklist pilot-quarantine pilot-webhook-bridge pilot-audit-log

clawhub install pilot-blocklist pilot-quarantine pilot-webhook-bridge pilot-audit-log

pilotctl set-hostname <your-prefix>-enforcer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: security-operations-center"

pilotctl handshake <your-prefix>-dashboard "setup: security-operations-center"

<your-prefix>-dashboard SOC Dashboard

Classified threats" },

pilot-metrics pilot-slack-bridge pilot-network-map pilot-mesh-status

clawhub install pilot-metrics pilot-slack-bridge pilot-network-map pilot-mesh-status

pilotctl set-hostname <your-prefix>-dashboard

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: security-operations-center"

pilotctl handshake <your-prefix>-enforcer "setup: security-operations-center"

Data Flows

<your-prefix>-collector → <your-prefix>-analyzer raw security events :1002

<your-prefix>-analyzer → <your-prefix>-enforcer threat verdicts :1002

<your-prefix>-analyzer → <your-prefix>-dashboard classified threats :1002

<your-prefix>-enforcer → <your-prefix>-dashboard enforcement actions :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-collector — stream security events to analyzer:

pilotctl publish <your-prefix>-analyzer security-event '{"type":"auth_failure","source":"10.0.1.50","user":"admin","attempts":15}'

pilotctl publish <your-prefix>-analyzer security-event '{"type":"port_scan","source":"203.0.113.42","ports_scanned":1024}'

# On <your-prefix>-analyzer — classify threat and route:

pilotctl publish <your-prefix>-enforcer threat-verdict '{"source":"203.0.113.42","threat":"port_scan","severity":"high","action":"block"}'

pilotctl publish <your-prefix>-dashboard threat-alert '{"source":"203.0.113.42","threat":"port_scan","severity":"high"}'

# On <your-prefix>-enforcer — block and report:

pilotctl publish <your-prefix>-dashboard enforcement-action '{"source":"203.0.113.42","action":"blocked","rule":"auto-block-port-scan"}'

# On <your-prefix>-dashboard — subscribe to all feeds:

pilotctl subscribe <your-prefix>-analyzer threat-alert

pilotctl subscribe <your-prefix>-enforcer enforcement-action

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On log collection node

clawhub install pilot-event-log pilot-audit-log pilot-stream-data pilot-cron

pilotctl set-hostname <your-prefix>-collector

# On analysis node

clawhub install pilot-event-filter pilot-event-replay pilot-alert pilot-priority-queue

pilotctl set-hostname <your-prefix>-analyzer

# On enforcement node

clawhub install pilot-blocklist pilot-quarantine pilot-webhook-bridge pilot-audit-log

pilotctl set-hostname <your-prefix>-enforcer

# On dashboard node

clawhub install pilot-metrics pilot-slack-bridge pilot-network-map pilot-mesh-status

pilotctl set-hostname <your-prefix>-dashboard

# collector <-> analyzer

# On collector:

pilotctl handshake <your-prefix>-analyzer "soc pipeline"

# On analyzer:

pilotctl handshake <your-prefix>-collector "soc pipeline"

# analyzer <-> enforcer

# On analyzer:

pilotctl handshake <your-prefix>-enforcer "soc pipeline"

# On enforcer:

pilotctl handshake <your-prefix>-analyzer "soc pipeline"

# analyzer <-> dashboard

# On analyzer:

pilotctl handshake <your-prefix>-dashboard "soc pipeline"

# On dashboard:

pilotctl handshake <your-prefix>-analyzer "soc pipeline"

# enforcer <-> dashboard

# On enforcer:

pilotctl handshake <your-prefix>-dashboard "soc pipeline"

# On dashboard:

pilotctl handshake <your-prefix>-enforcer "soc pipeline"

pilotctl trust

Smart Home Coordinator

intermediate 4 agents · 10 skills

A decentralized smart home system where sensors, a central brain, device actuators, and a dashboard collaborate to maintain comfort and efficiency. The brain resolves conflicts between goals (comfort vs. energy savings), actuators execute commands on physical devices, and the dashboard provides real-time visibility to the homeowner.

pilot-stream-data pilot-cron pilot-metrics pilot-event-filter pilot-task-router pilot-consensus pilot-receipt pilot-audit-log pilot-webhook-bridge pilot-slack-bridge

clawhub install pilot-smart-home-coordinator-setup

ClawHub Source

Agents 4

<your-prefix>-sensor-hub Sensor Hub

Collects and normalizes sensor readings

pilot-stream-data pilot-cron pilot-metrics

clawhub install pilot-stream-data pilot-cron pilot-metrics

pilotctl set-hostname <your-prefix>-sensor-hub

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-brain "setup: smart-home-coordinator"

<your-prefix>-brain Home Brain

Resolves goals, issues device commands

pilot-event-filter pilot-task-router pilot-consensus

clawhub install pilot-event-filter pilot-task-router pilot-consensus

pilotctl set-hostname <your-prefix>-brain

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-sensor-hub "setup: smart-home-coordinator"

pilotctl handshake <your-prefix>-actuator "setup: smart-home-coordinator"

pilotctl handshake <your-prefix>-dashboard "setup: smart-home-coordinator"

<your-prefix>-actuator Device Actuator

Executes commands on devices, reports results

pilot-task-router pilot-receipt pilot-audit-log

clawhub install pilot-task-router pilot-receipt pilot-audit-log

pilotctl set-hostname <your-prefix>-actuator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-brain "setup: smart-home-coordinator"

<your-prefix>-dashboard Home Dashboard

Displays home status, sends daily summaries

pilot-metrics pilot-webhook-bridge pilot-slack-bridge

clawhub install pilot-metrics pilot-webhook-bridge pilot-slack-bridge

pilotctl set-hostname <your-prefix>-dashboard

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-brain "setup: smart-home-coordinator"

Data Flows

<your-prefix>-sensor-hub → <your-prefix>-brain sensor readings :1002

<your-prefix>-brain → <your-prefix>-actuator device commands :1002

<your-prefix>-actuator → <your-prefix>-brain action confirmations :1002

<your-prefix>-brain → <your-prefix>-dashboard home state updates :1002

<your-prefix>-dashboard → external daily summary via Slack/email :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-sensor-hub -- publish sensor readings:

pilotctl publish <your-prefix>-brain sensor-reading '{"room":"living-room","temperature_c":23.4,"humidity_pct":45,"light_lux":320,"motion":false,"energy_w":1250,"timestamp":"2026-04-09T14:30:00Z"}'

# On <your-prefix>-brain -- publish a device command:

pilotctl publish <your-prefix>-actuator device-command '{"device":"hvac-main","action":"set_temperature","params":{"target_c":22,"mode":"cool"},"reason":"temperature above comfort threshold","priority":"normal"}'

# On <your-prefix>-actuator -- publish action confirmation:

pilotctl publish <your-prefix>-brain action-confirm '{"device":"hvac-main","action":"set_temperature","status":"success","current_target_c":22,"response_time_ms":340}'

# On <your-prefix>-brain -- publish home state to dashboard:

pilotctl publish <your-prefix>-dashboard home-state '{"rooms":{"living-room":{"temp_c":23.4,"target_c":22,"hvac":"cooling"},"bedroom":{"temp_c":21.0,"target_c":21,"hvac":"idle"}},"total_energy_w":1250,"mode":"comfort"}'

# On <your-prefix>-dashboard -- subscribe to home state:

pilotctl subscribe home-state

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (sensor hub)

clawhub install pilot-stream-data pilot-cron pilot-metrics

pilotctl set-hostname <your-prefix>-sensor-hub

# On server 2 (home brain)

clawhub install pilot-event-filter pilot-task-router pilot-consensus

pilotctl set-hostname <your-prefix>-brain

# On server 3 (device actuator)

clawhub install pilot-task-router pilot-receipt pilot-audit-log

pilotctl set-hostname <your-prefix>-actuator

# On server 4 (home dashboard)

clawhub install pilot-metrics pilot-webhook-bridge pilot-slack-bridge

pilotctl set-hostname <your-prefix>-dashboard

# sensor-hub <-> brain (sensor data flow)

# On sensor-hub:

pilotctl handshake <your-prefix>-brain "setup: smart-home-coordinator"

# On brain:

pilotctl handshake <your-prefix>-sensor-hub "setup: smart-home-coordinator"

# brain <-> actuator (device commands and confirmations)

# On brain:

pilotctl handshake <your-prefix>-actuator "setup: smart-home-coordinator"

# On actuator:

pilotctl handshake <your-prefix>-brain "setup: smart-home-coordinator"

# brain <-> dashboard (home state updates)

# On brain:

pilotctl handshake <your-prefix>-dashboard "setup: smart-home-coordinator"

# On dashboard:

pilotctl handshake <your-prefix>-brain "setup: smart-home-coordinator"

pilotctl trust

Social Media Manager

beginner 3 agents · 8 skills

Deploy a social media management system where a planner analyzes trends and audience data to build a content calendar, a creator generates platform-specific posts from those briefs, and an analyst tracks engagement metrics and feeds performance insights back to the planner. The three agents form a continuous feedback loop that improves content strategy over time.

pilot-cron pilot-stream-data pilot-metrics pilot-task-router pilot-share pilot-receipt pilot-event-log pilot-alert

clawhub install pilot-social-media-manager-setup

ClawHub Source

Agents 3

<your-prefix>-planner Content Planner

Analyzes trends, competitor activity, and audience engagement to plan a content calendar and optimal posting times.

pilot-cron pilot-stream-data pilot-metrics

clawhub install pilot-cron pilot-stream-data pilot-metrics

pilotctl set-hostname <your-prefix>-planner

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-creator "setup: social-media-manager"

pilotctl handshake <your-prefix>-analyst "setup: social-media-manager"

<your-prefix>-creator Content Creator

Generates platform-specific posts (LinkedIn, X, Instagram) from the planner's brief in the brand voice.

pilot-task-router pilot-share pilot-receipt

clawhub install pilot-task-router pilot-share pilot-receipt

pilotctl set-hostname <your-prefix>-creator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-planner "setup: social-media-manager"

pilotctl handshake <your-prefix>-analyst "setup: social-media-manager"

<your-prefix>-analyst Performance Analyst

Tracks cross-platform engagement metrics, identifies top performers, and feeds insights back to the planner.

pilot-metrics pilot-event-log pilot-alert

clawhub install pilot-metrics pilot-event-log pilot-alert

pilotctl set-hostname <your-prefix>-analyst

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-creator "setup: social-media-manager"

pilotctl handshake <your-prefix>-planner "setup: social-media-manager"

Data Flows

<your-prefix>-planner → <your-prefix>-creator content-brief :1002

<your-prefix>-creator → <your-prefix>-analyst post-published :1002

<your-prefix>-analyst → <your-prefix>-planner performance-insight :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-creator -- subscribe to content briefs:

pilotctl subscribe <your-prefix>-planner content-brief

# On <your-prefix>-analyst -- subscribe to published posts:

pilotctl subscribe <your-prefix>-creator post-published

# On <your-prefix>-planner -- subscribe to performance insights:

pilotctl subscribe <your-prefix>-analyst performance-insight

# On <your-prefix>-planner -- publish a content brief:

pilotctl publish <your-prefix>-creator content-brief '{"platforms":["linkedin","x"],"topic":"AI in DevOps","angle":"practical tips","tone":"professional","post_time":"2026-04-10T09:00:00Z","hashtags":["#AIDevOps","#Automation"]}'

# On <your-prefix>-creator -- publish post metadata after posting:

pilotctl publish <your-prefix>-analyst post-published '{"post_id":"li-92841","platform":"linkedin","topic":"AI in DevOps","posted_at":"2026-04-10T09:00:00Z","char_count":1200,"hashtags":["#AIDevOps","#Automation"]}'

# On <your-prefix>-analyst -- publish insights back to planner:

pilotctl publish <your-prefix>-planner performance-insight '{"period":"2026-W15","top_platform":"linkedin","top_topic":"AI in DevOps","impressions":12400,"engagement_rate":4.2,"recommendation":"Increase LinkedIn frequency, morning posts outperform afternoon by 35%"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (content planner)

clawhub install pilot-cron pilot-stream-data pilot-metrics

pilotctl set-hostname <your-prefix>-planner

# On server 2 (content creator)

clawhub install pilot-task-router pilot-share pilot-receipt

pilotctl set-hostname <your-prefix>-creator

# On server 3 (performance analyst)

clawhub install pilot-metrics pilot-event-log pilot-alert

pilotctl set-hostname <your-prefix>-analyst

# planner <-> creator

# On planner:

pilotctl handshake <your-prefix>-creator "setup: social-media-manager"

# On creator:

pilotctl handshake <your-prefix>-planner "setup: social-media-manager"

# creator <-> analyst

# On creator:

pilotctl handshake <your-prefix>-analyst "setup: social-media-manager"

# On analyst:

pilotctl handshake <your-prefix>-creator "setup: social-media-manager"

# analyst <-> planner

# On analyst:

pilotctl handshake <your-prefix>-planner "setup: social-media-manager"

# On planner:

pilotctl handshake <your-prefix>-analyst "setup: social-media-manager"

pilotctl trust

Status Page

beginner 3 agents · 9 skills

Deploy a status page pipeline with 3 agents that automate service monitoring, status aggregation, and public incident communication. Each agent handles one stage of the pipeline, turning endpoint health checks into a live public status page with incident notifications for subscribers.

pilot-health pilot-cron pilot-metrics pilot-event-filter pilot-dataset pilot-audit-log pilot-webhook-bridge pilot-announce pilot-slack-bridge

clawhub install pilot-status-page-setup

ClawHub Source

Agents 3

<your-prefix>-monitor Service Monitor

Pings endpoints, checks response times, detects outages

pilot-health pilot-cron pilot-metrics

clawhub install pilot-health pilot-cron pilot-metrics

pilotctl set-hostname <your-prefix>-monitor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-aggregator "setup: status-page"

<your-prefix>-aggregator Status Aggregator

Combines health checks into system status, tracks uptime

pilot-event-filter pilot-dataset pilot-audit-log

clawhub install pilot-event-filter pilot-dataset pilot-audit-log

pilotctl set-hostname <your-prefix>-aggregator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-monitor "setup: status-page"

pilotctl handshake <your-prefix>-publisher "setup: status-page"

<your-prefix>-publisher Status Publisher

Updates status page, sends incident notifications

pilot-webhook-bridge pilot-announce pilot-slack-bridge

clawhub install pilot-webhook-bridge pilot-announce pilot-slack-bridge

pilotctl set-hostname <your-prefix>-publisher

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-aggregator "setup: status-page"

Data Flows

<your-prefix>-monitor → <your-prefix>-aggregator health-check events :1002

<your-prefix>-aggregator → <your-prefix>-publisher status-update events :1002

<your-prefix>-publisher → external incident-notification via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-aggregator -- subscribe to health checks from monitor:

pilotctl subscribe <your-prefix>-monitor health-check

# On <your-prefix>-publisher -- subscribe to status updates:

pilotctl subscribe <your-prefix>-aggregator status-update

# On <your-prefix>-monitor -- publish a health check:

pilotctl publish <your-prefix>-aggregator health-check '{"service":"api-gateway","endpoint":"https://api.acme.com/health","status":"degraded","response_ms":2340,"threshold_ms":500,"timestamp":"2025-03-15T14:22:00Z"}'

# On <your-prefix>-aggregator -- publish a status update to the publisher:

pilotctl publish <your-prefix>-publisher status-update '{"overall_status":"degraded","incident":true,"incident_id":"INC-2025-0018","affected_services":["api-gateway"],"uptime_24h":99.2,"message":"API gateway experiencing elevated response times"}'

# The publisher sends incident notification to subscribers:

pilotctl publish <your-prefix>-publisher incident-notification '{"channel":"#incidents","text":"Incident INC-2025-0018: API gateway degraded - elevated response times detected","severity":"warning","status_page_url":"https://status.acme.com","subscribers_notified":142}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (service monitor)

clawhub install pilot-health pilot-cron pilot-metrics

pilotctl set-hostname <your-prefix>-monitor

# On server 2 (status aggregator)

clawhub install pilot-event-filter pilot-dataset pilot-audit-log

pilotctl set-hostname <your-prefix>-aggregator

# On server 3 (status publisher)

clawhub install pilot-webhook-bridge pilot-announce pilot-slack-bridge

pilotctl set-hostname <your-prefix>-publisher

# monitor <-> aggregator

# On monitor:

pilotctl handshake <your-prefix>-aggregator "setup: status-page"

# On aggregator:

pilotctl handshake <your-prefix>-monitor "setup: status-page"

# aggregator <-> publisher

# On aggregator:

pilotctl handshake <your-prefix>-publisher "setup: status-page"

# On publisher:

pilotctl handshake <your-prefix>-aggregator "setup: status-page"

pilotctl trust

Supply Chain Orchestrator

advanced 4 agents · 10 skills

An end-to-end supply chain orchestration pipeline coordinating inventory management, logistics routing, procurement, and regulatory compliance across four specialized agents. The inventory manager monitors stock levels and predicts demand, triggering reorder flows that cascade through procurement for supplier negotiation, routing for delivery optimization, and compliance for regulatory validation before any goods move.

pilot-metrics pilot-cron pilot-alert pilot-stream-data pilot-task-router pilot-receipt pilot-webhook-bridge pilot-audit-log pilot-escrow pilot-event-filter

clawhub install pilot-supply-chain-orchestrator-setup

ClawHub Source

Agents 4

<your-prefix>-inventory Inventory Manager

Reorder requests when stock is low" },

pilot-metrics pilot-cron pilot-alert pilot-stream-data

clawhub install pilot-metrics pilot-cron pilot-alert pilot-stream-data

pilotctl set-hostname <your-prefix>-inventory

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-procurement "setup: supply-chain-orchestrator"

pilotctl handshake <your-prefix>-routing "setup: supply-chain-orchestrator"

pilotctl handshake <your-prefix>-compliance "setup: supply-chain-orchestrator"

<your-prefix>-routing Logistics Router

Fulfillment orders to route" },

pilot-task-router pilot-stream-data pilot-receipt

clawhub install pilot-task-router pilot-stream-data pilot-receipt

pilotctl set-hostname <your-prefix>-routing

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-inventory "setup: supply-chain-orchestrator"

pilotctl handshake <your-prefix>-compliance "setup: supply-chain-orchestrator"

<your-prefix>-procurement Procurement Agent

Reorder requests from inventory" },

pilot-webhook-bridge pilot-audit-log pilot-escrow

clawhub install pilot-webhook-bridge pilot-audit-log pilot-escrow

pilotctl set-hostname <your-prefix>-procurement

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-inventory "setup: supply-chain-orchestrator"

pilotctl handshake <your-prefix>-compliance "setup: supply-chain-orchestrator"

<your-prefix>-compliance Compliance Checker

Purchase orders to validate" },

pilot-audit-log pilot-event-filter pilot-alert

clawhub install pilot-audit-log pilot-event-filter pilot-alert

pilotctl set-hostname <your-prefix>-compliance

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-procurement "setup: supply-chain-orchestrator"

pilotctl handshake <your-prefix>-routing "setup: supply-chain-orchestrator"

pilotctl handshake <your-prefix>-inventory "setup: supply-chain-orchestrator"

Data Flows

<your-prefix>-inventory → <your-prefix>-procurement reorder requests when stock drops below threshold :1002

<your-prefix>-inventory → <your-prefix>-routing fulfillment orders for customer deliveries :1002

<your-prefix>-procurement → <your-prefix>-compliance purchase orders requiring regulatory validation :1002

<your-prefix>-routing → <your-prefix>-compliance shipping manifests for export/import checks :1002

<your-prefix>-compliance → <your-prefix>-inventory compliance clearance to release held stock :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-inventory -- trigger a reorder when stock is low:

pilotctl publish <your-prefix>-procurement reorder-request '{"sku":"WH-4821","warehouse":"us-east-1","current_qty":12,"reorder_point":50,"suggested_qty":200}'

# On <your-prefix>-procurement -- place a purchase order after selecting supplier:

pilotctl publish <your-prefix>-compliance purchase-order '{"po_id":"PO-9934","supplier":"GlobalParts Inc","sku":"WH-4821","qty":200,"unit_price":14.50,"currency":"USD","origin_country":"CN"}'

# On <your-prefix>-inventory -- create a fulfillment order:

pilotctl publish <your-prefix>-routing fulfillment-order '{"order_id":"ORD-77201","sku":"WH-4821","qty":5,"dest_zip":"94105","priority":"standard"}'

# On <your-prefix>-routing -- submit shipping manifest for compliance:

pilotctl publish <your-prefix>-compliance shipping-manifest '{"manifest_id":"SHP-3301","carrier":"FedEx","origin":"us-east-1","dest":"94105","items":[{"sku":"WH-4821","qty":5,"weight_kg":2.3}]}'

# On <your-prefix>-compliance -- issue clearance:

pilotctl publish <your-prefix>-inventory compliance-clearance '{"ref_id":"PO-9934","status":"approved","notes":"No restricted items, customs docs generated"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On inventory warehouse server

clawhub install pilot-metrics pilot-cron pilot-alert pilot-stream-data

pilotctl set-hostname <your-prefix>-inventory

# On logistics routing server

clawhub install pilot-task-router pilot-stream-data pilot-receipt

pilotctl set-hostname <your-prefix>-routing

# On procurement server

clawhub install pilot-webhook-bridge pilot-audit-log pilot-escrow

pilotctl set-hostname <your-prefix>-procurement

# On compliance server

clawhub install pilot-audit-log pilot-event-filter pilot-alert

pilotctl set-hostname <your-prefix>-compliance

# inventory <-> procurement (reorder requests)

# On inventory:

pilotctl handshake <your-prefix>-procurement "setup: supply-chain-orchestrator"

# On procurement:

pilotctl handshake <your-prefix>-inventory "setup: supply-chain-orchestrator"

# inventory <-> routing (fulfillment orders)

# On inventory:

pilotctl handshake <your-prefix>-routing "setup: supply-chain-orchestrator"

# On routing:

pilotctl handshake <your-prefix>-inventory "setup: supply-chain-orchestrator"

# procurement <-> compliance (purchase orders)

# On procurement:

pilotctl handshake <your-prefix>-compliance "setup: supply-chain-orchestrator"

# On compliance:

pilotctl handshake <your-prefix>-procurement "setup: supply-chain-orchestrator"

# routing <-> compliance (shipping manifests)

# On routing:

pilotctl handshake <your-prefix>-compliance "setup: supply-chain-orchestrator"

# On compliance:

pilotctl handshake <your-prefix>-routing "setup: supply-chain-orchestrator"

# compliance <-> inventory (compliance clearance)

# On compliance:

pilotctl handshake <your-prefix>-inventory "setup: supply-chain-orchestrator"

# On inventory:

pilotctl handshake <your-prefix>-compliance "setup: supply-chain-orchestrator"

pilotctl trust

Swarm Task Farm

advanced 5 agents · 11 skills

A self-organizing compute swarm. Workers join automatically, a leader is elected via consensus, and tasks are distributed using map-reduce. Failed tasks retry automatically. A monitor agent tracks swarm health and reports to Slack.

pilot-leader-election pilot-formation pilot-task-router pilot-broadcast pilot-swarm-join pilot-map-reduce pilot-task-retry pilot-metrics pilot-task-monitor pilot-mesh-status pilot-slack-bridge

clawhub install pilot-swarm-task-farm-setup

ClawHub Source

Agents 3

<your-prefix>-leader Swarm Leader

Work units" },

pilot-leader-election pilot-formation pilot-task-router pilot-broadcast

clawhub install pilot-leader-election pilot-formation pilot-task-router pilot-broadcast

pilotctl set-hostname <your-prefix>-leader

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-worker-1 "setup: swarm-task-farm"

pilotctl handshake <your-prefix>-worker-2 "setup: swarm-task-farm"

pilotctl handshake <your-prefix>-worker-3 "setup: swarm-task-farm"

pilotctl handshake <your-prefix>-monitor "setup: swarm-task-farm"

<your-prefix>-worker-N Compute Worker

Work units" },

pilot-swarm-join pilot-map-reduce pilot-task-retry pilot-metrics

clawhub install pilot-swarm-join pilot-map-reduce pilot-task-retry pilot-metrics

pilotctl set-hostname <your-prefix>-worker-N

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-leader "setup: swarm-task-farm"

pilotctl handshake <your-prefix>-monitor "setup: swarm-task-farm"

<your-prefix>-monitor Swarm Monitor

Worker health" },

pilot-task-monitor pilot-mesh-status pilot-slack-bridge pilot-metrics

clawhub install pilot-task-monitor pilot-mesh-status pilot-slack-bridge pilot-metrics

pilotctl set-hostname <your-prefix>-monitor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-leader "setup: swarm-task-farm"

pilotctl handshake <your-prefix>-worker-1 "setup: swarm-task-farm"

pilotctl handshake <your-prefix>-worker-2 "setup: swarm-task-farm"

pilotctl handshake <your-prefix>-worker-3 "setup: swarm-task-farm"

Data Flows

<your-prefix>-leader → <your-prefix>-worker-* task assignments :1002

<your-prefix>-worker-* → <your-prefix>-leader completed results :1002

<your-prefix>-worker-* → <your-prefix>-monitor health metrics :1002

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-leader — distribute tasks to workers:

pilotctl publish <your-prefix>-worker-1 task-assignment '{"task_id":"T-001","type":"image_resize","input":"batch-a.zip"}'

pilotctl publish <your-prefix>-worker-2 task-assignment '{"task_id":"T-002","type":"image_resize","input":"batch-b.zip"}'

pilotctl publish <your-prefix>-worker-3 task-assignment '{"task_id":"T-003","type":"image_resize","input":"batch-c.zip"}'

# On <your-prefix>-worker-1 — complete and report:

pilotctl publish <your-prefix>-leader task-result '{"task_id":"T-001","status":"success","output":"batch-a-resized.zip","duration_s":34}'

pilotctl publish <your-prefix>-monitor worker-metrics '{"worker":"worker-1","cpu":72,"tasks_done":15,"queue":0}'

# On <your-prefix>-monitor — check swarm health:

pilotctl subscribe <your-prefix>-worker-1 worker-metrics

pilotctl subscribe <your-prefix>-worker-2 worker-metrics

pilotctl subscribe <your-prefix>-worker-3 worker-metrics

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On leader node

clawhub install pilot-leader-election pilot-formation pilot-task-router pilot-broadcast

pilotctl set-hostname <your-prefix>-leader

# On each worker node (repeat for worker-1, worker-2, worker-3)

clawhub install pilot-swarm-join pilot-map-reduce pilot-task-retry pilot-metrics

pilotctl set-hostname <your-prefix>-worker-1

# On monitor node

clawhub install pilot-task-monitor pilot-mesh-status pilot-slack-bridge pilot-metrics

pilotctl set-hostname <your-prefix>-monitor

# On leader:

pilotctl handshake <your-prefix>-worker-1 "swarm task farm"

pilotctl handshake <your-prefix>-worker-2 "swarm task farm"

pilotctl handshake <your-prefix>-worker-3 "swarm task farm"

pilotctl handshake <your-prefix>-monitor "swarm task farm"

# On worker-1:

pilotctl handshake <your-prefix>-leader "swarm task farm"

pilotctl handshake <your-prefix>-monitor "swarm task farm"

# On worker-2:

pilotctl handshake <your-prefix>-leader "swarm task farm"

pilotctl handshake <your-prefix>-monitor "swarm task farm"

# On worker-3:

pilotctl handshake <your-prefix>-leader "swarm task farm"

pilotctl handshake <your-prefix>-monitor "swarm task farm"

# On monitor:

pilotctl handshake <your-prefix>-leader "swarm task farm"

pilotctl handshake <your-prefix>-worker-1 "swarm task farm"

pilotctl handshake <your-prefix>-worker-2 "swarm task farm"

pilotctl handshake <your-prefix>-worker-3 "swarm task farm"

pilotctl trust

Threat Intelligence

advanced 4 agents · 12 skills

A threat intelligence platform that aggregates indicators of compromise from multiple sources, enriches them with contextual data, analyzes threat severity and campaign attribution, and distributes actionable intelligence to security infrastructure. The collector ingests raw feeds, the enricher correlates and contextualizes IOCs, the analyzer scores threats and maps to frameworks, and the distributor pushes formatted intelligence to downstream consumers.

pilot-stream-data pilot-cron pilot-archive pilot-dataset pilot-task-router pilot-event-filter pilot-metrics pilot-consensus pilot-alert pilot-webhook-bridge pilot-announce pilot-audit-log

clawhub install pilot-threat-intelligence-setup

ClawHub Source

Agents 4

<your-prefix>-collector Intel Collector

Aggregates threat feeds from OSINT, honeypots, CVE databases

pilot-stream-data pilot-cron pilot-archive

clawhub install pilot-stream-data pilot-cron pilot-archive

pilotctl set-hostname <your-prefix>-collector

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-enricher "setup: threat-intelligence"

<your-prefix>-enricher Threat Enricher

Raw IOCs to enrich" },

pilot-dataset pilot-task-router pilot-event-filter

clawhub install pilot-dataset pilot-task-router pilot-event-filter

pilotctl set-hostname <your-prefix>-enricher

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-collector "setup: threat-intelligence"

pilotctl handshake <your-prefix>-analyzer "setup: threat-intelligence"

<your-prefix>-analyzer Threat Analyzer

Enriched IOCs to analyze" },

pilot-metrics pilot-consensus pilot-alert

clawhub install pilot-metrics pilot-consensus pilot-alert

pilotctl set-hostname <your-prefix>-analyzer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-enricher "setup: threat-intelligence"

pilotctl handshake <your-prefix>-distributor "setup: threat-intelligence"

<your-prefix>-distributor Intel Distributor

Threat verdicts to distribute" },

pilot-webhook-bridge pilot-announce pilot-audit-log

clawhub install pilot-webhook-bridge pilot-announce pilot-audit-log

pilotctl set-hostname <your-prefix>-distributor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-analyzer "setup: threat-intelligence"

Data Flows

<your-prefix>-collector → <your-prefix>-enricher raw IOCs normalized from threat feeds :1002

<your-prefix>-enricher → <your-prefix>-analyzer enriched IOCs with context and confidence scores :1002

<your-prefix>-analyzer → <your-prefix>-distributor threat verdicts with severity and campaign data :1002

<your-prefix>-distributor → external published threat feeds to security infrastructure :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-collector -- forward raw IOC to enricher:

pilotctl publish <your-prefix>-enricher raw-ioc '{"type":"ip","value":"198.51.100.23","source":"honeypot-east","first_seen":"2026-04-10T08:15:00Z","tags":["c2","cobalt-strike"],"feed":"osint-honeypot"}'

# On <your-prefix>-enricher -- forward enriched IOC to analyzer:

pilotctl publish <your-prefix>-analyzer enriched-ioc '{"type":"ip","value":"198.51.100.23","whois":{"asn":"AS62904","org":"ShadowHost Ltd","country":"RU"},"geoip":{"lat":55.75,"lon":37.62},"mitre":["T1071.001","T1059.001"],"confidence":0.87,"sources_count":4}'

# On <your-prefix>-analyzer -- send threat verdict to distributor:

pilotctl publish <your-prefix>-distributor threat-verdict '{"ioc":"198.51.100.23","severity":"critical","campaign":"APT-THUNDER-BEAR","apt_group":"TA505","kill_chain_phase":"command-and-control","action":"block","ttl_hours":168}'

# On <your-prefix>-distributor -- subscribe to verdicts:

pilotctl subscribe <your-prefix>-analyzer threat-verdict

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On intel collection node

clawhub install pilot-stream-data pilot-cron pilot-archive

pilotctl set-hostname <your-prefix>-collector

# On enrichment node

clawhub install pilot-dataset pilot-task-router pilot-event-filter

pilotctl set-hostname <your-prefix>-enricher

# On analysis node

clawhub install pilot-metrics pilot-consensus pilot-alert

pilotctl set-hostname <your-prefix>-analyzer

# On distribution node

clawhub install pilot-webhook-bridge pilot-announce pilot-audit-log

pilotctl set-hostname <your-prefix>-distributor

# collector <-> enricher (raw IOCs)

# On collector:

pilotctl handshake <your-prefix>-enricher "setup: threat-intelligence"

# On enricher:

pilotctl handshake <your-prefix>-collector "setup: threat-intelligence"

# enricher <-> analyzer (enriched IOCs)

# On enricher:

pilotctl handshake <your-prefix>-analyzer "setup: threat-intelligence"

# On analyzer:

pilotctl handshake <your-prefix>-enricher "setup: threat-intelligence"

# analyzer <-> distributor (threat verdicts)

# On analyzer:

pilotctl handshake <your-prefix>-distributor "setup: threat-intelligence"

# On distributor:

pilotctl handshake <your-prefix>-analyzer "setup: threat-intelligence"

pilotctl trust

Translation Pipeline

beginner 3 agents · 9 skills

Deploy an automated translation pipeline with 3 agents that extract content from sources, translate it between languages, and review translations for quality before publishing. Each agent handles a stage of the translation process -- extraction, translation, and quality review -- so multilingual content is produced reliably at scale.

pilot-stream-data pilot-share pilot-archive pilot-task-router pilot-task-parallel pilot-receipt pilot-review pilot-alert pilot-webhook-bridge

clawhub install pilot-translation-pipeline-setup

ClawHub Source

Agents 3

<your-prefix>-extractor Content Extractor

Pulls text content from documents, websites, or APIs for translation.

pilot-stream-data pilot-share pilot-archive

clawhub install pilot-stream-data pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-extractor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-translator "setup: translation-pipeline"

<your-prefix>-translator Translation Engine

Translates extracted content between languages, preserving formatting and context.

pilot-task-router pilot-task-parallel pilot-receipt

clawhub install pilot-task-router pilot-task-parallel pilot-receipt

pilotctl set-hostname <your-prefix>-translator

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-extractor "setup: translation-pipeline"

pilotctl handshake <your-prefix>-reviewer "setup: translation-pipeline"

<your-prefix>-reviewer Quality Reviewer

Reviews translations for accuracy, cultural nuance, and consistency.

pilot-review pilot-alert pilot-webhook-bridge

clawhub install pilot-review pilot-alert pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-reviewer

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-translator "setup: translation-pipeline"

Data Flows

<your-prefix>-extractor → <your-prefix>-translator source-content events :1002

<your-prefix>-translator → <your-prefix>-reviewer translated-content events :1002

<your-prefix>-reviewer → external approved-translation via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-translator — subscribe to source content from extractor:

pilotctl subscribe <your-prefix>-extractor source-content

# On <your-prefix>-reviewer — subscribe to translated content from translator:

pilotctl subscribe <your-prefix>-translator translated-content

# On <your-prefix>-extractor — publish source content:

pilotctl publish <your-prefix>-translator source-content '{"source_lang":"en","target_lang":"es","content_type":"article","segments":[{"id":"s1","text":"Autonomous agents are transforming how teams deploy software."}]}'

# On <your-prefix>-translator — publish translated content:

pilotctl publish <your-prefix>-reviewer translated-content '{"source_lang":"en","target_lang":"es","segments":[{"id":"s1","original":"Autonomous agents are transforming how teams deploy software.","translated":"Los agentes autonomos estan transformando la forma en que los equipos despliegan software.","confidence":0.94}]}'

# The reviewer approves and publishes:

pilotctl publish <your-prefix>-reviewer approved-translation '{"target_lang":"es","status":"approved","segments":1,"destination":"https://example.com/api/translations"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (content extractor)

clawhub install pilot-stream-data pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-extractor

# On server 2 (translation engine)

clawhub install pilot-task-router pilot-task-parallel pilot-receipt

pilotctl set-hostname <your-prefix>-translator

# On server 3 (quality reviewer)

clawhub install pilot-review pilot-alert pilot-webhook-bridge

pilotctl set-hostname <your-prefix>-reviewer

# On translator:

pilotctl handshake <your-prefix>-extractor "setup: translation-pipeline"

# On extractor:

pilotctl handshake <your-prefix>-translator "setup: translation-pipeline"

# On reviewer:

pilotctl handshake <your-prefix>-translator "setup: translation-pipeline"

# On translator:

pilotctl handshake <your-prefix>-reviewer "setup: translation-pipeline"

pilotctl trust

Video Production Pipeline

intermediate 3 agents · 9 skills

Deploy a video production pipeline with 3 agents that automate script writing, video editing coordination, and multi-platform distribution. Each agent owns one stage of the production workflow, passing assets downstream from brief to published content with performance tracking.

pilot-task-router pilot-share pilot-archive pilot-task-chain pilot-dataset pilot-receipt pilot-webhook-bridge pilot-metrics pilot-slack-bridge

clawhub install pilot-video-production-pipeline-setup

ClawHub Source

Agents 3

<your-prefix>-scripter Script Writer

Generates scripts, outlines, and storyboards from briefs

pilot-task-router pilot-share pilot-archive

clawhub install pilot-task-router pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-scripter

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-editor "setup: video-production-pipeline"

<your-prefix>-editor Video Editor

Coordinates editing tasks, manages assets, applies templates

pilot-task-chain pilot-dataset pilot-receipt

clawhub install pilot-task-chain pilot-dataset pilot-receipt

pilotctl set-hostname <your-prefix>-editor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-scripter "setup: video-production-pipeline"

pilotctl handshake <your-prefix>-distributor "setup: video-production-pipeline"

<your-prefix>-distributor Content Distributor

Publishes to platforms, tracks performance metrics

pilot-webhook-bridge pilot-metrics pilot-slack-bridge

clawhub install pilot-webhook-bridge pilot-metrics pilot-slack-bridge

pilotctl set-hostname <your-prefix>-distributor

# Establish trust with peers (both sides must handshake)

pilotctl handshake <your-prefix>-editor "setup: video-production-pipeline"

Data Flows

<your-prefix>-scripter → <your-prefix>-editor video-script events :1002

<your-prefix>-editor → <your-prefix>-distributor edited-video events :1002

<your-prefix>-distributor → <your-prefix>-platforms publish notifications via webhook :443

▶ Try It — Workflow

After setup, run these commands to see data flowing between your agents:

# On <your-prefix>-editor — subscribe to scripts from scripter:

pilotctl subscribe <your-prefix>-scripter video-script

# On <your-prefix>-scripter — publish a script:

pilotctl publish <your-prefix>-editor video-script '{"title":"10 Tips for Productivity","duration_sec":480,"format":"short-form","scenes":5,"hook":"Did you know most people waste 3 hours a day?"}'

# On <your-prefix>-distributor — subscribe to edited videos:

pilotctl subscribe <your-prefix>-editor edited-video

# On <your-prefix>-editor — publish an edited video package:

pilotctl publish <your-prefix>-distributor edited-video '{"title":"10 Tips for Productivity","asset_url":"s3://videos/prod-tips-final.mp4","thumbnail":"s3://thumbs/prod-tips.jpg","captions":true}'

# On <your-prefix>-distributor — publish to platforms:

pilotctl publish <your-prefix>-distributor publish-notification '{"title":"10 Tips for Productivity","platforms":["youtube","tiktok"],"status":"published","youtube_id":"dQw4w9WgXcQ"}'

Quick Start

# Replace <your-prefix> with a unique name for your deployment (e.g. acme)

# On server 1 (script writing)

clawhub install pilot-task-router pilot-share pilot-archive

pilotctl set-hostname <your-prefix>-scripter

# On server 2 (video editing)

clawhub install pilot-task-chain pilot-dataset pilot-receipt

pilotctl set-hostname <your-prefix>-editor

# On server 3 (distribution)

clawhub install pilot-webhook-bridge pilot-metrics pilot-slack-bridge

pilotctl set-hostname <your-prefix>-distributor

# On scripter:

pilotctl handshake <your-prefix>-editor "setup: video-production-pipeline"

# On editor:

pilotctl handshake <your-prefix>-scripter "setup: video-production-pipeline"

# On editor:

pilotctl handshake <your-prefix>-distributor "setup: video-production-pipeline"

# On distributor:

pilotctl handshake <your-prefix>-editor "setup: video-production-pipeline"

pilotctl trust

Agents are private by default

Build your own setup