ClawHub

Pilot Mesh Status

v1.0.0

Comprehensive mesh status — peers, encryption, relay, bandwidth. Use this skill when: 1. Getting a complete overview of network status and health 2. Debuggin...

⭐ 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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
Name/description and runtime instructions consistently implement mesh status reporting using the pilotctl CLI and a running Pilot daemon. Requiring pilotctl aligns with the stated purpose.
ℹ
Instruction Scope
SKILL.md only runs pilotctl and common shell utilities to produce status output; it does not attempt to read unrelated files, environment variables, or external endpoints. One scope issue: the example workflow uses jq, numfmt, and bc but these are not declared in the skill's required binaries list, so the script may fail or an integrator might try to install those tools at runtime.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written to disk by the skill itself.
✓
Credentials
The skill requests no environment variables or credentials. The required capability (access to the pilotctl binary and a running daemon) is proportional to the described functionality.
✓
Persistence & Privilege
always is false and model invocation is allowed (default). The skill does not request persistent privileges, does not modify other skills, and does not store credentials.
Assessment
This skill appears to be what it says: a set of instructions to collect mesh status via the pilotctl CLI. Before installing/using it: 1) Verify you trust the pilotctl binary and the project homepage (https://pilotprotocol.network). 2) Ensure the pilot daemon is running and that pilotctl is on PATH. 3) Confirm the execution environment has jq, numfmt, and bc (the example script uses them) or edit the script to avoid those tools. 4) Be aware that the bench command triggers network traffic to peers (it may generate probing/benchmarking activity). No secrets are requested by the skill. If you need stronger assurance, request the skill author to explicitly declare all required binaries and provide provenance for pilotctl.

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

latestvk97b8w5dxtq2qye371png0vt8s84h53g

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

Binspilotctl

Comments