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
Secure webhook endpoint with correct auth and immediate 200 response
Immediate 200 response
100%
100%
RecordType routing
100%
100%
401 for auth failure (not 403)
100%
100%
No 403 on auth failure
100%
100%
Constant-time comparison
100%
100%
MessageID deduplication
100%
100%
Partial data guards
25%
87%
SpamComplaint suppression
0%
100%
SubscriptionChange SuppressSending check
33%
100%
Async processing note
100%
100%
Webhook registration with stream, triggers, and security configuration
postmark npm package
100%
100%
ServerClient instantiation
100%
100%
MessageStream specified
100%
100%
Separate streams handled
100%
100%
HttpAuth used for security
100%
100%
HTTPS endpoint URL
100%
100%
PostFirstOpenOnly configured
100%
100%
IncludeContent on Bounce
100%
100%
IncludeContent on SpamComplaint
100%
100%
Token from environment
100%
100%
Secret from environment
100%
100%
Bounce event handling and suppression management
HardBounce permanent removal
100%
100%
SoftBounce not removed
100%
100%
SpamComplaint immediate suppress
80%
100%
No hard bounce reactivation
100%
100%
Inactive field checked
25%
100%
No spam/hard suppression removal
100%
80%
Metadata correlation
100%
100%
Bounce type differentiation
100%
100%
Postmark Bounces API used
100%
100%
Suppression API used
100%
100%
Partial data guards
100%
100%
73ea6bf
Table of Contents
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.