email-sequence SKILL.md skillA
email-sequence from mia-ppp/pmm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mia-ppp/pmm-skills/email-sequence@v1.2.0Pins v1.2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mia-ppp/pmm-skills
- Path
skills/email-sequence/SKILL.md- Versions recorded
- 4
- Latest version
- v1.2.0, committed Sep 30, 2026
- First version recorded
- May 10, 2026
- Size
- 9,618 bytes
- Repository stars
- 54
- License
- MIT
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Email Sequence Design **Use the company SSOT when present:** follow `../_shared/ssot-consumption.md` and the project manifest to load only relevant approved context. Preserve covered strategic meaning while keeping this skill’s existing scope and frameworks. You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion. ## Initial Assessment **Load the evidence labels:** read `../_shared/evidence-gaps.md` (relative to this skill's folder) and follow its Customer-facing copy rules. Never drop a claim because proof is missing, and never state it as fact. Keep it as a `[Gap: ...]` placeholder with a provable fallback line under it. **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before creating a sequence, understand: 1. **Sequence Type** - Welcome/onboarding sequence - Lead nurture sequence - Re-engagement sequence …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_acmmlt7hiwbxgqoh/3030f8eded1d4855ed0233da9a3c06a3f6ec5b127c2bce8e7fb0c6bf46d7af25.json
Then /plugin install email-sequence@markdownregistry-acmmlt7hiwbxgqoh in Claude Code. It installs v1.2.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mia-ppp/pmm-skills/email-sequence@sha256:3030f8eded1d4855The line at the top of this page pins the label v1.2.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_acmmlt7hiwbxgqoh)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in mia-ppp/pmm-skills/email-sequence since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of email-sequence from somewhere else? Ask it: where did my email-sequence come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between May 10, 2026 and Sep 30, 2026, about one every 48 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.0 latest | 2026-09-30 | f96aeae | 9,618 B | A | view · diff |
| v1.2.0 | 2026-09-30 | 2f6abba | 9,577 B | A | view · diff |
| v1.1.0 | 2026-09-26 | 6092dd2 | 8,592 B | A | view · diff |
| v1.1.0 | 2026-05-10 | bb54afb | 8,544 B | A | view |
Copies
1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds an older version.
- the-utopia-studio/skills · plugins/utopia-gtm/skills/email-sequence/SKILL.md · 3 versions behind · 7 stars
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/email-sequence/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9618 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mia-ppp/pmm-skills · 54 stars · license MIT · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_acmmlt7hiwbxgqoh GET https://markdownregistry.com/api/v1/resolve?ref=mia-ppp/pmm-skills/email-sequence GET https://markdownregistry.com/api/v1/blob/3030f8eded1d4855ed0233da9a3c06a3f6ec5b127c2bce8e7fb0c6bf46d7af25
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from mia-ppp/pmm-skills
Every file in mia-ppp/pmm-skills