postmark-webhooks
Use when setting up Postmark webhooks for tracking email delivery, bounces, opens, clicks, spam complaints, or subscription changes — includes webhook configuration, payload handling, and security.
87
81%
Does it follow best practices?
Impact
99%
1.10xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 skill description that clearly communicates when to use it via an explicit 'Use when...' clause and covers relevant trigger terms for Postmark webhook scenarios. Its main weakness is that the capabilities are described more as topic areas (configuration, payload handling, security) rather than concrete actions (e.g., 'configure webhook endpoints', 'validate webhook signatures', 'parse bounce payloads'). Overall it performs well for skill selection purposes.
Suggestions
Replace topic-level phrases like 'webhook configuration, payload handling, and security' with concrete actions such as 'configure webhook endpoints, parse event payloads, validate webhook signatures' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Postmark webhooks) and lists several event types (delivery, bounces, opens, clicks, spam complaints, subscription changes) plus high-level areas (webhook configuration, payload handling, security), but doesn't list multiple concrete actions with specificity — it's more of a topic enumeration than action-oriented. | 2 / 3 |
Completeness | The description explicitly answers both 'what' (setting up Postmark webhooks for tracking various email events, webhook configuration, payload handling, security) and 'when' (starts with 'Use when...'), providing clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords a user would say: 'Postmark', 'webhooks', 'email delivery', 'bounces', 'opens', 'clicks', 'spam complaints', 'subscription changes', 'webhook configuration', 'payload handling', and 'security'. These cover a wide range of natural user queries. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Postmark webhooks, a particular email service provider's webhook system. This is a clear niche that is unlikely to conflict with generic email skills or other webhook-related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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 strong actionability and excellent progressive disclosure. The main weaknesses are minor verbosity (some repeated guidance about responding with 200, and explanatory content Claude doesn't need) and a lack of explicit validation/verification steps in the workflow. The code examples are executable and the reference structure is clean.
Suggestions
Add a validation step to the Quick Start workflow, such as using Postmark's webhook test feature or sending a test email to verify the endpoint receives events correctly.
Remove redundant mentions of 'respond 200 immediately' — it appears in Quick Start, the handler code comment, Common Mistakes, and Notes. State it once prominently.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured but includes some information Claude would already know (e.g., explaining what each event type means in the overview table's 'Common Use' column). The Notes section has some redundancy with earlier content (e.g., 'respond 200 immediately' is stated three times across the document). The content is reasonably efficient but could be tightened. | 2 / 3 |
Actionability | Provides fully executable code examples in both JavaScript and cURL for creating webhooks, a complete event routing handler, and specific API endpoints. The bounce type table with concrete action items and the common mistakes table with specific fixes are highly actionable. | 3 / 3 |
Workflow Clarity | The Quick Start provides a clear 5-step sequence, and the event handling flow is well-demonstrated. However, there are no explicit validation checkpoints — for example, no step to verify the webhook was created successfully, no guidance on testing the endpoint before going live, and no feedback loop for handling webhook delivery failures on the receiving end. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to payload-examples.md, handler-examples.md, security.md, bounce-management.md, and webhook-setup.md. The main file contains enough to get started while pointing to detailed references for deeper topics. | 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.