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 Sudhakaran88/solopreneur-skills --skill ecom-email-nurturegit clone --depth 1 https://github.com/Sudhakaran88/solopreneur-skillsWrote 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/sudhakaran88/solopreneur-skills/ecom-email-nurture)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/ecom-email-nurture"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/ecom-email-nurture/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/sudhakaran88/solopreneur-skills/ecom-email-nurture"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/ecom-email-nurture.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.00111 | $0.04478 |
| Opus 5 | $0.00056 | $0.02239 |
| Sonnet 5 | $0.00022 | $0.00896 |
| Haiku 4.5 | $0.00011 | $0.00448 |
Grade A, and why
ecom-email-nurture 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 12d 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an ecommerce email expert helping D2C solopreneurs build the Klaviyo flows that recover abandoned revenue, turn first-time buyers into repeat customers, and run 24/7 without a team.
When to Use This Skill
Use this skill when the conversation involves any of the following:
- Setting up or auditing Klaviyo (or Omnisend) flows for a Shopify store
- Writing or improving abandoned cart, welcome, post-purchase, browse abandon, or winback emails
- Deciding which flows to build first when starting from zero
- Choosing between Klaviyo, Omnisend, or Privy for a solo operator
- Adding SMS alongside email inside automation flows
- Diagnosing low open rates, recovery rates, or revenue-per-recipient in existing flows
- Segmenting a list into VIP, at-risk, first-time buyer, or repeat-purchaser buckets
Do NOT use this skill for generic newsletter sequences, SaaS onboarding drips, or B2B cold outreach — see email-sequence or onboarding-cro instead.
Context Check — Ask Before Building
Before writing a single email, surface these facts:
| Question | Why It Matters |
|---|---|
| What platform — Shopify, WooCommerce, other? | Flow triggers differ; Shopify + Klaviyo is the gold standard |
| ESP in use — Klaviyo, Omnisend, Privy, Shopify Email? | Determines what's possible (predictive data, SMS, splits) |
| Average Order Value (AOV)? | Drives discount strategy and whether to offer one at all |
| Product type — consumable, one-time purchase, high-consideration? | Sets winback timing and post-purchase cadence |
| Which flows are already live? | Avoids rebuilding what works; prioritises gaps |
| Current monthly email revenue attribution (if known)? | Baseline for measuring improvement |
| SMS number collected and opted in? | Determines if SMS add-on is realistic |
If the user says "I'm starting from scratch," skip the audit questions and go straight to Priority Order below.
ESP Selection for Shopify Solopreneurs
Klaviyo — the industry default for serious D2C brands. Best-in-class segmentation, predictive CLV, churn risk scoring, expected next order date. Native Shopify sync. Flows generate ~41% of total email revenue from just ~5% of sends, with revenue-per-recipient nearly 18x higher than broadcast campaigns. Worth the premium once monthly email revenue justifies the list cost.
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.
- 12d ago First seen · 360 lines · 111 tokens per session scan A 5eb123021586
ecom-email-nurture is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 111 tokens to every session and 4,478 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
mcp-playbook
Deep reference / playbook for correctly driving the crevideo-reach MCP — TikTok Shop affiliate (分销) and product-listing work: tool map (89 tools), the affiliate create flow, product onboarding, TC automation-wrapper vs direct entity, Open Collaboration (OC), read-side tool choice, filter schema, ID-space gotchas…
lint
Audit workspace structural health: stale status, orphan files/folders, unannotated decision supersessions, manifest drift. Read-only; --fix applies safe annotations. Use when the user asks for a health check or whether anything is stale, drifted, or inconsistent, or after session-start's unclean-close warning. Don't…
session-end
Use when closing a Memex session: at the SessionEnd hook, when a session is about to time out, when the hook didn't fire, or to force a clean checkpoint before a long break. Updates memory files, refreshes closets, verifies wikilinks.
upgrade
Upgrades an existing Memex workspace to the current major version in one command. Detects current state (manifest marker, summary-format version, closets coverage) and runs only the needed subset of /memex:resummarize, /memex:reindex, and lint.
consolidate
Sweeps the workspace for drift -- duplicate files, unannotated decision supersessions, orphans, bloated decisions logs -- on a cadence separate from session-end. Read-only by default; --fix applies safe annotations only (never auto-merges files).
reindex
Backfills or rebuilds every hub's CLOSETS.md from scratch, so closets exist immediately instead of accumulating across many session-ends -- for a v1-to-v2 upgrade, a large bulk import, or whenever you want full v2 retrieval quality now.