Hookdeck

v1.0.2

Hookdeck integration. Manage Connections, Issues, Workflows. Use when the user wants to interact with Hookdeck data.

0· 159·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The SKILL.md describes using the Membrane CLI to manage Hookdeck resources (connections, events, destinations, etc.). Requiring the Membrane CLI and a Membrane account is coherent with the stated Hookdeck integration purpose.
Instruction Scope
The instructions tell the user to install @membranehq/cli, run membrane login (browser-based auth), and use membrane commands (search, connect, action run, request). These are within scope for a CLI-based integration. Note: the skill relies on Membrane's proxy to forward requests to Hookdeck and to manage credentials — so API traffic and credentials will be handled by the Membrane service.
Install Mechanism
There is no automated install spec in the skill bundle; instead SKILL.md instructs the user to run 'npm install -g @membranehq/cli'. Installing a public npm CLI is a normal, moderate-risk step. Because the skill is instruction-only, no code is written by the skill itself.
Credentials
The skill declares no required env vars or credentials. Authentication is performed via Membrane's login flow (browser-based) and credential management is handled by Membrane; this is proportional to the integration's needs. Users should note that credentials and proxied API calls are managed by Membrane.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and has no install-time persistence specified. It relies on the Membrane CLI and user login, which is normal for a CLI-based integration.
Assessment
This skill is an instruction-only guide for using the Membrane CLI to access Hookdeck. Before installing/using it: (1) verify you trust Membrane (getmembrane.com, @membranehq/cli on npm and the GitHub repo) because the CLI will proxy requests and manage credentials on your behalf; (2) be aware you must install a global npm package and perform a browser-based login; (3) review what data will be proxied to Membrane (events, requests) and whether that is acceptable for your organization; (4) if you prefer not to route traffic through a third party, consider using Hookdeck's APIs directly with scoped API keys. If you want a deeper check, verify the @membranehq/cli package integrity on npm and inspect the repository source before installing.

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

latestvk974aejzjdph9njhj9x3az37c18425nv

License

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

Comments