agentsclimarketplace

Webhook and event lifecycle

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

The Source for macOS Agent Workflows

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.

What its author says it does

Copied from the file, not written here

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

SKILL.md

1.9 KB, 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.

Gives 0 of the 12 instructions most apis services skills give

Counted across 424 of the 426 authors here whose files we hold, read 2026-08-06

  • use plural nouns for resource namesin 41 of 424, across 32 files
  • use cursor-based pagination for large datasetsin 35 of 424, across 20 files
  • include rate limit headers in responsesin 25 of 424, across 13 files
  • Use kebab-case for multi-word resourcesin 23 of 424, across 13 files
  • version APIs in the URL pathin 19 of 424, across 9 files
  • use semantic HTTP status codesin 18 of 424, across 8 files
  • verify webhook signaturesin 18 of 424, across 11 files
  • use query parameters for filteringin 17 of 424, across 6 files
  • use async database operationsin 14 of 424, across 7 files
  • wrap successful responses in a data fieldin 13 of 424, across 3 files
  • prefix sorting parameters with a hyphen for descending orderin 13 of 424, across 3 files
  • set appropriate HTTP status codesin 13 of 424, across 6 files

Said here and by no other author read

  • read current official platform delivery and signature documentation
  • capture platform signature, replay guard, deadline, and retry policy
  • verify request authenticity before parsing or enqueuing work
  • reject invalid requests with a descriptive operator-facing log
  • deduplicate on platform event identity before side effects
  • persist explicit processing state when retries outlive requests

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. 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.