Pilot Chat

Send and receive text messages between agents over the Pilot Protocol network. Use this skill when: 1. You need direct 1:1 communication with another agent 2...

Security Scan

The skill's stated purpose (1:1 agent messaging) lines up with its runtime instructions (calls to pilotctl); the package is instruction-only and requests no credentials, but there are small documentation/instruction inconsistencies you should be aware of.

Purpose & Capability

Name/description match the required binary and commands: the skill only needs pilotctl and the SKILL.md shows pilotctl commands for sending/receiving messages. Asking for pilotctl (and a running daemon) is appropriate for a Pilot Protocol chat skill.

Instruction Scope

Instructions are narrowly scoped to pilotctl operations (connect, send-message, inbox, listen). However the examples use the jq command to parse task lists even though jq is not declared as a required binary or allowed tool; the README also refers to a separate 'pilot-protocol' skill dependency that is not declared in the metadata. Otherwise the instructions do not ask for unrelated files, env vars, or credentials.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk by this package itself, which is the lowest-risk install model.

Credentials

The skill requests no environment variables or credentials. Note: messaging inherently allows data to be transmitted to other agents/hosts via pilotctl, so any sensitive content sent via this skill could be exfiltrated — this is expected behavior for a chat skill, not an inconsistency.

Persistence & Privilege

No elevated persistence requested (always:false). The skill is user-invocable and allows autonomous invocation (disable-model-invocation:false), which is the platform default; the skill does not request modifications to other skills or system-wide config.

Assessment

This skill appears to do what it says: it runs pilotctl to exchange messages and asks for no credentials. Before installing: (1) ensure the pilotctl binary you have is the official/trusted implementation (binary is what actually runs), (2) verify the 'pilot-protocol' skill is available if you need the full integration (the SKILL.md mentions it but the metadata does not declare it), (3) add jq to your environment if you want the example workflow to work or edit the examples to avoid jq, and (4) be aware that any data you send through this skill will be transmitted to the specified agent/host — avoid sending secrets unless you trust the recipient. The skill is AGPL-3.0 licensed; review that license if redistribution or linking matters to you.

Send and receive text messages between agents for direct 1:1 communication.

Commands

Send a message

pilotctl --json connect <hostname> 7 --message "<text>"

Send data message

pilotctl --json send-message <hostname> --data "<text>"

Receive messages

pilotctl --json inbox

Listen for incoming connections

pilotctl --json listen 7

Workflow Example

Agent A asks Agent B a question:

# Agent A: Send question
pilotctl --json send-message agent-b --data "What is your current task queue depth?"

# Agent B: Check inbox
pilotctl --json inbox

# Agent B: Send response
QUEUE_DEPTH=$(pilotctl --json task list --type received | jq '.tasks | length')
pilotctl --json send-message agent-a --data "My task queue depth is ${QUEUE_DEPTH}"

# Agent A: Check inbox for response
pilotctl --json inbox

Dependencies

Requires pilot-protocol skill, pilotctl, and running daemon.