Pilot Announce

v1.0.0

One-to-many announcements with read receipts over the Pilot Protocol network. Use this skill when: 1. You need to broadcast important updates with delivery t...

0· 19·1 current·1 all-time
byCalin Teodor@teoslayer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill's name/description match its runtime instructions: it requires the pilotctl CLI and the pilot-protocol daemon and performs broadcasts and read-receipt operations. Asking for pilotctl and the pilot-protocol dependency is proportionate to the described functionality.
Instruction Scope
SKILL.md only instructs running pilotctl commands (send-message, publish, subscribe, inbox, peers) and a bash loop that queries trusted peers. This stays within the announced purpose. Minor issues: example workflow uses jq to parse pilotctl JSON output and a bash shebang, but jq and bash are not declared in the skill's required binaries list — the agent will need jq present for the example to work. Also note: the workflow explicitly iterates over all 'trusted' peers and will broadcast to them; make sure you actually want announcements sent to that set.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is downloaded or written by the skill itself. Low install risk.
Credentials
No environment variables, credentials, or config paths are requested. The skill relies on local pilotctl state and trust relationships, which is appropriate for a CLI-based announcement tool.
Persistence & Privilege
The skill is not always-on and does not request elevated or persistent platform privileges. Autonomous invocation is allowed by default (normal for skills) but not excessive here; the skill does not modify other skills or system-wide configuration.
Assessment
This skill appears to do what it says: it runs the pilotctl CLI to broadcast announcements and track receipts. Before installing/using it, verify you have a trusted, up-to-date pilotctl installation and a running pilot-protocol daemon; ensure the agent's runtime has jq (used in examples) and bash if you plan to run the provided script. Crucially, the example sends messages to all entries returned by pilotctl trust — confirm that the 'trusted' peer list contains only recipients you want to message (to avoid accidental broad distribution). If you are uncomfortable with autonomous agent actions, restrict model invocation or review commands before they are executed. Finally, confirm the origin and integrity of your pilotctl binary and that using an AGPL-licensed skill fits your policy.

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

latestvk97b6erd8rkxv710adrcye57b584ejmy

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

Binspilotctl

Comments