Pilot Compress
v1.0.0Transparent compression for large messages over the Pilot Protocol network. Use this skill when: 1. You need to reduce bandwidth for large payloads 2. You wa...
⭐ 0· 8·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
medium confidencePurpose & Capability
Name/description match the instructions: the SKILL.md shows how to compress/decompress payloads and send/receive via pilotctl. The only minor inconsistency is that the doc expects common helper tools (gzip/gunzip, base64, jq, stat, rm, zstd/lz4/brotli) but the declared required binaries in registry metadata list only pilotctl.
Instruction Scope
Instructions are narrowly scoped to compressing files/strings, sending via pilotctl, receiving inbox JSON, base64-decoding and decompressing. They do read local files and perform filesystem operations (stat, gzip, rm) and parse pilotctl output with jq — all expected for the task. Be aware these steps will decompress arbitrary data from the network (risk of zip/DEFLATE bombs or malicious payloads) and will delete temporary files during cleanup.
Install Mechanism
No install spec — instruction-only. Nothing is downloaded or written by the skill itself, which minimizes install-time risk.
Credentials
The skill does not request environment variables or credentials. It does rely on pilotctl and various compression/CLI utilities (not all declared) but does not require unrelated secrets or system-level credentials.
Persistence & Privilege
always:false and no install hooks or config modifications are present. The skill does not request persistent presence or elevated agent-wide privileges.
Assessment
This skill is an instruction-only helper for compressing data before sending it via pilotctl; it appears to do what it says. Before installing/using: 1) Ensure pilotctl and the compression/CLI tools referenced (gzip/gunzip, base64, jq, zstd/lz4/brotli, stat, rm) are available on your system — the registry metadata only lists pilotctl. 2) Only decompress data you trust; untrusted compressed content can be used for zip/DEFLATE bombs or to trigger resource exhaustion. 3) Note the scripts perform filesystem writes and temporary file removal (rm); run them in a safe directory or sandbox if you are unsure. 4) Confirm you trust the Pilot Protocol network and the pilotctl daemon you will use, since data is transmitted/received over that service. If you need higher assurance, request an explicit dependency list from the author or test the instructions in an isolated environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk974vehthat3gkms4eea7xk8y984hm45
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binspilotctl
