Webhook Platform Skill: What It Does and How to Install It

Helps you design the outbound webhooks your platform sends: events, signing, retries and the debugging tools.

Installs: 9.7K; on skills.sh
Stars: 9; on GitHub
Files: 5; besides SKILL.md
Updated: Nov 2026; last repo commit

webhook-platform-design makes Claude act as an outbound-webhook platform designer. It works in seven steps: event taxonomy and catalog, payload envelope and schema versioning, an HMAC signing scheme (Standard Webhooks), at-least-once delivery with retry and dead-letter policy, subscription lifecycle states, a debugging surface (delivery logs, replay, test events), and documentation.

It loads when you mention webhooks, event callbacks, signatures, delivery retries or a webhook consumer portal. It covers the provider side only; consumer-side retry mechanics go to api-idempotency-retry. It asks six clarifying questions and bundles four reference files and no scripts.

Good for

API teams adding webhooks to a product
Teams whose retry policy drops events after a few attempts
Platform leads asked by enterprise buyers how webhooks are signed

Install webhook-platform-design

Claude Code

Copy this prompt.

Install the webhook-platform-design skill in Claude Code. Run this command:

/plugin marketplace add samber/developer-platform-skills
/plugin install developer-platform-skills@developer-platform-skills

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

The README installs every skill in the repo (61 skills/*/SKILL.md in the git tree), because skills here reference each other. webhook-platform-design is one of them. Pick one route, not both.

From the project README. Source.

What's in the skill

When it loads

Design a provider-side outbound webhook platform - event taxonomy and catalog, payload envelope and schema versioning, an HMAC signing scheme (Standard Webhooks), at-least-once delivery with retry/backoff and dead-letter policy, subscription lifecycle states, and the developer-facing debugging surface (delivery logs, replay, test-event triggering). Use whenever the user mentions webhooks, event callbacks, push events to customer endpoints, webhook signatures, delivery retries, or a webhook consumer portal - even if they never say "webhook platform". Provider side only. Do NOT use for consumer-side retry mechanics - use samber/developer-platform-skills@api-idempotency-retry instead.

Sections in SKILL.md

Clarifying questions
Consumer sophistication
Build vs buy
Workflow
1. Event taxonomy and catalog
2. Payload envelope and schema versioning
3. Signing scheme
4. Delivery contract: guarantees, retry, dead-letter
5. Subscription lifecycle
6. Debugging surface
7. Documentation
Failure modes
Measurement
Invocation examples
References

Key facts

Author: Samuel Berthe
Repo: samber/developer-platform-skills, which holds 61 skills
License: MIT (LICENSE, README, plugin.json and SKILL.md all say MIT)
Version in SKILL.md: 1.0.2
Installs on skills.sh: 9,680 (Nov 2, 2026)
GitHub stars (repo): 9 (Nov 2, 2026)
Last commit (repo): Nov 1, 2026
What installs: 6 files including SKILL.md: 4 reference files and evals/evals.json; no scripts
Needs: The other skills in the repo; the README says to install all of them
Works in: Claude.ai, Claude Code, Codex, Cursor, Gemini CLI, and tools that read skills.sh installs

What it includes

Asks six questions, including consumer sophistication and build versus buy.
Try: “Our webhook system retries three times in a row then drops the event, and customers keep missing deliveries - redesign the retry and dead-letter policy.”
Clarifying questions
Defines the events and the catalog.
1. Event taxonomy and catalog
Designs the payload envelope and schema-versioning story.
2. Payload envelope and versioning
Adopts an HMAC signing scheme, Standard Webhooks.
3. Signing scheme
Sets guarantees, retry policy and dead-lettering.
4. Delivery contract
Models subscription states.
5. Subscription lifecycle
Designs delivery logs, replay and test-event triggering.
6. Debugging surface
Documents everything against a five-element rubric.
7. Documentation

From the official docs

Permissions

Low risk

This skill writes design advice and bundles no scripts, so the main thing to watch is where your agent saves notes.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It may save notes to developer-platform-context.md
SKILL.md says that when your agent keeps memory in a file, it should consider using this file name. Our advice: keep it out of commits if it holds company plans. github.com

Technical details

Scopes	Asks you interview questions and writes a design document from your answers

Questions

How do I install webhook-platform-design?

Use the install box at the top of this page. The README says to install every skill in samber/developer-platform-skills, not one, because the skills hand work to each other. Pick one route per agent.

Does webhook-platform-design work in Claude, Codex and Cursor?

The README documents install routes for Claude.ai (plugin marketplace), Claude Code, Codex, Cursor, Gemini CLI and the skills.sh CLI. The install box lists each one.

What does it ask me before it designs anything?

SKILL.md lists six questions to ask first, and the answers change the later steps. Have your current setup and constraints ready.

Does it run scripts or need an API key?

It bundles no scripts. The folder holds SKILL.md, reference Markdown files and an evals file, and the skill works by asking you questions and writing advice.

Is webhook-platform-design safe to install?

It bundles no scripts, so installing it adds instructions and reference files rather than programs. SKILL.md also suggests that, if your agent keeps notes in a file, it uses developer-platform-context.md. Our advice: keep that file out of public commits if it holds company plans, and check any figures the skill cites against their sources before quoting them to customers.

Is this for receiving webhooks?

No. SKILL.md says it is provider side only and points consumer-side retry mechanics to api-idempotency-retry.

Information

updated Nov 2, 2026

Repository: samber/developer-platform-skills
Folder: skills/webhook-platform-design

samber/developer-platform-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 2

samber/developer-platform-skills README · github.com
webhook-platform-design SKILL.md · github.com