30f9b9a729
* feat: v2.0 skill renames and CRO consolidation BREAKING CHANGE: Users must reinstall skills after this update. ## Skill Renames (16) - ab-test-setup → ab-testing - analytics-tracking → analytics - aso-audit → aso - competitor-alternatives → competitors - email-sequence → emails - free-tool-strategy → free-tools - launch-strategy → launch - onboarding-cro → onboarding - paywall-upgrade-cro → paywalls - popup-cro → popups - pricing-strategy → pricing - product-marketing-context → product-marketing - referral-program → referrals - schema-markup → schema - signup-flow-cro → signup - social-content → social ## Consolidations (1) - page-cro + form-cro → cro (form content in references/form.md) ## Why 2.0? - Shorter, cleaner skill names - Consistent naming (no -strategy, -setup, -cro suffixes) - All cross-references updated across 100+ files Total skills: 40 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(v2.0): update evals for renamed skills, fix validate script, clear warnings - Update 32 evals.json files to reference new skill names (page-cro → cro, product-marketing-context → product-marketing, etc.) — these were missed in the initial v2.0 rename pass since only SKILL.md and marketplace.json were updated. - Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk so frontmatter extraction works on macOS. - Move Copy Editing Checklist (56 lines) to references/checklist.md to bring copy-editing SKILL.md under the 500-line limit (508 → 457). - Add "see X" pointers to marketing-psychology description for skill discovery (cro, pricing, copywriting). - Update skill-request.yml issue template placeholder (page-cro → cro). All 40 skills now pass validation with zero warnings. * fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md Adds 48 new eval cases (6 per skill) for skills that previously had no evals: aso, co-marketing, community-marketing, competitor-profiling, directory-submissions, image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases). Strips leftover frontmatter from skills/cro/references/form.md — it was inherited from the old form-cro SKILL.md before consolidation. Reference files don't need frontmatter. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): rename paid-ads → ads One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates the skill directory, SKILL.md frontmatter, evals.json, README skill table, the v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in related skills (ad-creative, aso, competitor-profiling, customer-research, lead-magnets, marketing-ideas) plus the tools/integrations guides. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside each SKILL.md was still on 1.x. That mismatch would have caused the update-check flow to perpetually report 'update available' since it compares VERSIONS.md against local SKILL.md metadata versions. Caught by codex review (P1). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): add legacy product-marketing-context.md filename fallback Before this fix, users upgrading from v1.x who had a `product-marketing-context.md` file would lose automatic context loading — every skill only checked the new `product-marketing.md` filename. Now all 40 skills also accept the legacy filename (in either `.agents/` or `.claude/`), and the README migration command covers both legacy and current filenames. Caught by codex review (P1 + P2). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): re-sort README skills table alphabetically, fix ads box width The skills table had a few entries out of alphabetical order from the renames (co-marketing was after cold-email, ads was at the renamed position). Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the ASCII flow diagram to keep the box width consistent. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array README upgrade guide now includes: - A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so users don't end up with both old and new folders side-by-side after upgrading - The full v1 to v2 rename map for reference - Existing product-marketing-context.md migration steps (preserved) sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json -- Claude Code's plugin schema discovers skills via the `skills/` directory, and the explicit array was failing validation. The script now refreshes the description count and strips the stale array if present. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
5.3 KiB
5.3 KiB
Postmark
Transactional email delivery service with fast delivery, templates, bounce management, and detailed analytics.
Capabilities
| Integration | Available | Notes |
|---|---|---|
| API | ✓ | REST API for email sending, templates, bounces, stats |
| MCP | - | Not available |
| CLI | ✓ | postmark.js |
| SDK | ✓ | Node.js, Ruby, Python, PHP, Java, .NET, Go |
Authentication
- Type: Server Token (or Account Token for account-level ops)
- Header:
X-Postmark-Server-Token: {server_token}(server-level) - Header:
X-Postmark-Account-Token: {account_token}(account-level) - Get key: API Tokens tab at https://account.postmarkapp.com/servers
- Note: Server tokens are per-server; account tokens apply across all servers
Common Agent Operations
Send single email
POST https://api.postmarkapp.com/email
{
"From": "sender@example.com",
"To": "recipient@example.com",
"Subject": "Welcome!",
"HtmlBody": "<html><body><p>Hello!</p></body></html>",
"TextBody": "Hello!",
"MessageStream": "outbound",
"TrackOpens": true,
"TrackLinks": "HtmlAndText"
}
Send with template
POST https://api.postmarkapp.com/email/withTemplate
{
"From": "sender@example.com",
"To": "recipient@example.com",
"TemplateId": 12345,
"TemplateModel": {
"name": "Jane",
"action_url": "https://example.com/verify"
},
"MessageStream": "outbound"
}
Send batch emails
POST https://api.postmarkapp.com/email/batch
[
{
"From": "sender@example.com",
"To": "user1@example.com",
"Subject": "Notification",
"TextBody": "Hello user 1"
},
{
"From": "sender@example.com",
"To": "user2@example.com",
"Subject": "Notification",
"TextBody": "Hello user 2"
}
]
List templates
GET https://api.postmarkapp.com/templates?Count=100&Offset=0
Get template
GET https://api.postmarkapp.com/templates/{templateIdOrAlias}
Create template
POST https://api.postmarkapp.com/templates
{
"Name": "Welcome Email",
"Alias": "welcome",
"Subject": "Welcome {{name}}!",
"HtmlBody": "<html><body><p>Hello {{name}}</p></body></html>",
"TextBody": "Hello {{name}}"
}
Get delivery stats
GET https://api.postmarkapp.com/deliverystats
List bounces
GET https://api.postmarkapp.com/bounces?count=50&offset=0&type=HardBounce
Activate bounce (reactivate recipient)
PUT https://api.postmarkapp.com/bounces/{bounceId}/activate
Search outbound messages
GET https://api.postmarkapp.com/messages/outbound?count=50&offset=0&recipient=user@example.com
Get outbound stats overview
GET https://api.postmarkapp.com/stats/outbound?fromdate=2025-01-01&todate=2025-01-31
Get open stats
GET https://api.postmarkapp.com/stats/outbound/opens?fromdate=2025-01-01&todate=2025-01-31
Get click stats
GET https://api.postmarkapp.com/stats/outbound/clicks?fromdate=2025-01-01&todate=2025-01-31
Get server info
GET https://api.postmarkapp.com/server
List suppressions
GET https://api.postmarkapp.com/message-streams/outbound/suppressions/dump
Create suppression
POST https://api.postmarkapp.com/message-streams/outbound/suppressions
{
"Suppressions": [
{ "EmailAddress": "user@example.com" }
]
}
API Pattern
Postmark uses simple REST endpoints with PascalCase field names in request/response bodies. Authentication is via custom headers rather than Authorization. Pagination uses Count and Offset parameters. Email sending is synchronous with immediate delivery confirmation.
Key Metrics
Delivery Metrics
Sent- Total emails sentBounced- Bounce count by type (hard, soft, transient)SpamComplaints- Spam complaint countOpens- Open count and unique opensClicks- Click count and unique clicks
Bounce Types
HardBounce- Permanent delivery failureSoftBounce- Temporary delivery failureTransient- Temporary issue (retry)SpamNotification- Marked as spam
Message Fields
MessageID- Unique message identifierSubmittedAt- Submission timestampStatus- Delivery statusRecipients- Recipient list
Parameters
Email Parameters
From- Sender address (must be verified)To- Recipient (comma-separated for multiple)Subject- Email subjectHtmlBody/TextBody- Email contentMessageStream- outbound (transactional) or broadcastTrackOpens- Enable open tracking (boolean)TrackLinks- None, HtmlAndText, HtmlOnly, TextOnlyTag- Custom tag for categorization
Stats Parameters
fromdate- Start date (YYYY-MM-DD)todate- End date (YYYY-MM-DD)tag- Filter by tag
When to Use
- Transactional emails (password resets, order confirmations, notifications)
- Template-based email sending with dynamic variables
- Monitoring email deliverability and bounce rates
- Tracking email engagement (opens, clicks)
- Managing email suppressions and bounces
- High-reliability email delivery with fast performance
Rate Limits
- 500 messages per batch request
- 10 MB max per single message (including attachments)
- 50 MB max per batch request
- API rate limits vary by plan
Relevant Skills
- emails
- transactional-email
- email-deliverability
- onboarding-email