← Back to Skills Marketplace
Openhook Cli
by
Berkant Ay
· GitHub ↗
· v1.0.2
· MIT-0
221
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install openhook-cli
Description
Receive real-time webhook events from platforms like GitHub, Stripe, Linear, and coordinate multi-agent workflows via messaging channels.
Usage Guidance
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.
Capability Analysis
Type: OpenClaw Skill
Name: openhook-cli
Version: 1.0.2
The skill bundle facilitates the installation and use of the 'openhook' CLI, which involves high-risk actions such as adding a third-party Homebrew tap (openhook-dev/openhook) and running background daemons (openhook daemon start) as described in SKILL.md. While these capabilities are consistent with the stated purpose of webhook management and agent-to-agent communication via openhook.dev, they represent a significant security risk for an automated agent due to the potential for binary execution and persistence. Additionally, _meta.json contains an anomalous future-dated timestamp (2026), which is a common indicator of automated or non-standard package generation.
Capability Assessment
Purpose & 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.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openhook-cli - After installation, invoke the skill by name or use
/openhook-cli - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
Added credential declaration in frontmatter to satisfy security scan
v1.0.1
Fixed security scan warnings: removed curl|sh installer, documented API key requirement
v1.0.0
Initial release of openhook-cli.
- Introduces CLI for receiving real-time events from platforms like GitHub, Stripe, Linear, and Vercel.
- Supports agent-to-agent communication via channels for multi-agent workflows.
- Provides installation instructions for Homebrew and shell script.
- Adds commands for subscribing to events, listening interactively or as JSON, managing background daemons, and handling channels.
- Includes examples for common event automation patterns and channel-based workflows.
- Reference section lists all available CLI commands and their descriptions.
Metadata
Frequently Asked Questions
What is Openhook Cli?
Receive real-time webhook events from platforms like GitHub, Stripe, Linear, and coordinate multi-agent workflows via messaging channels. It is an AI Agent Skill for Claude Code / OpenClaw, with 221 downloads so far.
How do I install Openhook Cli?
Run "/install openhook-cli" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Openhook Cli free?
Yes, Openhook Cli is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Openhook Cli support?
Openhook Cli is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Openhook Cli?
It is built and maintained by Berkant Ay (@berkantay); the current version is v1.0.2.
More Skills