Pilot Discover
v1.0.0Advanced agent discovery by tags, polo score, and status. Use this skill when: 1. Finding agents by specific capabilities (tags like "ai", "storage", "comput...
⭐ 0· 0·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
Name, description, and declared dependency on the pilotctl binary align with the provided commands (peers, lookup, info, ping). The skill's stated purpose (discovering agents by tags/polo score/status) matches the concrete pilotctl usage.
Instruction Scope
SKILL.md only instructs the agent to run pilotctl commands (search, lookup, info, peers, ping) which is in-scope for discovery. However, the example workflow uses jq to parse JSON but jq is not listed in the skill's required binaries; this is an operational mismatch that could cause failures. The instructions do not request unrelated files, environment variables, or external endpoints beyond the Pilot Protocol tooling.
Install Mechanism
There is no install spec (instruction-only), so nothing is downloaded or written to disk by the skill itself. This lowers its installation risk; the only runtime dependency is pilotctl which must already be present and trusted.
Credentials
The skill declares no required environment variables or credentials, which is proportional to a local discovery tool. One caveat: the SKILL.md notes the daemon must be running and have registry access — acquiring registry access might require credentials or config held by pilotctl/daemon, but those are not described here. Confirm how pilotctl authenticates and whether it will access remote registries or local config files before use.
Persistence & Privilege
The skill does not request always:true, does not persist or alter other skills, and is invocation-enabled (default). This is appropriate for a discovery/search skill; no excessive privileges are requested.
Assessment
This skill appears to be what it claims: a helper for running pilotctl discovery commands. Before installing, verify you have a trusted pilotctl binary and that the pilot daemon you will use is configured correctly. Note the example uses jq to filter JSON output but jq is not declared as a requirement—either install jq or adapt the workflow. Also confirm whether your pilotctl/daemon requires credentials to access the network registry and where those credentials are stored (local config files, env vars, or a credential manager). Because the skill will run pilotctl commands that contact peers (lookup/ping), consider the network privacy implications: do you want your environment to probe external nodes and potentially reveal your IP or other metadata? Finally, obtain pilotctl from the official source (pilotprotocol.network or upstream releases) and review its documentation before granting the daemon network/registry access.Like a lobster shell, security has layers — review code before you run it.
latestvk97cfqvvwt9xd31ggxe3y1f4xn84h95q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binspilotctl