postmark-automation

Automate Postmark email delivery tasks via Rube MCP (Composio): send templated emails, manage templates, monitor delivery stats and bounces. Always search tools first for current schemas.

1.63x

Quality

61%

Does it follow best practices?

Impact

95%

1.63x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/postmark-automation/SKILL.md

Quality

Content

57%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 well-structured and actionable with concrete tool sequences, but it is held back by redundant pitfalls, missing validation feedback loops on batch/destructive operations, and all reference material inlined rather than progressively disclosed.

Suggestions

Add explicit validation checkpoints to the batch-send and server-edit workflows (e.g., require POSTMARK_VALIDATE_TEMPLATE before batch send, and verify the response/ETag after POSTMARK_EDIT_SERVER) to lift the workflow_clarity cap.

Move the Quick Reference table and detailed per-tool parameter lists into a references/ file (e.g. TOOLS.md) and link to it from the body to improve progressive disclosure and reduce duplication.

Trim the 'Known Pitfalls' section to only items not already stated in the per-workflow Pitfalls blocks to remove redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but the 'Known Pitfalls' section repeats rate-limit, batch-500, sender-signature, and numeric-template-id points already covered per-workflow, and the Quick Reference table re-lists tools, so it could be tightened.	3 / 5
Actionability	Names exact MCP tool slugs (POSTMARK_*), key parameters, and concrete pitfalls per workflow; as an instruction-only skill the guidance is actionable, with only the minor gap that live schemas are deferred to RUBE_SEARCH_TOOLS.	4 / 5
Workflow Clarity	Numbered tool sequences with [Required]/[Optional]/[Prerequisite] tags and an ACTIVE-connection checkpoint are clear, but batch send (up to 500) and server edits lack validation/feedback loops — template validation is marked [Optional] and there is no post-send verification — so the destructive/batch cap holds at 3.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but the entire Quick Reference table and detailed parameter docs are inlined in a single 185-line file with no bundle references to deeper material, fitting the 'content that should be separate is inline' anchor.	3 / 5
	Total	13 / 20 Passed

Description

66%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 clearly states capabilities with good trigger keywords and a distinct Postmark niche, but it lacks an explicit "Use when..." usage trigger, capping completeness. It is solid but one clause short of excellent.

Suggestions

Add an explicit 'Use when...' clause naming concrete user triggers, e.g. 'Use when sending or debugging Postmark transactional email, managing templates, or investigating bounces.'

Drop or de-emphasize the operational 'Always search tools first' line from the description; it belongs in the body, not the trigger statement.

Consider adding 'spam complaints' and 'server settings' to round out the capability list for more comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "send templated emails, manage templates, monitor delivery stats and bounces" — but omits server config and spam complaints, leaving minor coverage gaps rather than comprehensive coverage.	4 / 5
Completeness	Has a clear "what" but no "Use when..." trigger clause — the closing "Always search tools first for current schemas" is operational guidance, not usage triggers, so completeness is capped at 3 per the rubric.	3 / 5
Trigger Term Quality	Good natural-keyword coverage (Postmark, email, templated emails, delivery stats, bounces, templates) with only a few synonyms missing (e.g., "transactional email"), though "Rube MCP (Composio)" is technical jargon.	4 / 5
Distinctiveness Conflict Risk	"Postmark email delivery" carves a clear niche with minimal conflict risk, though the generic "email" framing leaves minor overlap with other email-sending skills.	4 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/postmark-automation/SKILL.md
Commit: a9fa86d

Reviewed: about 19 hours 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.