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.
75
65%
Does it follow best practices?
Impact
95%
1.63xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/postmark-automation/SKILL.mdQuality
Discovery
67%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 is strong in specificity and distinctiveness, clearly identifying Postmark-specific email delivery tasks and the integration mechanism. However, it lacks an explicit 'Use when...' clause which caps completeness, and the trigger terms could be broader to capture more natural user language around email sending and transactional email needs.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about sending emails via Postmark, checking email delivery status, or managing Postmark email templates.'
Include additional natural trigger terms like 'transactional email', 'send email', 'email API', or 'email notifications' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'send templated emails', 'manage templates', 'monitor delivery stats and bounces', and 'search tools first for current schemas'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the capabilities listed. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Postmark', 'email delivery', 'templated emails', 'templates', 'bounces', and 'delivery stats'. However, it misses common user variations like 'transactional email', 'email API', 'send email', or 'email notifications'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to be used by users. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'Postmark' as the email platform and 'Rube MCP (Composio)' as the integration method. This is unlikely to conflict with generic email skills or other delivery platform skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with clear workflow sequences and good validation checkpoints, but it suffers from moderate verbosity due to repeated pitfalls across sections and lacks concrete executable examples (actual tool call syntax with sample payloads). The content would benefit from deduplicating repeated guidance and adding at least one fully concrete example of an MCP tool invocation.
Suggestions
Add a concrete, copy-paste-ready example of at least one full tool invocation (e.g., a complete POSTMARK_SEND_BATCH_WITH_TEMPLATES call with sample Messages array and TemplateModel) to improve actionability.
Deduplicate pitfalls—consolidate repeated warnings (batch 500 limit, numeric template IDs, sender verification) into the 'Known Pitfalls' section only, and remove them from individual workflow sections to improve conciseness.
Consider splitting the detailed per-workflow sections or the quick reference table into a separate reference file to improve progressive disclosure for this longer skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some redundancy—pitfalls are repeated across sections (e.g., batch 500 limit, template IDs being numeric, sender verification mentioned multiple times). The 'Known Pitfalls' section rehashes points already covered in individual workflows. Some explanatory text like 'Hard bounces indicate permanent delivery failures' explains concepts Claude already knows. | 2 / 3 |
Actionability | Tool sequences are clearly named and ordered with labeled steps, and key parameters are listed. However, there are no executable code examples or concrete MCP call syntax—the template variable resolution pattern uses pseudocode-style numbered steps rather than actual tool invocation examples with real parameter structures. A concrete example of a POSTMARK_SEND_BATCH_WITH_TEMPLATES call with sample JSON payload would significantly improve actionability. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with labeled steps (Prerequisite/Optional/Required annotations), explicit tool ordering, and validation checkpoints (e.g., validate template before sending, confirm connection is ACTIVE before running workflows). The template variable resolution pattern includes a validate-before-send feedback loop. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a quick reference table, but it's a long monolithic document (~180 lines of content) with no bundle files to offload detailed reference material. The per-workflow pitfalls, common patterns, and known pitfalls sections could be split into separate reference files. The external link to Composio docs is helpful but the skill itself could benefit from better layering. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
74c7031
- 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.