Claude Code plugin

import { Aside, Steps } from ‘@astrojs/starlight/components’

The Hookman plugin for Claude Code adds skills that drive the Hookman CLI for you. Ask Claude to route a webhook to a branch, work out why a delivery failed, or forward webhooks to your laptop, and it runs the right commands and explains what it found.

It doesn’t talk to Hookman on its own: it runs the hookman CLI as you, with your login or HOOKMAN_API_KEY.

Install

1. Add the Hookman marketplace and install the plugin:

   claude plugin marketplace add royletron/hookman
   claude plugin install hookman@hookman

2. Make sure you have the CLI and an account. The setup skill checks both, or install the CLI yourself:

   npm i -g @hookman/cli
   hookman login

To try the plugin from a checkout of the repository without installing it, start Claude Code with claude --plugin-dir ./packages/claude-plugin.

To pick up new versions, run claude plugin update hookman@hookman.

Skills

Skill	Use it to
/hookman:setup	Install and log in to the CLI, register this branch’s deployment, and get the endpoint to give your webhook provider. Runs only when you invoke it.
/hookman:routing-rules	Create and remove routing rules, and register, switch or remove deployments.
/hookman:debug-webhook	Work out why a webhook failed, didn’t arrive, or went to the wrong deployment.
/hookman:local-dev	Forward real webhooks to a server on your machine with hookman listen.
/hookman:test-email	Test sign-up, verification and magic-link flows with throwaway inboxes.

Claude also uses routing-rules, debug-webhook, local-dev and test-email on its own when your request matches, so you can just describe what you want:

• “Send Stripe test events to the staging deployment.”
• “Why did the last Stripe webhook return a 422?”
• “Forward webhooks for the feature/checkout deployment to localhost:4242.”
• “Create an inbox and run the sign-up flow against it.”

What it will and won’t do

Routing changes made with the CLI go live immediately. The plugin asks Claude to confirm with you before running `hookman rule set`, `hookman rule remove`, `hookman switch` or `hookman remove`.

• Debugging is read-only. debug-webhook only reads logs; it won’t change routing while it investigates.
• Replay isn’t in the CLI. To replay a stored payload, use the dashboard’s log view; see Webhook replay.
• Dashboard-only features. Reordering rules, enabling or disabling them, nested conditions and fan-out are managed in the dashboard or API, so the plugin can describe them but not change them.
• Inboxes need a Pro or Team plan and are being rolled out gradually. If your organisation doesn’t have them yet, test-email says so rather than retrying.
• No secrets in files. The setup skill never writes an API key into a file that would be committed; in CI, use a repository secret.

Related

• CLI reference: every command the skills use
• llms.txt: a machine-readable summary of these docs for other AI tools