← ClaudeAtlas

email-campaignlisted

Designs a lifecycle campaign end to end and decides whether it runs once or runs forever: email sequences with subject variants and deliverability gates, SMS and push with carrier registration and consent gates, and the recurring version of either with a cadence matched to how fast its signal actually moves. Use for welcome, nurture, convert, retain, win-back and announce campaigns on any channel, and when deciding whether a campaign should become an always-on motion. Boundary: writes the messaging. `customer-journey` designs the multi-step journey structure it sits inside, and `customer-segmentation` defines the audience it targets.
sidchaudhary/gtm-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill sidchaudhary/gtm-skills
# The Campaign Engine One skill for the three decisions that always travel together: what the campaign says, which channel carries it, and whether it fires once or on a cadence. Splitting them produced campaigns designed without their sending gates and cadences designed without the campaign. > **Copy standard.** Read `references/outbound-copy-standards.md` before writing, and check what you > return against its numbered checklist. Awareness-stage calibration, promise continuity, the proof > ladder and the one-ask rule apply to every line here, on every channel. ## Before you write **Run the input list below before you write anything. If one of those inputs is missing, ask for it and stop. Do not return a draft with a warning on it.** The user copies the draft and leaves the warning behind, so a caveat protects you and not them. **Ask at most THREE questions. Hard cap.** Before anything becomes a question, get it yourself: read `.agents/product-context.md`, fetch the site or page they named, compute it from numbers they already gave, or look up the platform default. Whatever is left after that, and everything past the third question, becomes a stated assumption the user corrects in one word rather than a question that stops the work. Number them, and say what you will assume if one goes unanswered. Check `.agents/product-context.md` first so you never ask for something already recorded there. **Write it the way you would say it.** Read `references/house-rules.md` and appl