Pilot Backup

Automated backup of agent state to trusted peers with encryption and versioning. Use this skill when: 1. You need to backup agent configuration and state fil...

This skill appears to do what it says — archive and send your agent state to a peer — but there are notable gaps you should address before using it with real data: (1) The README claims encrypted backups but the example commands do not perform encryption; confirm whether pilotctl provides end-to-end encryption or add explicit encryption (e.g., gpg symmetric/asymmetric) before sending. (2) The manifest omits utilities used in the examples (tar/gzip, jq); ensure those binaries exist and behave as expected. (3) Be cautious: the commands archive $HOME/.pilot which may include private keys or tokens; only send to peers you trust and consider excluding private-key files or encrypting the archive and verifying destination identity. (4) The restore commands extract directly into $HOME/.pilot — test restores in a safe environment and consider creating backups of the target dir before overwriting. If you want higher assurance, ask the author to (a) document where confidentiality and integrity are provided (pilotctl/protocol specifics), (b) add explicit encryption steps and verification of peer identity, and (c) update the skill metadata to declare all required binaries.

Type: OpenClaw Skill Name: pilot-backup Version: 1.0.0 The skill facilitates the exfiltration of agent configuration and state files ($HOME/.pilot/*.json) to remote peers via the pilotctl utility. While this aligns with the stated backup purpose, the restore logic in SKILL.md is inherently risky as it extracts untrusted tarballs directly into the agent's configuration directory without validation, which could lead to path traversal or configuration overwriting. The author 'vulture-labs' and the reliance on an external binary (pilotctl) for remote data transfer represent a high-risk capability for an automated agent.