Webhook Relay
DocumentationFundamentals

Agent Skills

Install the open-source Webhook Relay Agent Skills so Claude and other skill-aware agents can forward, transform, debug, tunnel, and schedule webhooks with the relay CLI.

Overview

Agent Skills are small, self-contained instruction packs that teach Claude (and other skill-aware agents) how to perform a specific task. Webhook Relay publishes an open-source set of Skills that show agents how to drive the platform with the relay CLI and API — forwarding webhooks, transforming them, debugging incoming requests, exposing services over tunnels, and scheduling recurring webhooks.

The Skills are maintained on GitHub:

Use that repository to browse the source, open issues, or contribute new skills.

Skills vs. MCP

Skills and the MCP server solve related but different problems, and they work well together:

  • Skills are instructions. They teach an agent how to use the relay CLI/API correctly — the right commands, payload shapes, and workflows. They run wherever your agent has a shell.
  • MCP is a live connection. It gives an agent typed tools to manage buckets, inspect webhook logs, and work with transform functions directly against your account.

Install the Skills for guided, command-line workflows; connect MCP when you want the agent to call Webhook Relay tools directly.

Available skills

SkillWhat it does
webhook-debugCapture and inspect webhooks with a free, no-signup bin at bin.webhookrelay.com — a public URL that records any HTTP request so you can see the exact method, headers, query and body a provider sends, stream requests live, mock the response, and verify HMAC signatures. No CLI or account required.
webhook-forwarding-internalReceive webhooks from providers (Stripe, GitHub, Shopify, CI, etc.) and forward them to a destination with no public IP — localhost, a private LAN host, or a Kubernetes service. The relay agent performs the final hop, so no inbound firewall ports are needed. Best for local development.
webhook-forwarding-publicForward webhooks server-side from a public Webhook Relay endpoint to another internet-reachable URL — no local agent required. Relay between cloud services, put a stable URL in front of an API, fan one webhook out to many destinations, or transform payloads in transit.
webhook-transformationsWrite, test, and attach JavaScript (or Lua) functions that modify webhooks in flight — reshape the JSON body, rename fields, add/remove headers, change the method or path, set the response, drop requests conditionally, or call other HTTP APIs.
relay-tunnelsExpose a local or internal HTTP/TCP service on a stable public hostname (an ngrok-style reverse proxy) without opening firewall ports — share a dev server, demo a local app, expose an internal API, or tunnel TCP (SSH, databases).
recurring-webhooksSchedule cron-driven webhooks that fire automatically — send a recurring HTTP request (method, body, headers) to one or more destinations on an interval or at specific times. Use for health checks, heartbeats, scheduled reports, or triggering a function on a timer.

Installation

The fastest way to install is with the skills CLI:

npx skills add webhookrelay/skills

Add -g to install globally for all your agents:

npx skills add webhookrelay/skills -g

Install a single skill

Pass --skill <name> to install just one:

npx skills add webhookrelay/skills --skill webhook-debug

Claude Code plugin marketplace

The repository doubles as a Claude Code plugin marketplace. Add it, then install the plugin:

/plugin marketplace add webhookrelay/skills
/plugin install webhookrelay-skills

Manual install

You can also copy any skills/<name>/ folder from the repository into your agent's skills directory.

Prerequisites

The webhook-debug skill works against the public bin API with nothing but curl — no account or key needed.

Every other skill uses the relay CLI:

  1. Install it — see CLI installation.
  2. Log in: relay login (or set the RELAY_KEY / RELAY_SECRET environment variables).
  3. Verify: relay bucket ls.

Concepts at a glance

  • Bucket — groups inputs and outputs.
  • Input — a public HTTPS endpoint that receives webhooks.
  • Output — a destination requests are relayed to; internal (delivered by a running agent, e.g. localhost) or public (delivered server-side).
  • Function — server-side JavaScript/Lua that transforms requests/responses.
  • Tunnel — a public hostname that proxies inbound HTTP/TCP to a local or internal service.
  • Cron — a scheduled, recurring webhook.

See Getting Started for the full model.

Issues and contributions

The Skills are open source. To report a problem, request a new skill, or read the code, use the GitHub repository:

Did this page help you?