Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Openhook Cli
v1.0.2Receive real-time webhook events from platforms like GitHub, Stripe, Linear, and coordinate multi-agent workflows via messaging channels.
⭐ 0· 100·0 current·0 all-time
byBerkant Ay@berkantay
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md describes receiving webhooks (GitHub, Stripe, etc.) and coordinating agent-to-agent channels — requiring an Openhook API key is coherent with that purpose. However, the registry metadata lists no required environment variables while the SKILL.md explicitly requires OPENHOOK_API_KEY, an inconsistency between declared metadata and the instructions.
Instruction Scope
Instructions are mostly limited to using the openhook CLI (subscribe, listen, daemon, channel create/subscribe/send). They do not ask the agent to read unrelated local files or arbitrary environment variables. One behavioural risk: channels and endpoints allow sending messages (and therefore arbitrary payloads) to other agents or endpoints — this is expected for the feature but expands the surface for data transfer/exfiltration.
Install Mechanism
The skill is instruction-only (no install spec), but the README recommends installing via a Homebrew tap (openhook-dev/openhook) hosted on GitHub. That is a standard source, but because there is no enforced install spec, the agent or user could be running different versions or binaries from other locations — verify the tap and binary provenance before executing.
Credentials
The SKILL.md requires OPENHOOK_API_KEY (oh_live_ or oh_test_) to operate. The registry metadata, however, lists no required env vars or primary credential — this mismatch is concerning. The single API key is proportionate to the functionality, but it grants full access to the user's Openhook account (subscriptions, channels, messages), so treat the key as sensitive and prefer a scoped/test key where possible. The instructions also reference endpoint IDs and channel IDs (which act like additional credentials) but do not document how they should be secured.
Persistence & Privilege
The skill does not request always: true, does not include install-time code, and does not request system-wide configuration changes. It can be invoked autonomously (default) which is normal for skills; combine this with the API key access when assessing risk.
What to consider before installing
Before installing: verify the Homebrew tap and the GitHub repo (https://github.com/openhook-dev/openhook-cli) to ensure the CLI is the legitimate project; confirm that OPENHOOK_API_KEY is required (the registry metadata omission is likely an error) and consider creating a limited-scope or test key (oh_test_*) for evaluation. Understand that channels/endpoints can ferry arbitrary data to external recipients — do not send secrets or internal-only payloads through openhook channels. Restrict agent autonomy if you do not want the agent to send messages or create subscriptions without explicit approval. If anything about the provenance, API key scope, or endpoint IDs is unclear, ask the publisher for clarifying documentation before granting access.Like a lobster shell, security has layers — review code before you run it.
latestvk9739xy7tr4fmhdnagpr2hmzk1837bqy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.