CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

postmark-inbound

Use when processing incoming emails with Postmark inbound webhooks — building reply-by-email, email-to-ticket, document extraction, or any workflow that receives and parses email.

1.17x
Quality

85%

Does it follow best practices?

Impact

100%

1.17x

Average score across 3 eval scenarios

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 body is highly actionable with copy-paste code, precise operational details, and a clean four-file reference structure. Its main weaknesses are redundancy — the retry block and Notes section repeat content available elsewhere or already stated — and a missing inline test/verification step in the Quick Start workflow.

Suggestions

Remove the duplicated retry table, 403 note, and retry API details from the body (keep a one-line summary pointing to references/inbound-setup.md), or drop them from the reference — currently both carry the full block.

Trim the Notes section: the MailboxHash, StrippedTextReply, and body-size bullets restate points already made in the MailboxHash section, payload table, and Common Mistakes table.

Add a verification step to Quick Start, e.g., 'Test: Server → Inbound → Send Test in the Postmark dashboard, then confirm your endpoint returns 200', to close the workflow validation gap.

DimensionReasoningScore

Conciseness

The body is mostly lean (tables, bullets, no explanations of concepts Claude already knows), but includes clear tightening opportunities: the full 10-row retry table plus 403 note and retry API are inlined in the body while also duplicated in references/inbound-setup.md, the Notes section restates MailboxHash/StrippedTextReply/body-size points already covered, and the CVE-2026-111497 inflate:false guidance appears twice (code comment plus a long run-on table row) with time-sensitive dates/versions outside any deprecated section. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened', not the 2 anchor's pervasive padding.

3 / 5

Actionability

The Express endpoint is copy-paste ready with real body-parser hardening, destructuring, MailboxHash routing, and the mandatory 200 response; the payload field table, concrete '+ addressing' examples, exact retry intervals, and the specific retry endpoint (PUT /messages/inbound/{messageid}/retry) fully cover the common cases. This matches the 5 anchor's fully-executable, copy-paste-ready standard.

5 / 5

Workflow Clarity

Quick Start gives a clear 4-step sequence (set up domain, set webhook URL, build endpoint, return 200) and the error-handling section documents retry behavior, the 403 abort case, and manual retry — real error-recovery guidance. It falls short of 5 because there is no inline verification checkpoint (e.g., a 'send a test inbound message' step, which exists only in the reference), leaving a minor validation gap at the 4 anchor.

4 / 5

Progressive Disclosure

Structure is good: key payload fields and a basic endpoint are inline, bulk details are split across four real, well-signaled, one-level-deep reference files with descriptive link text. It misses 5 because content placement is inconsistent in places — the retry schedule is fully inlined in the body while the body simultaneously claims 'See references/inbound-setup.md for ... retry schedule' (where the same table is duplicated), a minor organization gap matching the 4 anchor.

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 an explicit 'Use when' trigger clause, concrete workflow capabilities, and a well-defined Postmark inbound niche. Its only weaknesses are minor: a few natural trigger synonyms are absent and the capability list leans on use-case names rather than direct action verbs.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "building reply-by-email, email-to-ticket, document extraction, or any workflow that receives and parses email" — naming the domain plus multiple specific workflows. It falls short of the 5 anchor only because coverage has minor gaps (e.g., attachment handling and inbound rules are only implied via "document extraction"), and it enumerates use cases more than distinct actions.

4 / 5

Completeness

Both halves are explicit and concrete: "Use when processing incoming emails with Postmark inbound webhooks" answers 'when' with concrete triggers, and "building reply-by-email, email-to-ticket, document extraction, or any workflow that receives and parses email" answers 'what'. It matches the 5 anchor's pattern of explicit what-and-when with concrete trigger phrases; the 4 anchor's weaker 'when' ("Use when working with PDF files") is clearly exceeded.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "incoming emails", "Postmark inbound webhooks", "reply-by-email", "email-to-ticket", "document extraction", "receives and parses email" are phrases users would plausibly say. A few natural variants are missing (e.g., "email attachments", "email parsing", "inbound email"), keeping it below the comprehensive-synonym coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

"Postmark inbound webhooks" carves out a clear niche with distinct triggers (reply-by-email, email-to-ticket), and "incoming" disambiguates from outbound-email skills. Minimal conflict risk with other skills, matching the 5 anchor's clear-niche pattern.

5 / 5

Total

18

/

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-inbound/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.