- Home
- Skills
- Testing & Debugging
- Webhook Delivery Reliability Audit
Works with the AI Agents you already use
Webhook Delivery Reliability Audit
Audit webhook logs by event and destination. Separate retries and duplicate acknowledgements, flag signature failures, and measure delivery, timeliness and missing evidence with explicit denominators.
$5
Webhook Delivery Reliability Audit
Example session with this skill installed
Synthetic demonstration request
Audit orders.webhook deliveries for 2026-11-02, events emitted 10:00:00–10:07:00 UTC, one per minute. Expected events evt-1..evt-8 (source of truth is complete). SLA: a 2xx within 120 s of emit. Success = 2xx; trusted = 2xx AND signature verified. Evidence cutoff 10:15:00 UTC. Report coverage, delivery, timeliness, duplicates, signature failures and next investigations. Do not resend anything.
Rows are delivery attempts, not a status stream. Times are UTC on 2026-11-02.
| Row | Event | Attempt | Emit | Finish | Status | Final | Sig OK |
|---|---|---|---|---|---|---|---|
| 1 | evt-1 | a1 | 10:00:00 | 10:00:03 | 200 | true | yes |
| 2 | evt-2 | a1 | 10:01:00 | 10:01:02 | 500 | false | - |
| 3 | evt-2 | a2 | 10:01:00 | 10:01:40 | 200 | true | yes |
| 4 | evt-3 | a1 | 10:02:00 | 10:02:04 | 200 | true | no |
| 5 | evt-4 | a1 | 10:03:00 | 10:03:03 | 200 | true | yes |
| 6 | evt-4 | a2 | 10:03:00 | 10:03:30 | 200 | true | yes |
| 7 | evt-5 | a1 | 10:04:00 | 10:04:05 | 503 | false | - |
| 8 | evt-5 | a2 | 10:04:00 | 10:06:00 | 503 | false | - |
| 9 | evt-5 | a3 | 10:04:00 | 10:09:00 | 503 | true | - |
| 10 | evt-6 | a1 | 10:05:00 | 10:08:30 | 200 | true | yes |
| 11 | evt-8 | a1 | 10:07:00 | 10:07:02 | 200 | true | yes |
evt-7 (emitted 10:06:00) has no attempt row.
- Read your context and instructions
- Compiled the webhook delivery reliability
Six of eight expected events delivered a 2xx by cutoff; five were on time and five were signature-verified; four satisfied both conditions. evt-7 has no observation in a complete export, and evt-5 exhausted three attempts returning 503. evt-4 was delivered twice (idempotency risk) and evt-3 was accepted with an invalid signature (security finding).
Contract: orders.webhook; 8 due events evt-1..evt-8; 120 s SLA; cutoff 10:15:00; complete export; signature required for trust. Eleven attempts cover seven events.
| Measure | Result |
|---|---|
| Due events | 8 |
| Outcome reconciliation | 6 delivered + 1 failed + 1 missing = 8 |
| Observed coverage | 7/8 = 87.50% |
| Delivery by cutoff | 6/8 = 75.00% |
| On-time delivery (<=120s) | 5/8 = 62.50% |
| Trusted delivery (2xx + sig) | 5/8 = 62.50% |
| Retry recoveries | 1 (evt-2) |
| Duplicate deliveries | 1 (evt-4) - idempotency risk |
| Signature failures | 1 (evt-3) - security finding |
| Event | Outcome | Evidence / next check |
|---|---|---|
| evt-2 | Delivered, on time via retry | Rows 2-3: 500 then 200 at 10:01:40 (40 s) |
| evt-3 | Delivered, signature invalid | Row 4: verify signing secret and verification path before trusting payload |
| evt-4 | Delivered twice | Rows 5-6: two 2xx for one event; confirm the receiver is idempotent |
| evt-5 | Failed (exhausted) | Rows 7-9: three 503s, final at 10:09:00; inspect upstream cause |
| evt-6 | Delivered, late | Row 10: first 2xx at 10:08:30, 210 s > 120 s SLA |
| evt-7 | Missing | No row in a complete export; compare dispatch history to ingestion |
First-success latencies: 3, 40, 4, 3, 210, 2 s -> min/median/max = 2/3.5/210 s (n=6). These are delivery latencies, not uptime. Investigate evt-7 and evt-3 first (unknown disposition, verification failure), then evt-4, evt-5, evt-6. No production changes were made.
Connects securely to your tools. The creator never sees your data.
About this skill
Stop trusting a wall of 200s
A webhook can return 200 twice for the same event, succeed only on its third retry, or never arrive at all. Counting success lines hides every one of those. This skill guides your AI agent through a read-only audit of webhook delivery logs, keeping logical event–destination pairs separate from delivery attempts so retries and duplicates do not distort the numbers.
What you receive
- A SKILL.md workflow plus a synthetic worked example.
- A clear audit contract: expected events, window, evidence cutoff, SLA, success and trust definitions.
- Reconciled outcomes per expected event–destination pair: delivered, failed, unresolved, and missing or unknown evidence.
- Observed coverage, delivery, on-time and trusted-delivery rates with explicit denominators.
- Duplicate-delivery (idempotency) flags, signature-verification failures, retry recoveries, latency, and traceable next-step investigations.
How to use it
Ask your compatible agent to audit your webhook delivery logs. Provide a redacted export or pasted records (event id, endpoint, attempt, status, timestamps, final flag, signature result), the list of events that were expected, a time zone, a cutoff and an SLA. The agent produces the report; you decide what to investigate.
Boundaries
Instruction skill, not a hosted monitor or a webhook replayer. It does not connect to providers, resend deliveries, change endpoints, or guarantee delivery. No required paid API. An incomplete export cannot prove a missing delivery; it is reported as unknown coverage. Large exports need an analysis-capable agent with local tools.
Validation
Frontmatter and package validation pass. The worked-example arithmetic reconciles (6 delivered + 1 failed + 1 missing = 8 due events) and was checked programmatically. The demonstration is synthetic, not customer production data. Results depend on the quality of supplied evidence and the agent used.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.
Read-only instruction skill, not monitoring, a replayer, or an integration. Cohort rates require expected event–destination pairs and usable correlation/time evidence; on-time metrics require an SLA. Incomplete exports cannot prove non-delivery, and HTTP acknowledgements do not prove downstream business processing. Signature trust requires explicit evidence. Ordering needs source sequence. Large exports require local analysis tools; results depend on evidence and agent capability.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 9 days ago
Permissions
Read-only analysis of user-provided webhook logs. File reading is needed only for supplied files; terminal/local analysis is optional for larger exports. No network, credentials, environment variables, provider connections, or production writes are required.