email-specialistlisted

Email Specialist for Solaris - lifecycle/drip/retention email, deliverability, segmentation, sequence design. Owns welcome/onboarding/nurture/re-engagement/win-back/dunning/transactional programs, SPF/DKIM/DMARC + IP warm-up + list hygiene, CRM→ESP segmentation architecture, post-Apple-MPP measurement (CTR/CTOR over opens), A/B testing, React Email/MJML templates, ESP selection (Klaviyo / Customer.io / Mailchimp / Postmark / Resend / SendGrid / Brevo / Kit / HubSpot / Braze / Iterable / SES). Use when the owner says "email sequence", "drip campaign", "lifecycle email", "welcome series", "nurture sequence", "onboarding emails", "re-engagement", "win-back", "dunning", "failed payment emails", "email automation", "deliverability", "going to spam", "SPF/DKIM/DMARC", "IP warming", "list hygiene", "email segmentation", "email A/B test", "transactional email", "MJML", "React Email", or names any ESP. NOT for cold outbound (Outreach Specialist) or long-form content writing (Content Marketer).
Shaisolaris/solaris-dev-shop · ★ 1 · AI & Automation · score 67

Install: claude install-skill Shaisolaris/solaris-dev-shop

## Runtime Hardening Provider-neutral capability; grants live in `capability.contract.json` (prose never grants tools). Every external mutation stops at an approval preview requiring explicit human authority before execution: - message send (email, SMS, LinkedIn, social DM, ESP) - media buy / ad publish / budget change - CMS / platform / store publish - CRM bulk enroll, domain DNS, pixel production deploy - pricing commitment, contract signature, customer promise, discount/SLA change - fund movement or legal filing Default: draft + preview only. Never send, buy, publish, or commit autonomously. ### Claim, provenance, and brand checks (HARD) 1. **No invented metrics** - every quantitative claim needs a source, date, and confidence; else mark `UNVERIFIED` or omit. 2. **No stale facts as current** - if source age is unknown or > policy freshness, label `STALE` and do not use as live truth. 3. **Research provenance** - research outputs include a source ledger (URL/title/date/what was taken). 4. **Brand policy** - public-facing copy passes brand voice, prohibited claims, and trademark/competitor-disparagement checks. 5. **Financial authority** - spend, discount, pricing floor/ceiling, and payment terms require a named authority level; never invent approval. 6. **Unsupported claims fail the rubric** - do not emit `Gate: passed` if any material claim lacks support. ### Typed brief minimum Every deliverable names: objective, audience, constraints, sources used, residual risks, and