postmark

Use when working with Postmark email platform - routes to specific sub-skills for sending emails, processing inbound email, managing templates, or configuring webhooks.

1.07x

Quality

81%

Does it follow best practices?

Impact

100%

1.07x

Average score across 2 eval scenarios

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

An exemplary routing skill body: token-efficient tables, unambiguous routing to sub-skills (including a thoughtful outbound/inbound webhook disambiguation), and concrete setup details. The only deductions are minor marketing fluff in the intro and the absence of any inline executable API example.

Dimension	Reasoning	Score
Conciseness	The body is dense and efficient — routing maps, token tables, and install commands with almost no explanation of concepts Claude already knows — but minor fluff like 'built for developers, with 15+ years of deliverability expertise' and 'Detect the project language' framing could be trimmed, keeping it just below the every-token-earns-its-place anchor.	4 / 5
Actionability	Guidance is mostly executable: exact auth headers (X-Postmark-Server-Token), per-language install commands, stream values, and a 17-entry routing map. It stops short of fully copy-paste-ready material (no example API request), though that is reasonably delegated to the sub-skills, matching the concrete-with-minor-gaps anchor.	4 / 5
Workflow Clarity	As a router skill with a single unambiguous action, it qualifies for the simple-skill exception: the Quick Routing section maps phrases to sub-skills explicitly, and the outbound-vs-inbound webhook comparison table acts as a disambiguation checkpoint. No destructive or batch operations exist, so the validation cap does not apply.	5 / 5
Progressive Disclosure	No bundle files exist, and the body is a clean overview with well-organized sections that clearly signals one-level-deep pointers to sub-skills and external docs — exactly the structure the simple-skill exception rewards for a routing hub.	5 / 5
	Total	18 / 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 router-style description: third-person, concise, with an explicit 'Use when' clause and four concrete capability areas anchored to a specific platform. Its main weaknesses are the generic when-clause and missing natural trigger synonyms (e.g., transactional email, bounces, SPF/DKIM) that would sharpen discovery.

Suggestions

Extend the when-clause with concrete trigger phrases, e.g. 'Use when the user mentions Postmark, transactional email, bounce handling, or email delivery issues'.

Include the best-practices/deliverability scope (SPF/DKIM/DMARC setup, compliance, list hygiene) so the description's coverage matches all five sub-skills.

Add common synonyms such as 'transactional email' and 'email API' to broaden natural trigger coverage without adding length.

Dimension	Reasoning	Score
Specificity	The description lists four concrete capability areas ("sending emails, processing inbound email, managing templates, or configuring webhooks"), matching the several-specific-actions anchor, but coverage has minor gaps — the best-practices/deliverability sub-skill and compliance work are omitted, and the actions remain at the routing level rather than the operations themselves.	4 / 5
Completeness	It explicitly answers both what ("routes to specific sub-skills for...") and when ("Use when working with Postmark email platform"), matching the both-present-but-when-could-be-more-specific anchor; it is not a 5 because the when-clause names no concrete trigger phrases beyond the platform itself.	4 / 5
Trigger Term Quality	Natural phrases users would say are present ("sending emails", "inbound email", "templates", "webhooks"), giving good keyword coverage, but common variations like "transactional email", "bounce", "delivery", or "SPF/DKIM" are missing, so it falls short of the comprehensive-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	"Postmark email platform" establishes a clear niche with distinct triggers tied to a specific vendor, and the enumerated sub-skill scopes further disambiguate it, so conflict risk with other skills is minimal.	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: 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.