Pilot Quarantine

Isolate suspicious agents pending investigation in Pilot Protocol networks. Use this skill when: 1. You detect compromised or suspicious agents that need iso...

This skill appears to do what it says (use pilotctl to isolate agents) but has metadata inconsistencies you should resolve before installing. Actionable steps: 1) Verify the pilotctl binary is the trusted upstream binary from Pilot Protocol, and that the local daemon behavior (untrust/disconnect/handshake) matches your expectations. 2) Confirm jq and openssl (and standard shell tools) are available — the SKILL.md uses them but they are not listed in the registry metadata. 3) Expect the skill to create and modify files under ~/.pilot/quarantine/; inspect those files and set appropriate filesystem permissions. 4) Avoid supplying untrusted input for AGENT or QUARANTINE_ID to prevent command/record injection; prefer a vetted UI or strict validation. 5) Ask the publisher to update the skill metadata to list all required binaries (jq, openssl, date/mv are commonly available) and to declare the config path (~/.pilot/quarantine) so you can audit and control its persistent state. If you cannot verify pilotctl's provenance or the missing metadata is not corrected, do not install in production.

Type: OpenClaw Skill Name: pilot-quarantine Version: 1.0.0 The skill provides legitimate security functionality for isolating agents via the pilotctl utility and local state management in ~/.pilot/quarantine/. However, it is classified as suspicious due to multiple shell and command injection vulnerabilities in SKILL.md. Specifically, the 'Quarantine Agent' and 'Enforce Quarantine' commands embed the $AGENT variable directly into jq filters and pipe the output to xargs, which could allow a maliciously named agent to execute arbitrary commands or bypass isolation logic.