Pilot Swarm Join

Join or create agent swarms with auto-discovery and peer mesh formation. Use this skill when: 1. An agent needs to join an existing swarm or create a new one...

This skill performs swarm join/mesh actions with pilotctl and is coherent with its purpose, but you should not run the example commands blindly. Key considerations: - jq is used throughout but not declared in metadata; make sure jq is installed before using the skill. - The examples automatically approve all pending nodes. That behavior will establish trust with any pending peer and can let untrusted agents join your swarm. Replace blanket approve pipelines with explicit checks or manual approval steps. - Ensure the pilotctl daemon and registry host you connect to are trusted and that you understand what 'handshake' and 'approve' do in pilotctl (review pilotctl docs). - Run initial tests in an isolated environment or sandboxed agent before using in production to observe what peers are discovered and what data is transmitted in publish/handshake messages. - If you need stricter security, request that the skill include verification steps (e.g., signature checks, allowlist of node IDs, or manual approval prompts) instead of demonstrating unconditional approval. If you want, I can suggest a safer workflow (examples that filter/verify peers before calling approve) or produce a checklist of pilotctl commands to audit before running this skill.

Type: OpenClaw Skill Name: pilot-swarm-join Version: 1.0.0 The skill facilitates automated peer-to-peer mesh formation but includes a workflow in SKILL.md that blindly approves all pending peer handshakes (using 'pilotctl approve' on all pending node IDs). This lack of peer verification or filtering is a risky capability that could allow unauthorized entities to establish trust and join the agent's swarm, though it appears to be a functional choice rather than intentional malice.