Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/finsilabs/awesome-ecommerce-skillsnpx agentmods add skills/finsilabs/awesome-ecommerce-skills/email-service-integrationWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/finsilabs/awesome-ecommerce-skills/email-service-integration)<a href="https://agentmods.dev/skills/finsilabs/awesome-ecommerce-skills/email-service-integration"><img src="https://agentmods.dev/badge/skills/finsilabs/awesome-ecommerce-skills/email-service-integration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/finsilabs/awesome-ecommerce-skills/email-service-integration"><img src="https://agentmods.dev/badge/skills/finsilabs/awesome-ecommerce-skills/email-service-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.02730 |
| Opus 5 | $0.00016 | $0.01365 |
| Sonnet 5 | $0.00006 | $0.00546 |
| Haiku 4.5 | $0.00003 | $0.00273 |
Grade A, and why
email-service-integration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Service Integration
Overview
Transactional emails — order confirmations, shipping notifications, password resets, and account alerts — are critical customer touchpoints that must arrive instantly and reliably. This skill covers setting up email delivery on each platform and integrating dedicated transactional services (SendGrid, Amazon SES, Postmark) with SPF/DKIM/DMARC DNS records for deliverability, reusable templates, and bounce/complaint handling.
When to Use This Skill
- When setting up transactional email for a new e-commerce store
- When emails are landing in spam due to missing SPF, DKIM, or DMARC records
- When migrating from a platform's built-in email to a dedicated transactional service
- When building custom email templates that match your brand identity
- When tracking email delivery, open rates, and bounces for transactional emails
Core Instructions
Step 1: Determine your platform and recommended approach
| Platform | Default Email | Recommended Upgrade |
|---|---|---|
| Shopify | Shopify Email (built-in, branded templates, free up to 10K/month) | Customize templates in Settings → Notifications; for high volume or advanced flows use Klaviyo or Omnisend |
| WooCommerce | WordPress sends via your hosting server (poor deliverability) | Install FluentSMTP (free) to route via SendGrid/SES/Postmark; use WooCommerce Email Customizer ($49) for branded templates |
| BigCommerce | BigCommerce built-in transactional email (basic templates) | Customize templates in Marketing → Transactional Emails; for advanced templates use Klaviyo BigCommerce integration |
| Custom / Headless | None — you build it | Integrate SendGrid, Postmark, or Amazon SES directly; build templates with React Email; see implementation below |
Step 2: Platform-specific email setup
Shopify
Customize built-in transactional emails:
- Go to Settings → Notifications in your Shopify admin
- Click any notification type (Order Confirmation, Shipping Notification, etc.) to open the editor
- Edit the HTML/Liquid template directly — Shopify provides liquid variables for order data
- Upload your logo in Online Store → Themes → Customize → Theme settings → Logo — it appears automatically in notification emails
- In Settings → General, set your sender email — Shopify authenticates it automatically via SPF/DKIM
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/bounce-webhook-handling-and-suppression-/criteria.json 3.1 KB
- evals/bounce-webhook-handling-and-suppression-/task.md 1.9 KB
- evals/postmark-integration-with-domain-separat/criteria.json 2.6 KB
- evals/postmark-integration-with-domain-separat/task.md 1.8 KB
- evals/sendgrid-react-email-template-integratio/criteria.json 2.8 KB
- evals/sendgrid-react-email-template-integratio/task.md 1.8 KB
- tile.json 248 B
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 254 lines · 32 tokens per session scan A 5a4108ae2b2d
email-service-integration is a skill published in the GitHub repository finsilabs/awesome-ecommerce-skills (52 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 2,730 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
email-deliverability
Use when mail already sent lands in spam, is rejected, or fails the Gmail/Yahoo bulk-sender checks and the fix is authentication and reputation, not the sending code: SPF/DKIM/DMARC alignment, domain warmup, spam-complaint rate, one-click unsubscribe, BIMI. NOT putting mail on the wire through a provider API (that is…
email-connector
Use when wiring server code to send transactional or bulk email via Resend, SendGrid, or Postmark: a provider-agnostic sendEmail() seam, idempotent retries, 100-cap batches with partial failures, transactional-vs-broadcast streams, bounce webhooks feeding a suppression list. NOT SPF/DKIM/DMARC inbox reputation (that…
email-security
DMARC/SPF/DKIM check, email spoofing, SMTP test, and security header analysis.
analyzing-email-headers-for-phishing-investigation
Parse and analyze email headers (Received chain, Return-Path, Message-ID) to trace the true origin of a phishing email and validate SPF, DKIM, and DMARC results to confirm or rule out sender spoofing. Use when triaging a suspicious or reported email, investigating a phishing incident, or verifying whether a message's…
analyzing-email-headers-for-phishing-investigation
Parse and analyze email headers to trace the origin of phishing emails, verify sender authenticity, and identify spoofing through SPF, DKIM, and DMARC validation.
analyzing-email-headers-for-phishing-investigation
Use when parse and analyze email headers to trace the origin of phishing emails, verify sender authenticity, and identify spoofing through SPF, DKIM, and DMARC validation. Use when working with analyzing email headers for phishing investigation.