CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/webhook-delivery-tester

Build-an-X for webhook delivery + receiver tests per Standard Webhooks (standardwebhooks.com) - HMAC-SHA256 signature verification, retry semantics with exponential backoff + jitter, replay-window check via timestamp tolerance, ordering guarantees, dead-letter handling for permanent failures, content-type + body-encoding fidelity. Use when authoring tests for webhook senders OR receivers in any system (Stripe / Twilio / SendGrid / GitHub / GitLab outbound webhooks; SaaS app inbound webhooks).

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is lean, actionable, and well-sequenced with executable test code and a clear end-to-end checklist. Content is appropriately split into one one-level-deep reference file holding the retry/vendor lookup data.

DimensionReasoningScore

Conciseness

Lean body focused on what Claude doesn't already know: signing scheme, header formats, and test recipes; no generic explanations of what webhooks or HMAC are. A couple of lines (overview bullets, references) are background but earn their place.

3 / 3

Actionability

Provides fully executable Python test functions for signing, retry, signature verification, replay defense, idempotency, and ordering, plus a concrete to-sign scheme and header examples; copy-paste ready.

3 / 3

Workflow Clarity

Clear Step 1-9 sequence with an end-to-end checklist and a 'critical' escalation callout for replay/out-of-order gaps; anti-patterns table ties fixes back to steps, giving explicit feedback/validation guidance.

3 / 3

Progressive Disclosure

SKILL.md stays as an overview with a single one-level-deep reference (references/vendor-payloads-and-retries.md) that is clearly signaled in both Step 3 and Step 7; the reference file holds the lookup table as described.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, action-oriented, and explicitly scoped with a 'Use when' trigger clause and concrete vendor examples. It is slightly dense but covers both what and when clearly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: HMAC-SHA256 signature verification, retry semantics with exponential backoff + jitter, replay-window check via timestamp tolerance, ordering guarantees, dead-letter handling, content-type + body-encoding fidelity.

3 / 3

Completeness

Explicitly answers what (the build-an-X capability enumerated) and when ('Use when authoring tests for webhook senders OR receivers...').

3 / 3

Trigger Term Quality

Good coverage of natural terms users would say: 'authoring tests for webhook senders OR receivers', 'Stripe / Twilio / SendGrid / GitHub / GitLab outbound webhooks', 'SaaS app inbound webhooks'.

3 / 3

Distinctiveness Conflict Risk

Clear niche (webhook delivery + receiver testing per Standard Webhooks) with distinct triggers; unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents