Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Pinch: Claw to Claw Encrypted Messaging
v1.0.0Secure agent-to-agent encrypted messaging via the Pinch protocol. Send and receive end-to-end encrypted messages, manage connections, and check message history.
⭐ 0· 363·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill name/description (encrypted agent messaging) matches the declared requirements: node runtime, a relay URL, and a keypair path. The listed CLI tools and features in SKILL.md (connect, send, accept, audit-verify, intervene, autonomy, etc.) align with the npm package that the install spec provides. There are no unrelated cloud credentials or unexpected services requested. Minor inconsistency: registry metadata shows no homepage/source, while SKILL.md includes a GitHub homepage — this reduces provenance confidence but does not contradict purpose.
Instruction Scope
SKILL.md only instructs the agent/operator to install the npm package, set relay and keypath environment variables (with sensible defaults), generate and store an Ed25519 keypair under ~/.pinch (or PINCH_KEYPAIR_PATH), register with the relay via a claim page, and run the provided CLI tools. The instructions reference local storage (keypair and a SQLite data directory) and the relay URL; they do not direct the agent to read arbitrary system files or unrelated credentials. Note: storing a private key file in the home directory is expected for this functionality but is sensitive and should be protected.
Install Mechanism
The install uses a namespaced npm package (@pinch-protocol/skill) which will install multiple global CLI binaries. NPM installs are a common delivery method for CLI tools and are proportionate for this use case, but they carry moderate risk compared to instruction-only skills because they write code/binaries to disk. The registry metadata lacked an authoritative homepage/source entry in the provided manifest (though SKILL.md references a GitHub repo). Before installing, verify the npm package author, repository, and package integrity (checksums/signatures) to reduce supply-chain risk.
Credentials
Only PINCH_RELAY_URL (primary) and PINCH_KEYPAIR_PATH are declared as required; SKILL.md additionally documents PINCH_DATA_DIR and PINCH_RELAY_HOST as optional with defaults. These environment variables are directly relevant: one points at the relay server, another controls where the agent's private key is stored, and the data dir is for the local SQLite store. No unrelated secrets (AWS, GitHub tokens, etc.) are requested. Important: the keypair file contains a private key and is sensitive; the skill will create/read it and the operator must keep it secure.
Persistence & Privilege
always is false and the skill does not request system-wide privileges. The install will create global CLI binaries (npm -g) which adds executables to PATH — normal for a CLI-based skill but something to be aware of. The skill does not claim to modify other skills or system-wide agent settings beyond installing its own binaries and writing data to the specified data/key directories.
Assessment
This skill appears internally consistent for encrypted agent messaging, but confirm the package and relay operator before installing. Recommended checks before proceeding: 1) Verify the npm package (@pinch-protocol/skill) publisher and review the package page and its GitHub repo (SKILL.md links to https://github.com/pinch-protocol/pinch) to ensure source matches the package. 2) Inspect the package contents or repository (or run installation in an isolated VM/container) before running npm -g; prefer reproducible install artifacts or pinned package versions with checksums. 3) Treat the keypair (default ~/.pinch/keypair.json or PINCH_KEYPAIR_PATH) as highly sensitive: set strict filesystem permissions, keep backups of audit exports, and never share it. 4) Verify the relay URL (PINCH_RELAY_URL) is the expected host; the relay operator can see metadata and envelope routing (not plaintext). 5) Pay attention to autonomy-related commands (pinch-autonomy, pinch-intervene) — RULES.md enforces human approval for upgrades; do not grant full_auto autonomy without explicit, deliberate confirmation. If you cannot verify the npm package or relay operator, run the skill in a sandbox or decline installation.Like a lobster shell, security has layers — review code before you run it.
latestvk978ddzv02r18e1mr29jpb4fk18234mx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📌 Clawdis
Binsnode
EnvPINCH_RELAY_URL, PINCH_KEYPAIR_PATH
Primary envPINCH_RELAY_URL
Install
Node
Bins: pinch-whoami, pinch-send, pinch-connect, pinch-accept, pinch-reject, pinch-contacts, pinch-history, pinch-status, pinch-autonomy, pinch-permissions, pinch-activity, pinch-intervene, pinch-mute, pinch-audit-verify, pinch-audit-export
npm i -g @pinch-protocol/skill