CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

postmark-webhooks

Use when setting up Postmark outbound webhooks for tracking email delivery, bounces, opens, clicks, spam complaints, or subscription changes — includes webhook configuration, endpoint verification, per-webhook statistics, retry behavior, payload handling, and security.

1.22x
Quality

91%

Does it follow best practices?

Impact

99%

1.22x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is highly actionable and well-structured, with executable code, precise API facts, and an exemplary progressive-disclosure layout pointing to real reference files. Its one weakness is redundancy — the Notes and Common Mistakes sections restate material from the dedicated sections, and time-sensitive CVE/release details are inlined rather than referenced.

Suggestions

Trim the Notes section to only facts not already covered: the full retry-ladder restatement, verification rules (422/1364), and idempotency advice all duplicate dedicated sections above.

State the "respond 200 immediately, then process asynchronously" guidance once (e.g., Quick Start step 6) instead of four times across Quick Start, two Common Mistakes rows, and Notes.

Move the CVE-2026-111497 compression details and the October 2026 Node.js release pointer into references/security.md, keeping a single-line advisory inline.

DimensionReasoningScore

Conciseness

The body is mostly dense, non-obvious domain fact (retry ladder, 4xx drop rules, verify semantics), but it could be tightened: the Notes section restates the full retry schedule, verification rules, and idempotency advice already given in dedicated sections, "respond 200 immediately, process async" appears in Quick Start, two Common Mistakes rows, and Notes, and time-sensitive specifics (CVE-2026-111497, October 2026 Node.js releases) sit inline rather than in a reference. Not a 2 because it never explains concepts Claude already knows — the redundancy is repetition, not padding with known material.

3 / 5

Actionability

Fully executable throughout: complete Node.js and cURL create-webhook examples, a working Express handler routing on RecordType, exact endpoint paths, retry intervals, header names (X-PM-Retries-Remaining, X-PM-Webhook-Trace-Id), and error codes (422/1364) — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

The 6-step Quick Start is clearly sequenced and the verification flow has real checkpoints — 422/1364 rejection semantics, the "read the Success field, not the status code" rule, and a fix-then-re-verify loop for paused event types. Falls short of 5 because the checkpoints live in separate sections rather than the Quick Start sequence, and there is no step for locally testing the handler before creating the webhook.

4 / 5

Progressive Disclosure

A clear overview body with five real, well-signaled, one-level-deep reference files (webhook-setup, payload-examples, handler-examples, security, bounce-management), each cited at the point of need with its purpose stated (e.g., "for the full response shape and field reference"); bulk detail is appropriately split out and navigation is easy.

5 / 5

Total

17

/

20

Passed

Description

100%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.

The description is exemplary: it names a specific niche (Postmark outbound webhooks), enumerates the six event types that serve as natural trigger phrases, and explicitly covers both when to use it and what it includes. Every dimension lands at the top anchor with no vagueness or padding.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — "webhook configuration, endpoint verification, per-webhook statistics, retry behavior, payload handling, and security" — plus all six tracked event types (delivery, bounces, opens, clicks, spam complaints, subscription changes), giving comprehensive coverage with no gaps; anchor 4's "minor gaps in coverage" does not apply.

5 / 5

Completeness

Explicitly answers both questions: an explicit "Use when setting up Postmark outbound webhooks for tracking…" trigger clause with concrete trigger phrases, and a clear "what" via "includes webhook configuration, endpoint verification, per-webhook statistics, retry behavior, payload handling, and security" — the exact pattern of the anchor-5 example.

5 / 5

Trigger Term Quality

The phrases users would naturally say when they need this skill — "email delivery", "bounces", "opens", "clicks", "spam complaints", "subscription changes" — are all present alongside the domain terms "Postmark" and "webhooks"; coverage is comprehensive for the domain, matching the top anchor rather than the "a few natural terms missing" of anchor 4.

5 / 5

Distinctiveness Conflict Risk

"Postmark outbound webhooks" defines a clear brand- and direction-specific niche (explicitly scoping away inbound email webhooks), so it is unlikely to fire for a different skill; minimal conflict risk.

5 / 5

Total

20

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ActiveCampaign/postmark-skills

Path

postmark-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.