CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

courier-webhooks

Receive and verify Courier outbound webhooks. Use when setting up Courier webhook handlers, debugging courier-signature verification, or handling notification and audience events like message:updated, notification:submitted, or audiences:updated.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

The core technical content is excellent: complete executable verification code with thoughtful handling of the undocumented timestamp unit, a clean event envelope description, and well-signaled reference files. The main weaknesses are non-essential tail sections that spend tokens on cross-promotion rather than the task, and example links pointing at paths missing from the bundle.

Suggestions

Trim the cross-promotional tail: cut the 10-item 'Related Skills' list to 1-2 most-relevant entries and drop or compress the 'Attribution' section, which add ~25 lines without aiding the webhook task.

Remove the 'When to Use This Skill' section, which restates the frontmatter description and spends tokens on content Claude already receives at trigger time.

Fix or remove the dangling examples/express/, examples/nextjs/, and examples/fastapi/ links, since those directories are absent from the bundle — replace with a note that full handlers live in the upstream repository.

DimensionReasoningScore

Conciseness

The core sections (Verification, Event Payload Structure, Event Types) are tight and avoid explaining concepts Claude already knows, but the body carries unnecessary padding: a 10-item "Related Skills" link list, an "Attribution" section, and a "When to Use This Skill" section that duplicates the frontmatter description. This is more than the 'minor instances that could be trimmed' of the 4 anchor, though not the pervasive padding of a 2.

3 / 5

Actionability

The verification section is fully executable, copy-paste-ready JavaScript with unit normalization, stale-delivery rejection, timing-safe comparison, and a length-mismatch guard, plus a concrete env var and a runnable hookdeck-cli tunnel command. It matches the 'fully executable, covers common cases' top anchor rather than the 4 anchor's 'minor gaps'.

5 / 5

Workflow Clarity

The body lays out a coherent implicit sequence (configure secret via env var -> tunnel for local dev -> verify -> dispatch on top-level `type`), and the code embeds validation checkpoints (staleness rejection, false-on-parse-failure). It is not a 5 because the full handler workflow (verify, parse, respond, idempotency) is deferred to an external skill and no guidance is given on responding to failed verification.

4 / 5

Progressive Disclosure

The SKILL.md is a clear overview with three real one-level-deep references (references/overview.md, setup.md, verification.md) well-signaled in a 'Reference Materials' section. It is not a 5 because the body links to examples/express/, examples/nextjs/, and examples/fastapi/ directories that are not present in the bundle, so those navigation paths dangle.

4 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

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

A strong description with a clear what and an explicit, multi-clause 'Use when' trigger list naming concrete events and the signature header. Third-person-free imperative voice matches the exemplars. Minor room to expand capability coverage and add a few natural term variants.

DimensionReasoningScore

Specificity

"Receive and verify Courier outbound webhooks" names the domain and several concrete actions, reinforced with specific artifacts like "courier-signature verification" and event names "message:updated, notification:submitted, or audiences:updated". It falls short of the 5 anchor because it omits other capabilities the skill covers (setup configuration, local tunneling, event dispatch handling).

4 / 5

Completeness

It explicitly answers both what ("Receive and verify Courier outbound webhooks") and when ("Use when setting up Courier webhook handlers, debugging courier-signature verification, or handling notification and audience events like...") with concrete trigger phrases, matching the top anchor. It is not a 4 because the 'when' clause is already explicit and specific, not merely present-with-room-to-improve.

5 / 5

Trigger Term Quality

Natural user phrases are present: "setting up Courier webhook handlers", "debugging courier-signature verification", and exact event names users would cite. A few natural variants (e.g., "Courier notifications", "webhook events") are missing, keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The Courier brand and provider-specific terms ("courier-signature", "message:updated", "audiences:updated") form a clear niche with minimal conflict risk against the many sibling webhook skills. Not a 4 because no closely related skill (e.g., knock-webhooks) would plausibly trigger on these terms.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

hookdeck/webhook-skills

Path

skills/courier-webhooks/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.