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.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill postmark-automation71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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.
This description effectively communicates specific capabilities for Postmark email automation and is highly distinctive due to naming the specific service and integration. However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know exactly when to select this skill, and could benefit from more natural trigger terms users might actually say.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions Postmark, transactional emails, email templates, or delivery tracking.'
Include additional natural trigger terms like 'transactional email', 'email API', 'email notifications', or 'delivery reports' that users commonly say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'send templated emails, manage templates, monitor delivery stats and bounces.' Also includes the operational guidance to 'search tools first for current schemas.' | 3 / 3 |
Completeness | Clearly answers 'what' (send templated emails, manage templates, monitor stats/bounces) but lacks an explicit 'Use when...' clause. The 'when' is only implied through the capability listing. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Postmark', 'email delivery', 'templated emails', 'bounces', but missing common variations users might say like 'transactional email', 'email API', or 'delivery notifications'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Postmark' and 'Rube MCP (Composio)' as clear identifiers. Unlikely to conflict with generic email skills due to the specific service and integration mentioned. | 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 skill provides comprehensive coverage of Postmark operations with well-structured workflows and clear sequencing. However, it lacks concrete executable examples (showing actual tool call syntax) and could be more concise by eliminating redundancy between the workflow sections and the Quick Reference table. The validation checkpoints and pitfall documentation are strengths.
Suggestions
Add concrete, executable examples showing actual tool invocation syntax with realistic parameters (e.g., a complete POSTMARK_SEND_BATCH_WITH_TEMPLATES call with sample Messages array)
Consolidate the 'Known Pitfalls' section with workflow-specific pitfalls to reduce redundancy
Consider splitting detailed workflow documentation into separate files (e.g., TEMPLATES.md, MONITORING.md) with SKILL.md as a concise overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the Quick Reference table duplicates information from the workflows, and some pitfalls are repeated across sections. The content could be tightened by consolidating common pitfalls. | 2 / 3 |
Actionability | Provides tool names and parameter lists but lacks executable code examples. The 'Template Variable Resolution' pattern shows pseudocode-style steps rather than actual API calls with concrete syntax. No copy-paste ready examples of actual tool invocations. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with labeled steps (Required/Optional/Prerequisite), explicit tool ordering, and validation checkpoints (e.g., validate template before sending, confirm connection is ACTIVE before running workflows). The setup section includes a clear verification step. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document with no references to external files for detailed content. The Quick Reference table is helpful but the document could benefit from splitting detailed workflow documentation into separate files. | 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 | |
- 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.