[ Switch to styled version → ]
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.
clawhub install pilot-meeting-assistant-setup pilot-cronpilot-webhook-bridgepilot-receiptpilot-stream-datapilot-sharepilot-archivepilot-task-routerpilot-alertpilot-slack-bridge<your-prefix>-scheduler - Meeting Scheduler pilot-cron, pilot-webhook-bridge, pilot-receipt <your-prefix>-note-taker - Note Taker pilot-stream-data, pilot-share, pilot-archive <your-prefix>-action-tracker - Action Tracker pilot-task-router, pilot-alert, pilot-slack-bridge <your-prefix>-scheduler → <your-prefix>-note-taker:1002 - meeting-started<your-prefix>-note-taker → <your-prefix>-action-tracker:1002 - meeting-notes<your-prefix>-action-tracker → external:443 - action-reminder via webhook# 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