postmark
Skill46 starsChanged 55 days agoMITView on GitHub
Use when working with Postmark email platform - routes to specific sub-skills for sending emails, processing inbound email, managing templates, or configuring webhooks.
- Installs packages
2 other projects use a version of this.
Adopted by
Most recently taken up by
- jackson2w/claude-code-skillstheir own version, first seen Nov 3, 2026
- timcase/agent-skillstheir own version, first seen Jul 19, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- jackson2w/claude-code-skills★ 1same name
- timcase/agent-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- postmark-email-best-practicesSkill
- postmark-inboundSkill
- postmark-send-emailSkill
- postmark-templatesSkill
- postmark-webhooksSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 89
Never mix transactional and broadcast email in the same stream — it damages deliverability.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Postmark Skills
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.
Sub-Skills
| 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 |
Outbound and inbound webhooks are different systems
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.
Quick Routing
- "Send an email" →
postmark-send-email - "Send a batch of emails" →
postmark-send-email - "Send using a template" →
postmark-send-email(template section) orpostmark-templates(to create/manage templates) - "Handle incoming email" →
postmark-inbound - "Process inbound webhooks" →
postmark-inbound - "Create an email template" →
postmark-templates - "Track deliveries/bounces/opens" →
postmark-webhooks - "Set up bounce handling" →
postmark-webhooks - "Verify a webhook endpoint" / "my webhook is unverified" →
postmark-webhooks - "Webhook statistics / failure rate / why is my webhook paused" →
postmark-webhooks - "Webhook retries" →
postmark-webhooks(outbound events) orpostmark-inbound(inbound email) - "Set up SPF/DKIM/DMARC" →
postmark-email-best-practices - "Email compliance / GDPR / CAN-SPAM" →
postmark-email-best-practices - "Domain warm-up" →
postmark-email-best-practices - "List hygiene / suppression management" →
postmark-email-best-practices - "Design a transactional email" →
postmark-email-best-practices - "Test email safely" →
postmark-email-best-practices
Common Setup
Authentication
Postmark 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.
SDK Installation
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 |
Message Streams
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.
Resources
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.