Pilot Relay
v1.0.0Store-and-forward messaging for offline peers over the Pilot Protocol network. Use this skill when: 1. You need to send messages to agents that may be offlin...
⭐ 0· 95·0 current·0 all-time
byCalin Teodor@teoslayer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (store-and-forward messaging over Pilot Protocol) matches the runtime instructions: all commands are pilotctl invocations and the SKILL.md explicitly declares the pilotctl binary and pilot-protocol dependency. There are no unrelated credentials, binaries, or install steps requested.
Instruction Scope
Instructions are narrowly scoped to running pilotctl (send-message, inbox, daemon start/status, etc.). They do not request arbitrary file reads or environment variables. Notes: example snippets pipe output into jq but jq is not declared as a required binary; examples assume the daemon will manage network activity and keys (the skill references 'trust relationship' and encrypted messages), so users should confirm key/trust establishment outside the skill.
Install Mechanism
There is no install spec (instruction-only), so nothing is written to disk by the skill itself. This is the lowest-risk install model.
Credentials
The skill declares no environment variables, credentials, or config paths. The functionality relies on a local binary/daemon and pre-existing trust relationships; no disproportionate credentials are requested by the skill.
Persistence & Privilege
The skill is not always-on and does not request elevated platform privileges or modifications to other skills. Model invocation is enabled (default), which is normal for skills; this does not by itself increase concern.
Assessment
This skill is coherent but still requires caution before use. Verify that the pilotctl binary on your system is the legitimate, up-to-date release from the Pilot Protocol project (do not run an untrusted binary). Confirm the pilot-protocol skill and any relay/registry endpoints are from sources you trust, and that end-to-end encryption keys are under your control (the SKILL.md claims relay nodes cannot read message content, but that depends on correct key management). Examples use jq but jq is not listed as required—install a trusted jq if you want to run the shell snippets. Be aware that starting the pilotctl daemon exposes a network-facing agent process and will read local pilot/protocol config files; review those config files and relay node lists before use. Finally, note the AGPL-3.0 license (may affect redistribution) and the skill source is listed as unknown—if provenance matters, obtain pilotctl and pilot-protocol from official project pages and validate checksums/signatures before integrating.Like a lobster shell, security has layers — review code before you run it.
latestvk973zdb76nnjww5sbvk02gfnz584ghqb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binspilotctl