Agent skill · software engineering · jeremylongshore
adobe-webhooks-events
Implement Adobe I/O Events registration, challenge validation, authentic delivery, idempotent enqueue, replay operations, and disablement recovery. Use when the task requires adobe i/o events authentic delivery. Trigger with "Adobe webhook", "Adobe I/O Events", or "verify Adobe event".
Why this skill is useful
Adds specific implementation details for Adobe I/O Events webhook registration and signature verification that the AI wouldn't reliably generate on its own.
What it needs
Requires @adobe/aio-lib-events installed locally. Requires adobe account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Adobe I/O Events Authentic Delivery Overview Implement Adobe I/O Events registration, challenge validation, authentic delivery, idempotent enqueue, replay operations, and disablement recovery. This workflow produces a reviewable artifact and evidence before any live side effect. Prerequisites Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle. Named product, identity, security, data, budget, release, and operations owners appropriate to the scope. Synthetic or approved non-production fixtures with secret and content canaries. Current Contract Webhook endpoints are public HTTPS and must echo the GET challenge during registration. Event delivery is at least once and may duplicate or arrive out of order. Validate recipientclientid plus the digital signature/public key from a validated static.adobeioevents.com URL, or use an approved mTLS configuration. Recheck the dated evidence map before relying on mutable product behavior. Authentication Use an entitled Developer Console project and least-privilege credential for registration administration. Delivery handlers never receive or log management credentials. Instructions 1. Resolve provider, event codes, organization/project/workspace, registration owner, endpoint, and data classification. 2. Validate the Registration API schema from current docs; do not copy a remembered payload or integration route. 3. Implement a narrow GET challenge response and POST size/type/schema checks before business processing. 4. Verify recipient client ID and signature/key allowlist or mTLS, then deduplicate on event identity before enqueue. 5. Acknowledge quickly; process asynchronously with ordering-aware state, retry budgets, DLQ, and replay controls. 6. Monitor retries and journal/recovery windows, manually re-enable disabled registrations, and reconcile gaps. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-webhooks-events