agentsclimarketplace
Sign in

Webhook and event lifecycle

Skill gaelic-ghost/socket/skills/webhook-and-event-lifecycle

Design and repair secure inbound events, webhooks, interactions, retries, acknowledgements, and delivery observability for messaging and collaboration platforms.From its SKILL.md

Install
npx -y skills add gaelic-ghost/socket --skill webhook-and-event-lifecycle

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 321 tokens by cl100k_base, as published. Nobody here has run it

Webhook And Event Lifecycle

Purpose

Make inbound messaging events trustworthy, prompt, idempotent, and diagnosable. This skill owns the event boundary; it does not own application business logic, persistent conversation policy, or a platform transport implementation.

Workflow

  1. Read current official delivery and signature-verification documentation for the selected platform.
  2. Capture the platform's request signature, timestamp/replay guard, response deadline, retry policy, event ID, ordering guarantees, and rate limits.
  3. Verify authenticity before parsing or enqueueing work. Reject an invalid request with a descriptive operator-facing log that identifies the platform, validation stage, and likely cause without exposing secrets.
  4. Deduplicate on the platform event identity before side effects. Persist an explicit processing state when retries can outlive a request.
  5. Acknowledge on time, then execute slow work through the selected app runtime. Use platform-native deferred responses where they exist.
  6. Record correlation IDs, delivery outcome, retry count, and a privacy-safe error summary. Do not log raw message content or tokens by default.

Required Output

Document the request verifier, acknowledgement path, duplicate rule, retry and failure behavior, ordering assumption, response/update path, and targeted replay test. Hand service implementation to the chosen server stack skill.

Guards

  • Do not use a shared webhook wrapper merely because multiple providers use HTTP.
  • Do not acknowledge an event as successful before a required signature or idempotency check.
  • Do not claim a webhook works without a platform test delivery, local signed fixture, or observed request trace.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most apis services skills give in 321 tokens

Counted across 448 of the 471 authors here whose files we hold, read 2026-09-06

  • Use HTTP status codes semanticallyin 25 of 448, across 11 files
  • Return 201 with a Location header on createin 24 of 448, across 9 files
  • Name resources plural, lowercase, kebab-casein 23 of 448, across 9 files
  • Configure rate limiting with limit headersin 22 of 448, across 8 files
  • Paginate list endpoints with cursor or offsetin 21 of 448, across 10 files
  • Version APIs in the URL pathin 21 of 448, across 11 files
  • Validate request input with a schemain 21 of 448, across 7 files
  • Add pagination to all list endpointsin 18 of 448, across 15 files
  • Match HTTP method to the operationin 12 of 448, across 6 files
  • Return 400 or 422 with field-level detailsin 12 of 448, across 2 files
  • Check ownership before returning resourcesin 12 of 448, across 2 files
  • Limit query depth and complexityin 12 of 448, across 7 files

Said here and by no other author read

  • Read the platform's current delivery and signature documentation
  • Capture signature, replay guard, response deadline, retry policy, ordering, rate limits
  • Verify authenticity before parsing or enqueueing work
  • Reject invalid requests with descriptive logs that hide secrets
  • Deduplicate on the platform event identity before side effects
  • Persist explicit processing state when retries outlive a request

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.