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.71x

Quality

80%

Does it follow best practices?

Impact

96%

1.71x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

A well-structured, highly actionable skill body: copy-paste endpoint code, precise field/mistake tables, and a clean four-file reference split that keeps the main file focused. The main improvements are removing duplication (retry table, Notes vs. Common Mistakes, How It Works vs. Quick Start) and surfacing a webhook testing step in the main workflow.

Suggestions

Replace the inline 10-row retry table with a one-line summary (e.g., 'up to 10 retries over ~10.5 hours; 403 stops retries immediately') and let references/inbound-setup.md carry the full schedule, since that file already duplicates it.

Add a 'Test your webhook' step to Quick Start (e.g., 'Server → Inbound → Send Test in the dashboard') so the workflow has an explicit validation checkpoint in the main body.

Merge the Notes section into Common Mistakes and consolidate 'How It Works' with 'Quick Start' to remove repeated statements about returning 200, StrippedTextReply, and body size limits.

Dimension	Reasoning	Score
Conciseness	The body is efficient — lean tables, no explanations of concepts Claude already knows — but 'How It Works' and 'Quick Start' overlap, the Notes section repeats rows from Common Mistakes, and the full 10-row retry table duplicates the 'Webhook Retries' section in references/inbound-setup.md verbatim. These are minor trims, matching the level-4 rather than level-5 anchor.	4 / 5
Actionability	Fully executable copy-paste Express endpoint code with a concrete MailboxHash parsing pattern, plus specific commands and values throughout (`50mb` body limit, `PUT /messages/inbound/{messageid}/retry`, inline MailboxHash routing examples) — matches the level-5 anchor for covering the common cases.	5 / 5
Workflow Clarity	Quick Start gives a clear 4-step sequence, and the Error Handling section documents failure behavior and recovery (retry schedule, 403 stops retries, manual retry API, activity-page monitoring). It falls short of level 5 because the body lacks an explicit 'test your webhook' validation checkpoint — testing appears only in references/inbound-setup.md.	4 / 5
Progressive Disclosure	Good structure: an overview body with four well-signaled, one-level-deep references (inbound-setup.md, payload-structure.md, handler-examples.md, inbound-api.md — all verified to exist) with descriptive link text. Minor organization gap: the inline 10-row retry table and 403 note duplicate the reference's Webhook Retries section, so content placement isn't perfectly split.	4 / 5
	Total	17 / 20 Passed

Description

78%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, trigger-first description with an explicit 'Use when' clause, a clearly named niche, and several concrete use cases. Its main weakness is that the capability ('what') is implied by use-case labels rather than stated as a direct third-person action, and a few natural trigger synonyms are absent.

Suggestions

Lead with a third-person capability statement (e.g., "Processes incoming email via Postmark inbound webhooks: parses payloads, threads replies, and extracts attachments.") before the 'Use when' clause so the 'what' is explicit.

Add a few natural trigger synonyms such as "inbound email", "email attachments", or "email forwarding" to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Postmark inbound webhooks") and several concrete workflows ("reply-by-email, email-to-ticket, document extraction") plus the action "receives and parses email", but these are use-case labels rather than a comprehensive list of concrete operations, so it falls just below the level-5 anchor.	4 / 5
Completeness	The 'when' is explicit and strong ("Use when processing incoming emails with Postmark inbound webhooks..."), but the 'what' is only implied through the use-case list — there is no standalone third-person capability statement — so it does not clearly and explicitly answer both at level 5.	4 / 5
Trigger Term Quality	Good natural-term coverage: "incoming emails", "inbound webhooks", "reply-by-email", "email-to-ticket", "document extraction", "parses email". A few common variations are missing (e.g., "inbound email", "email attachments", "email forwarding"), keeping it below the comprehensive level-5 anchor.	4 / 5
Distinctiveness Conflict Risk	Clear niche anchored to Postmark inbound webhooks with distinct, specific triggers ("reply-by-email", "email-to-ticket", "document extraction"); minimal risk of triggering for an unrelated skill.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 269553e

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.