Use when working with Postmark email platform - routes to specific sub-skills for sending emails, processing inbound email, managing templates, or configuring webhooks.
80
81%
Does it follow best practices?
Impact
100%
1.07xAverage score across 2 eval scenarios
Low
Low-risk findings worth noting
Postmark is a transactional email platform built for developers, with 15+ years of deliverability expertise. These skills teach AI agents how to use the Postmark API effectively.
| Feature | Skill | Use When |
|---|---|---|
| Sending emails | postmark-send-email | Sending transactional or broadcast emails — single, batch, bulk, or with templates |
| Inbound processing | postmark-inbound | Processing incoming emails via webhooks, building reply-by-email, email-to-ticket, or document extraction |
| Template management | postmark-templates | Creating, editing, or sending with Postmark's server-side Handlebars templates and layouts |
| Webhooks | postmark-webhooks | Setting up outbound webhooks for delivery, bounce, open, click, spam complaint, and subscription change events — including endpoint verification, per-webhook statistics, and retry behavior |
| Best practices | postmark-email-best-practices | Deliverability setup, compliance (CAN-SPAM/GDPR/CASL), email design, list management, testing, and sending reliability |
postmark-webhooks covers outbound event webhooks; postmark-inbound covers inbound email webhooks. They run on separate infrastructure and have different retry schedules — do not apply one to the other:
Outbound webhooks (postmark-webhooks) | Inbound webhooks (postmark-inbound) | |
|---|---|---|
| Retries | Up to 9 retries over ~72 minutes (3 standard + 6 backoff) | Up to 10 retries over ~10.5 hours |
| Retried on | 5xx, 408, 429, network timeouts only — every other 4xx is permanent | Any non-200 response |
Endpoint verification and per-webhook statistics are outbound features — see postmark-webhooks.
postmark-send-emailpostmark-send-emailpostmark-send-email (template section) or postmark-templates (to create/manage templates)postmark-inboundpostmark-inboundpostmark-templatespostmark-webhookspostmark-webhookspostmark-webhookspostmark-webhookspostmark-webhooks (outbound events) or postmark-inbound (inbound email)postmark-email-best-practicespostmark-email-best-practicespostmark-email-best-practicespostmark-email-best-practicespostmark-email-best-practicespostmark-email-best-practicesPostmark uses two types of API tokens:
| Token | Header | Scope |
|---|---|---|
| Server Token | X-Postmark-Server-Token | Sending emails, templates, bounces, webhooks, message streams |
| Account Token | X-Postmark-Account-Token | Managing servers, domains, sender signatures |
Get your Server API Token from Postmark Servers.
Detect the project language and install the appropriate SDK:
| File | Language | Install Command |
|---|---|---|
package.json | Node.js / TypeScript | npm install postmark |
requirements.txt / pyproject.toml | Python | pip install postmarker |
Gemfile | Ruby | gem install postmark |
composer.json | PHP | composer require wildbit/postmark-php |
*.csproj / *.sln | .NET | dotnet add package Postmark |
Postmark separates email by intent into Message Streams:
| Stream | Value | Purpose |
|---|---|---|
| Transactional | outbound | 1:1 triggered emails (welcome, password reset, receipts) — default |
| Broadcast | broadcast | Marketing, newsletters, announcements |
Never mix transactional and broadcast email in the same stream — it damages deliverability.
SKILL.md
269553e
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.