Pilot Directory
v1.0.0Local directory of known agents with cached metadata. Use this skill when: 1. Maintaining a persistent directory of frequently contacted agents 2. Caching ag...
⭐ 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 and description match the runtime instructions: the SKILL.md uses pilotctl to list, find, and lookup peers and to cache metadata. Requiring pilotctl and a running pilot daemon is appropriate for a local directory of agents.
Instruction Scope
Instructions are narrowly scoped to running pilotctl commands, processing their JSON output, and writing local files (ai_directory.jsonl, ai_directory.json, ai_lookup.txt). They do not request unrelated files or credentials. However, the instructions rely heavily on jq but jq is not declared in the skill's declared binaries — this is an inconsistency that could cause failures or indicate sloppy packaging.
Install Mechanism
No install spec and no code files (instruction-only) — lowest install risk. The skill expects an existing pilotctl binary and a running daemon; those are external requirements, not an install performed by the skill.
Credentials
The skill requests no environment variables, no credentials, and no config paths. That is proportionate for a local directory/cache skill.
Persistence & Privilege
always is false and the skill is user-invocable; it does persist data to local files per its declared purpose, which is expected and proportionate. It does not request elevated or cross-skill privileges.
Assessment
This skill appears to do what it says: run pilotctl commands, collect JSON metadata, and save it locally. Before installing, confirm you have a trustworthy pilotctl binary and that the pilot daemon is the official implementation you expect. Note the SKILL.md uses jq but the skill metadata did not declare jq as a required binary — install jq or update the skill if needed. Be aware the exported files will contain agent hostnames/node IDs and possibly other metadata; store them securely and avoid publishing them. If you allow autonomous invocation of skills in your agent, remember this skill can enumerate local peers and write files — only enable it if you trust the pilotctl daemon and the Pilot Protocol environment.Like a lobster shell, security has layers — review code before you run it.
latestvk97e5jexwkezafev3tw0se83ex84hty1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binspilotctl