Hook Contract - check your webhooks, then write the contract
Check a platform's outbound webhooks from the sender's side, then write the event catalog and the delivery contract. Paste the event names, one real delivery and the retry schedule. Free in your browser: names linted (resource.action, past tense, one delimiter); the envelope and the signing scheme read against Standard Webhooks; the delivery's HMAC signature verified with a test secret that never leaves the page; the retry schedule worked out (linear or exponential, attempts, span); dead-lettering, ordering, auto-disable and the debugging surface checked; and verification snippets for Node, Python and Go. A metered run writes the event catalog and envelope, or the delivery contract - at-least-once, the exact schedule, dead-lettering, subscription states and the subscriber docs. Built on the SkillSafe skill @samber/webhook-platform-design, from samber/developer-platform-skills (MIT), by Samuel Berthe.
gpt-terra Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.