Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Pilot Clipboard

v1.0.0

Shared clipboard for quick text and data snippets between agents over Pilot Protocol. Use this skill when: 1. You need to share short text snippets or comman...

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
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description align with functionality (sending/pasting short text via pilotctl). However SKILL.md invokes additional tools (jq, pbcopy/pbpaste, xclip/xsel) that are not declared in the skill's metadata 'requires' section. The metadata only lists pilotctl; jq is required by the examples and script. This is an inconsistency that affects install/usage but does not necessarily imply malicious intent.
Instruction Scope
The instructions explicitly read local input (stdin/command output) and send it to arbitrary Pilot destination IDs via pilotctl --data / send-message, and read the inbox to paste remote content. That behavior is coherent with a clipboard skill, but it also means any copied content (including passwords, tokens, or other sensitive data) will be transmitted to the network. The skill does not include any guidance or safeguards to prevent accidental transmission of secrets.
Install Mechanism
Instruction-only skill with no install spec or code files, so nothing will be written to disk by the skill itself. This is the lowest install risk. The runtime relies on external binaries (pilotctl, jq, clipboard utilities) to be present on PATH.
Credentials
The skill requests no environment variables or credentials, which is proportionate. However, it depends on pilotctl and implicitly the 'pilot-protocol' skill/daemon which may use stored credentials/configuration outside this skill; those are not declared or discussed. Verify what credentials the Pilot ecosystem requires before trusting network operations.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and is user-invocable only. It does not request elevated persistence or system-wide configuration changes.
What to consider before installing
This skill appears to do what it says (share short text over the Pilot network), but take these precautions before installing or using it: - Do not send secrets: Clipboard contents and command output sent with pilot-clipboard will be transmitted to remote Pilot peers. Avoid copying passwords, API keys, or anything sensitive. - Verify the pilotctl binary and Pilot network: pilotctl is the program actually performing network operations. Only use pilot-clipboard if pilotctl comes from a trusted source and you understand how Pilot identifies recipients. Check the pilot-protocol skill/daemon configuration for where credentials are stored and who can receive messages. - Install missing tools: The SKILL.md examples require jq and (optionally) pbcopy/pbpaste or xclip/xsel for system clipboard integration; these are not declared in metadata. Install these separately if you intend to use the examples. - Test in isolation: Try the workflow in a sandbox or test account before using it with real data. - Confirm provenance: The skill source is unknown and the registry entry points to a homepage; if you need higher assurance, ask the publisher for source code or a signed release and review the pilotctl/pilot-protocol codebase. Confidence is medium: the skill is coherent with its stated purpose, but the undeclared runtime dependencies and the inherent privacy/exfiltration risk of a networked clipboard justify caution.

Like a lobster shell, security has layers — review code before you run it.

latestvk9762bkmprym8njbv6bjz4pwhx84hxr3

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

Binspilotctl

Comments