Hookdeck
Analysis
This Hookdeck skill is purpose-aligned, but it asks the agent to install an unpinned third-party CLI, use remote agent instructions, and grant Membrane access to Hookdeck-related credentials.
Findings (9)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
`clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.
The skill tells the agent to consume remote instructions from a connection workflow as instructions for its own behavior, without saying they must be treated as untrusted or subordinate to the user request.
`membrane connection ensure "https://hookdeck.com/" --json` ... `If no app is found, one is created and a connector is built automatically.`
The CLI instruction can create account-side connections/connectors automatically, and the artifact does not clearly define approval, rollback, or containment boundaries for these mutations.
npm install -g @membranehq/cli@latest
The skill instructs a global npm installation using the moving `@latest` tag, so the installed code is not pinned to a reviewed version.
npx @membranehq/cli connection get <id> --wait --json
The skill includes shell commands that execute a package through npm/npx. This is expected for a CLI-based integration, but users should recognize it runs local code.
Hookdeck is a webhook management tool ... transformations, and retries to ensure webhooks are delivered and handled correctly.
Hookdeck configuration can affect webhook delivery and integrations. This is central to the skill's purpose, but mistakes in webhook routing, transformations, or retries can affect downstream systems.
This skill uses the Membrane CLI to interact with Hookdeck.
The skill is branded as a Hookdeck integration but clearly discloses that Membrane is the operational intermediary. This is not deceptive, but it is an important trust distinction.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Membrane handles authentication and credentials refresh automatically
The skill depends on delegated authentication and credential refresh. This is aligned with managing Hookdeck data, but it grants sensitive account access through Membrane.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Each result includes `id`, `name`, `description`, `inputSchema` ... and `outputSchema`
The agent is expected to use retrieved action metadata and descriptions as context for choosing actions. This is purpose-aligned, but retrieved descriptions can be over-trusted if not validated against the user's goal.
This skill uses the Membrane CLI to interact with Hookdeck. Membrane handles authentication and credentials refresh automatically
Hookdeck access is mediated through an external provider/CLI that handles authentication. This is disclosed and purpose-aligned, but it creates a third-party data and credential boundary users should understand.
