Pilot Chat Collaboration Hub Setup

v1.0.0

Deploy a chat and collaboration hub with 4 agents. Use this skill when: 1. User wants to set up a multi-agent chat platform 2. User is configuring a chat ser...

0· 86·0 current·0 all-time
byCalin Teodor@teoslayer

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for teoslayer/pilot-chat-collaboration-hub-setup.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Pilot Chat Collaboration Hub Setup" (teoslayer/pilot-chat-collaboration-hub-setup) from ClawHub.
Skill page: https://clawhub.ai/teoslayer/pilot-chat-collaboration-hub-setup
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: pilotctl, clawhub
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install pilot-chat-collaboration-hub-setup

ClawHub CLI

Package manager switcher

npx clawhub@latest install pilot-chat-collaboration-hub-setup
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (deploy a 4-agent chat hub) matches the instructions: installing pilot-* skills via clawhub, setting hostnames with pilotctl, writing a manifest, and performing handshakes. Required binaries (pilotctl, clawhub) are relevant and expected.
Instruction Scope
SKILL.md stays within the stated purpose but includes operations that affect system state: installing skills on nodes (clawhub), setting hostnames (pilotctl), and writing a manifest file to ~/.pilot/setups/chat-collaboration-hub.json. It also instructs creating mutual trust/handshakes between agents, which is necessary for the hub but increases the trust footprint.
Install Mechanism
This is instruction-only (no install spec). It relies on external tools (clawhub to install many pilot-* packages). The manifest does not provide package provenance, checksums, or verification guidance for what clawhub will fetch. That is expected functionally but increases risk because arbitrary code may be installed by clawhub/pilotctl.
Credentials
No environment variables or credentials are requested by the skill and none are accessed in the instructions. The skill's configuration changes are limited to user-home manifest files and handshake/trust operations between agents.
Persistence & Privilege
always:false and default autonomous invocation are set. The skill writes a manifest into ~/.pilot (its own configuration area) and performs host configuration via pilotctl; it does not request persistent elevated platform privileges or modify other skills' configs.
Assessment
This skill is coherent for deploying a multi-agent chat hub, but before using it: 1) Verify the provenance and trustworthiness of the pilotctl and clawhub binaries and the pilot-* packages they will install (inspect repositories, checksums, or vendor docs). 2) Back up any existing ~/.pilot configuration before the skill writes the manifest. 3) Run installations in a controlled environment or isolated network if possible, because clawhub will fetch and install code on each node. 4) Understand that the handshake/auto-trust steps create mutual trust between agents—only establish them between nodes you control and have audited. 5) If you need a higher assurance, request the skill author to include explicit verification steps (signed releases, checksums, or source URLs) for the installed pilot-* packages.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

Binspilotctl, clawhub
latestvk974dtygtyb1nwm8cy93gqm0nx85ak9j
86downloads
0stars
1versions
Updated 5d ago
v1.0.0
MIT-0

Chat & Collaboration Hub Setup

Deploy 4 agents: chat server, moderator, translator, and archive bot.

Roles

RoleHostnameSkillsPurpose
chat-server<prefix>-chatpilot-group-chat, pilot-thread, pilot-presence, pilot-broadcastHosts rooms and threads
moderator<prefix>-moderatorpilot-event-filter, pilot-blocklist, pilot-audit-log, pilot-alertContent filtering
translator<prefix>-translatorpilot-translate, pilot-stream-data, pilot-task-routerReal-time translation
archive-bot<prefix>-archive-botpilot-archive, pilot-event-log, pilot-backup, pilot-cronArchival and compliance

Setup Procedure

Step 1: Ask the user which role and prefix.

Step 2: Install skills:

# chat-server:
clawhub install pilot-group-chat pilot-thread pilot-presence pilot-broadcast
# moderator:
clawhub install pilot-event-filter pilot-blocklist pilot-audit-log pilot-alert
# translator:
clawhub install pilot-translate pilot-stream-data pilot-task-router
# archive-bot:
clawhub install pilot-archive pilot-event-log pilot-backup pilot-cron

Step 3: Set hostname and write manifest to ~/.pilot/setups/chat-collaboration-hub.json.

Step 4: All agents handshake the chat server.

Manifest Templates Per Role

chat-server

{
  "setup": "chat-collaboration-hub", "role": "chat-server", "role_name": "Chat Server",
  "hostname": "<prefix>-chat",
  "skills": {
    "pilot-group-chat": "Host group chat rooms with membership management.",
    "pilot-thread": "Support threaded conversations within rooms.",
    "pilot-presence": "Track online/away/offline status of participants.",
    "pilot-broadcast": "Broadcast messages to all room participants."
  },
  "data_flows": [
    { "direction": "send", "peer": "<prefix>-moderator", "port": 1002, "topic": "chat-message", "description": "Messages for filtering" },
    { "direction": "send", "peer": "<prefix>-translator", "port": 1002, "topic": "chat-message", "description": "Messages for translation" },
    { "direction": "send", "peer": "<prefix>-archive-bot", "port": 1002, "topic": "chat-message", "description": "Messages for archival" },
    { "direction": "receive", "peer": "<prefix>-moderator", "port": 1002, "topic": "moderation-result", "description": "Filter decisions" },
    { "direction": "receive", "peer": "<prefix>-translator", "port": 1002, "topic": "translated-message", "description": "Translations" }
  ],
  "handshakes_needed": ["<prefix>-moderator", "<prefix>-translator", "<prefix>-archive-bot"]
}

moderator

{
  "setup": "chat-collaboration-hub", "role": "moderator", "role_name": "Content Moderator",
  "hostname": "<prefix>-moderator",
  "skills": {
    "pilot-event-filter": "Filter messages for policy violations and spam.",
    "pilot-blocklist": "Maintain blocklist of abusive agents.",
    "pilot-audit-log": "Log moderation decisions.",
    "pilot-alert": "Alert admins on serious violations."
  },
  "data_flows": [
    { "direction": "receive", "peer": "<prefix>-chat", "port": 1002, "topic": "chat-message", "description": "Messages to filter" },
    { "direction": "send", "peer": "<prefix>-chat", "port": 1002, "topic": "moderation-result", "description": "Filter decisions" }
  ],
  "handshakes_needed": ["<prefix>-chat"]
}

translator

{
  "setup": "chat-collaboration-hub", "role": "translator", "role_name": "Auto-Translator",
  "hostname": "<prefix>-translator",
  "skills": {
    "pilot-translate": "Translate messages between languages in real time.",
    "pilot-stream-data": "Stream translated content back to chat server.",
    "pilot-task-router": "Route translation tasks by language pair."
  },
  "data_flows": [
    { "direction": "receive", "peer": "<prefix>-chat", "port": 1002, "topic": "chat-message", "description": "Messages to translate" },
    { "direction": "send", "peer": "<prefix>-chat", "port": 1002, "topic": "translated-message", "description": "Translations" }
  ],
  "handshakes_needed": ["<prefix>-chat"]
}

archive-bot

{
  "setup": "chat-collaboration-hub", "role": "archive-bot", "role_name": "Archive Bot",
  "hostname": "<prefix>-archive-bot",
  "skills": {
    "pilot-archive": "Archive all conversations for search and compliance.",
    "pilot-event-log": "Maintain searchable event log of all messages.",
    "pilot-backup": "Periodic backup of chat archives.",
    "pilot-cron": "Schedule archive backup jobs."
  },
  "data_flows": [
    { "direction": "receive", "peer": "<prefix>-chat", "port": 1002, "topic": "chat-message", "description": "Messages to archive" },
    { "direction": "send", "peer": "<prefix>-chat", "port": 1002, "topic": "archive-confirm", "description": "Archival confirmation" }
  ],
  "handshakes_needed": ["<prefix>-chat"]
}

Data Flows

  • chat-server → moderator/translator/archive-bot : messages (port 1002)
  • moderator → chat-server : filter decisions (port 1002)
  • translator → chat-server : translated messages (port 1002)

Workflow Example

# On chat-server — broadcast message to services:
pilotctl --json publish <prefix>-moderator chat-message '{"room":"general","sender":"alice","text":"Hello!"}'
pilotctl --json publish <prefix>-translator chat-message '{"room":"general","text":"Hello!","lang":"en"}'
# On moderator:
pilotctl --json publish <prefix>-chat moderation-result '{"msg_id":"M-5012","action":"approve"}'
# On translator:
pilotctl --json publish <prefix>-chat translated-message '{"msg_id":"M-5012","target_lang":"ja","text":"こんにちは!"}'

Dependencies

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

Comments

Loading comments...