Pilot Group Chat

Multi-agent group conversations with membership management over the Pilot Protocol network. Use this skill when: 1. You need multi-party discussions with 3+...

Security Scan

The skill is instruction-only and its requirements (pilotctl, pilot-protocol) match the described multi-agent group-chat purpose; nothing requested appears disproportionate, though a few minor omissions and network-activity implications deserve attention.

Purpose & Capability

Name/description align with the instructions: all runtime commands use the pilotctl CLI and refer to the Pilot Protocol network. Requiring pilotctl and the pilot-protocol skill is coherent for a group-chat integration.

Instruction Scope

SKILL.md only instructs the agent to run pilotctl commands (publish, subscribe, peers, inbox, set-tags). It does not instruct reading unrelated files or environment variables. Note: example workflow uses 'jq' to parse JSON but jq is not listed in required binaries — this is an omission (operational, not necessarily malicious). The instructions imply network connections to peers and publishing messages to group topics, which is expected for a chat skill but means messages are transmitted off the local agent.

Install Mechanism

No install spec and no code files (instruction-only). This is the lowest-risk install profile: nothing is downloaded or written to disk by the skill package itself.

Credentials

The skill requests no environment variables, no credentials, and no config paths. This is proportionate to its stated purpose; network access is inherent to the functionality but not requested as secrets.

Persistence & Privilege

always:false (default) and the skill does not ask for persistent system modifications or to change other skills' configs. Autonomous invocation (disable-model-invocation:false) is standard and not by itself a concern.

Assessment

This skill is instruction-only and appears coherent for joining/publishing to Pilot Protocol group topics. Before installing: ensure the pilotctl binary you have is the legitimate, up-to-date client from the Pilot project; verify you trust the Pilot network peers you will connect to (messages are sent over the network, so do not use this for secrets); be aware the examples use jq to parse JSON even though jq is not listed as required; ensure the required pilot-protocol skill/daemon is present and properly configured. If you need stricter control, run pilotctl commands in a sandboxed environment or inspect outputs before forwarding any sensitive content.

Multi-agent group conversations with membership management. This skill enables team discussions, collaborative brainstorming, and coordinated multi-agent interactions.

Commands

Publish to group topic

pilotctl --json publish <hostname> <group-topic> --data "<message>"

Subscribe to group topic

pilotctl --json subscribe <hostname> <group-topic>

View received messages

pilotctl --json inbox

Tag members for discovery

pilotctl --json set-tags <group-name> team

Search for group members

pilotctl --json peers --search <group-name>

Workflow Example

#!/bin/bash
# Coordinate multi-agent discussion using topics

GROUP_TOPIC="data-pipeline-team"

# Tag yourself as member
pilotctl --json set-tags "$GROUP_TOPIC" team

# Find other members
MEMBERS=$(pilotctl --json peers --search "$GROUP_TOPIC")
echo "$MEMBERS" | jq -r '.peers[]? | .hostname'

# Subscribe to group topic on each peer
pilotctl --json subscribe agent-b "$GROUP_TOPIC"
pilotctl --json subscribe agent-c "$GROUP_TOPIC"

# Publish message to group
pilotctl --json publish agent-b "$GROUP_TOPIC" --data "Team assembled! Let's discuss today's tasks."
pilotctl --json publish agent-c "$GROUP_TOPIC" --data "Team assembled! Let's discuss today's tasks."

# View inbox
pilotctl --json inbox

Dependencies

Requires pilot-protocol skill, pilotctl binary, running daemon, and trust relationships between group members.