Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ariadoss/superskills --skill email-marketinggit clone --depth 1 https://github.com/ariadoss/superskillsWrote 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/ariadoss/superskills/email-marketing)<a href="https://agentmods.dev/skills/ariadoss/superskills/email-marketing"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/email-marketing/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/ariadoss/superskills/email-marketing"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/email-marketing.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.00089 | $0.01418 |
| Opus 5 | $0.00044 | $0.00709 |
| Sonnet 5 | $0.00018 | $0.00284 |
| Haiku 4.5 | $0.00009 | $0.00142 |
Grade A, and why
email-marketing 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 11d 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.
This is a copy
100% identical to email-marketing — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Channels: Email Marketing
Guides email marketing strategy for AI/SaaS products. Email ROI ~$36 per dollar spent; open/click rates typically higher than social. Covers EDM vs Newsletter, five content types, deliverability (SPF/DKIM/DMARC), and SEO synergy via article delivery.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for audience and content strategy. See content-marketing for content types and formats across channels.
Identify:
- Goal: Retention, conversion, brand reach, or SEO synergy
- Content mix: Onboarding, campaign, announcement, features, newsletter
- List size: Bulk sender rules (5,000+/day) require Gmail/Yahoo compliance
EDM vs Newsletter
| Type | Purpose | Use |
|---|---|---|
| EDM | Direct marketing; conversion-focused | Promotions, campaigns, announcements; bulk sends |
| Newsletter | Ongoing value; relationship | Industry insights, curated articles; regular cadence |
Combine both: EDM for push; Newsletter for nurture. Cover different stages and goals.
Five Content Types
| Type | Use |
|---|---|
| Onboarding | Welcome + first-use guidance; 5-7 day sequence; behavior-triggered; drive "Aha!" moment |
| Campaign | Promotions, limited-time; conversion or participation |
| Announcement | Product launch, major update; one-time important notice |
| Features update | New features, improvements; help users adopt |
| Blog/Newsletter | Curated articles, industry insights; sustained touch |
User Best Practices
| Practice | Guideline |
|---|---|
| Personalization | Segment by behavior, source, stage; boosts open/click |
| Timing | New users: dense; existing: controlled pace; behavior-triggered > calendar-only |
| Welcome series | Send soon after signup; 5-7 emails over days; guide first key action |
| Unsubscribe | One-click required (Gmail/Yahoo); honor within 48h; clear entry |
| Complaint rate | Keep below 0.3%; list hygiene critical |
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.
- 11d ago First seen · 124 lines · 89 tokens per session scan A a5d4c597afec
email-marketing is a skill published in the GitHub repository ariadoss/superskills (9 stars, last pushed 4d ago), licensed MIT. It adds 89 tokens to every session and 1,418 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to email-marketing, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…