postmark-send-email

Use when sending transactional or broadcast emails through Postmark — single sends, batch (up to 500), bulk, or template-based emails with support for attachments, tracking, and message streams.

2.15x

Quality

89%

Does it follow best practices?

Impact

99%

2.15x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 API skill: executable code, dense decision tables, real feedback loops for batch/error handling, and a clean one-level reference bundle that all exists. The main weaknesses are minor — redundancy between the Notes section, earlier sections, and the error-handling reference, plus no single unified send-and-validate workflow sequence.

Suggestions

Trim the Notes section: three of its bullets (token env var, 50-recipient cap, POSTMARK_API_TEST) duplicate the Authentication, Single Email, and Testing sections verbatim.

Replace the full inline HTTP error-code table with the few most common codes and defer the rest to references/error-handling.md, which already contains the same table — this also removes the duplication.

Add one short end-to-end ordered workflow (setup → choose stream/endpoint → send → verify ErrorCode/response → handle retries) so the existing validation guidance forms a single explicit sequence.

Dimension	Reasoning	Score
Conciseness	The body is dense and table-driven with executable snippets and almost no explanation of concepts Claude already knows, but the Notes section repeats earlier content ("Store API key in POSTMARK_SERVER_TOKEN", "Maximum 50 recipients", POSTMARK_API_TEST usage all appear in Authentication, the To parameter, and Testing respectively) and the inline error table duplicates references/error-handling.md. Not 5: these redundancies could be trimmed; not 3: verbosity is minor, not 'some unnecessary explanation' throughout.	4 / 5
Actionability	Every section gives copy-paste-ready material: complete Node.js examples for single, batch, and template sends, a working retry function with exponential backoff, exact endpoints, the auth header, parameter tables, and concrete attachment JSON. Common cases are covered inline with per-language variants delegated to references.	5 / 5
Workflow Clarity	A Quick Start sequence (token → verify sender → install SDK → choose endpoint), a decision matrix for endpoint choice, and strong error-recovery feedback loops (per-result ErrorCode checks for batch, retry-with-backoff only for 429/500, explicit 'do not retry' guidance) satisfy the batch-operation validation bar. Not 5: there is no single end-to-end sequence from setup through a verified send — validation guidance is distributed across sections rather than one explicit ordered workflow with checkpoints.	4 / 5
Progressive Disclosure	Each major area keeps concise key content inline and clearly signals a one-level-deep reference with a description of its contents ("See [references/batch-email-examples.md] ... for chunking patterns, attachments, and Python/Ruby/cURL examples"); all six referenced files exist and none nest further. Matches the anchor-5 pattern of a clear overview with well-signaled, appropriately split references.	5 / 5
	Total	18 / 20 Passed

Description

92%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: explicit 'Use when' trigger, comprehensive enumeration of concrete capabilities, third-person voice, and clear Postmark-specific niche. The only gap is missing a few natural synonyms (e.g., newsletter, notifications) that users might phrase differently.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities — "single sends, batch (up to 500), bulk, or template-based emails with support for attachments, tracking, and message streams" — comprehensively covering the Postmark sending surface. Not 4: coverage of send modes plus features (attachments, tracking, streams) is complete rather than having minor gaps.	5 / 5
Completeness	It opens with an explicit trigger clause ("Use when sending transactional or broadcast emails through Postmark") and clearly states what it does by enumerating the four send modes and feature support. Both 'what' and 'when' are explicit with concrete trigger phrases, matching the anchor-5 example structure.	5 / 5
Trigger Term Quality	Natural phrases a user would say are present — "sending transactional or broadcast emails", "batch", "bulk", "template-based emails", "through Postmark" — but common synonyms like "newsletter", "mail", or "notifications" are absent. Not 5: keyword coverage is good but not comprehensive with synonyms; not 3: it goes well beyond a single generic keyword.	4 / 5
Distinctiveness Conflict Risk	The Postmark branding plus specific modes (batch up to 500, message streams, broadcast) carve out a clear niche with distinct triggers and minimal conflict risk with generic email skills. Only trivially overlaps with sibling Postmark skills, which is below the 'minor overlap' bar of 4.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: ActiveCampaign/postmark-skills
Path: postmark-send-email/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.