Pilot Archive
v1.0.0Index and search historical data exchanges, messages, and file transfers over Pilot Protocol. Use this skill when: 1. You need to search through past message...
⭐ 0· 18·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 align with the runtime instructions: the SKILL.md uses pilotctl to fetch inbox/received data and builds local JSONL indexes. One minor incoherence: the manifest declares pilotctl as a required binary but the instructions also require jq (and mention tar/gzip) — jq and export tools are listed in SKILL.md dependencies but not declared in the registry metadata.
Instruction Scope
Instructions only call pilotctl and local shell tools to read message/file histories and write indexes under $HOME/.pilot/archive. They do not call external endpoints or request unrelated system credentials. Note: the skill will collect and store potentially sensitive message/file contents locally — this is expected behavior for an archiver but is privacy-relevant.
Install Mechanism
Instruction-only skill with no install spec or archive downloads; lowest-risk installation model. It assumes existing binaries on PATH rather than fetching code.
Credentials
No environment variables or credentials are requested. The skill reads/writes only within the user's $HOME/.pilot directory as part of its stated purpose.
Persistence & Privilege
always:false and no special privileges requested. The skill writes local archive files but does not alter other skills or system-wide agent settings.
Assessment
This skill appears to do what it says: locally index and search Pilot Protocol history. Before installing: (1) ensure pilotctl and jq are installed and the pilot daemon is trusted/running locally; the SKILL.md expects jq and mentions tar/gzip but the registry metadata doesn't list jq — consider adding it to required binaries. (2) Be aware it will copy message and file metadata/content into $HOME/.pilot/archive (sensitive data stored locally). (3) Review/limit file permissions on the archive directory and vet pilotctl (it can access your messages). (4) Test commands manually to confirm no unexpected network activity. If you need stronger privacy controls, avoid indexing or add filters to exclude sensitive messages.Like a lobster shell, security has layers — review code before you run it.
latestvk9771n5px82e7wjwzrz60tn2d184fa40
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binspilotctl