postmark
Use when working with Postmark email platform - routes to specific sub-skills for sending emails, processing inbound email, managing templates, or configuring webhooks.
86
80%
Does it follow best practices?
Impact
98%
1.24xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./SKILL.mdQuality
Discovery
89%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 is a solid routing-level skill description that clearly identifies when it should be used (Postmark platform) and what sub-capabilities it covers. Its main weakness is that it describes itself as a router to sub-skills rather than listing concrete actions, making the specificity somewhat abstract. The trigger terms and completeness are strong, and the Postmark platform name makes it highly distinctive.
Suggestions
Consider adding a few more concrete action examples beyond category names, e.g., 'send transactional emails via Postmark API, parse inbound email webhooks, create and edit email templates, set up bounce/delivery webhooks'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Postmark email platform) and lists some actions (sending emails, processing inbound email, managing templates, configuring webhooks), but these are more like categories than concrete specific actions. It mentions 'routes to specific sub-skills' which is a meta-description rather than describing concrete capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (routes to sub-skills for sending emails, processing inbound email, managing templates, configuring webhooks) and 'when' (explicitly starts with 'Use when working with Postmark email platform'). The trigger guidance is explicit. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Postmark', 'sending emails', 'inbound email', 'templates', 'webhooks'. These are terms a user would naturally use when needing this skill. Good coverage of the platform's key feature areas. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct due to the specific platform name 'Postmark' and the combination of email-specific sub-capabilities. Unlikely to conflict with generic email skills or other platform-specific skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%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 routing/overview skill that effectively directs users to appropriate sub-skills. Its main strengths are the clear routing table, progressive disclosure to sub-skills, and useful common setup information. Weaknesses include some marketing language, minor redundancy between the Sub-Skills table and Quick Routing section, and lack of executable code examples in the common setup.
Suggestions
Remove the marketing language ('15+ years of deliverability expertise') — Claude doesn't need to be sold on the platform.
Add a minimal executable code example in Common Setup showing client initialization (e.g., Node.js or Python) to make the authentication section more actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient as a routing/overview skill, but includes some unnecessary explanation (e.g., '15+ years of deliverability expertise' is marketing fluff, and the Message Streams explanation could be more terse). The Quick Routing section is somewhat redundant with the Sub-Skills table. | 2 / 3 |
Actionability | Provides concrete SDK install commands and authentication header details, which is useful. However, as a routing skill it mostly points elsewhere rather than providing executable guidance itself. The Common Setup section has actionable tables but no code examples showing actual API usage. | 2 / 3 |
Workflow Clarity | For a routing/overview skill, the workflow is clear: identify the task from the Quick Routing list, go to the appropriate sub-skill. The Common Setup section provides a clear sequence (get token → install SDK → understand streams). No multi-step destructive operations exist here, so no validation checkpoints are needed. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — provides a concise overview with a well-organized routing table and quick routing guide, then clearly points to five specific sub-skills for detailed content. References are one level deep and clearly signaled with consistent naming. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ActiveCampaign/postmark-skills
- Commit
73ea6bf
- 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.