email-campaign
Skill43 starsChanged 23 days agoMITView on GitHub
A sequence of emails that share one template and one voice: the plan, the timing, every subject line, every message with its text part. Use for onboarding, a launch series, a nurture or a re-engagement run.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- StephanMeijer/skillstheir own version, first seen Nov 8, 2026
- munnam77/claude-for-solopreneurstheir own version, first seen Oct 20, 2026
- SELAT-AI/selat-skillstheir own version, first seen Oct 4, 2026
- sidchaudhary/gtm-skillstheir own version, first seen Aug 21, 2026
- clawdbartell-wq/owl-skillstheir own version, first seen May 18, 2026
- BlackBlazeXXX/claude-skills-marketingtheir own version, first seen Mar 31, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- SELAT-AI/selat-skills★ 2same name
- BlackBlazeXXX/claude-skills-marketing★ 1same name
- clawdbartell-wq/owl-skills★ 1same name
- sidchaudhary/gtm-skills★ 1same name
- anshul-garg27/claude-enhancement-suite★ 0same name
- munnam77/claude-for-solopreneurs★ 0same name
- StephanMeijer/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- adapters/agents.mdAGENTS.md
- accessibility-auditSkill
- brand-kitSkill
- chart-designSkill
- dashboard-layoutSkill
- dashboardSkill
- design-critiqueSkill
- design-handoffSkill
- design-qaSkill
- design-reviewSkill
- designSkill
- design-systemSkill
- design-templateSkill
- studioSkill
- email-templateSkill
- helpSkill
- initSkill
- motion-designSkill
- presentation-designSkill
- social-campaignSkill
- social-contentSkill
- statusSkill
- tasteSkill
- variantsSkill
- videoSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Run an email sequence as the Design Manager.
- Very specific: line 35
Run: Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Run an email sequence as the Design Manager.
Deliverable and standard. A sequence plan to standards/copy.md and each email to ${CLAUDE_PLUGIN_ROOT}/skills/desk/standards/email.md, all built on one template picked once, so the series reads as one sender.
Desks.
| Desk | Agent | Tier | Does |
| Growth/Analytics Specialist | desk:growth-analytics-specialist | senior | the sequence logic: how many, when, what each one is for, what to measure |
| Email Copywriter | desk:email-copywriter | builder | subjects, preheaders, bodies, CTAs, text parts for every email |
| Copy Editor | desk:copy-editor | senior | one voice across the run, the banned list |
| Compliance Designer | desk:compliance-designer | senior | footer, consent and the legal line, once for the series |
| Email Designer | desk:email-designer | builder | three template roughs at the senior model, then every email |
| Art Director | desk:art-director | director | the pick of the template, notes on the set |
| Creative Director | desk:creative-director | director | sign-off on the template and the set sheet |
Inputs. Text (the goal, the audience, the product), a file to draw from (onboarding docs, a feature list), a URL, screenshots to feature.
Proof sizes. email-600, light and dark, per email.
Output under .desk/out/<id>/:
sequence.md: a table of number, day, purpose, subject, preheader, CTA, what it measures.NN-<slug>.htmlandNN-<slug>.txtper email, numbered in send order.subjects.md: three subject options per email with counts, the chosen one marked.set.html: every email at thumbnail size on one sheet, in order.renders/per email, light and dark.
Run. Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above. Command name for state and events: email-campaign. Changes to the loop for this command:
- Scope is
full. The sequence plan comes first and sets the count (default 5) and days (default 0, 2, 5, 9, 14). Copy for every email follows through the Copy Editor before any build. - Roughs are three templates shown on email one. The pick is of the template. Every email is then built in it, up to four in parallel, each polished until proof passes light and dark.
- Sign-off is on
set.htmlplus email one and the last one in full. Template notes apply to every email in one polish round.
The ask: $ARGUMENTS
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.