sales-sms-marketing
SMS marketing strategy — opt-in collection, compliance (TCPA/GDPR), campaign types, automation triggers, segmentation, timing, two-way messaging, MMS, and analytics. Covers strategy and implementation across Omnisend, Klaviyo, Attentive, Postscript, Brevo, ActiveCampaign, Mailchimp, and more. Use when SMS campaigns have low click-through rates, opt-in list growth has stalled, subscribers are opting out too fast, you're unsure if your SMS program is TCPA/GDPR compliant, automations aren't converting, or you don't know which SMS platform to pick. Do NOT use for email marketing (use /sales-email-marketing), push notifications (use /sales-push-notification), cold outbound sequences (use /sales-cadence), or platform-specific config (use /sales-omnisend, /sales-klaviyo, /sales-brevo, etc.). For Omnisend-specific help, use /sales-omnisend. For Klaviyo-specific help, use /sales-klaviyo.
What this skill does
# SMS Marketing
Help the user with SMS marketing strategy — from opt-in collection and compliance through campaign design, automation, segmentation, and analytics. This skill is tool-agnostic but includes platform-specific guidance for Omnisend, Klaviyo, Attentive, Postscript, Brevo, ActiveCampaign, Mailchimp, and others.
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated knowledge.
Ask the user:
1. **What do you need help with?**
- A) Strategy — planning an SMS marketing program from scratch
- B) Opt-in collection — building an SMS subscriber list
- C) Compliance — TCPA, GDPR, consent management
- D) Campaign design — what to send, copy, CTAs
- E) Automation — triggered SMS (cart abandonment, welcome, post-purchase)
- F) Segmentation — targeting the right contacts for SMS
- G) Timing & frequency — when and how often to text
- H) Two-way messaging — conversational SMS
- I) Analytics — measuring SMS performance
- J) Tool selection — choosing an SMS marketing platform
- K) Something else — describe it
2. **What's your business type?**
- A) E-commerce / DTC brand
- B) SaaS / software
- C) Local business / retail
- D) B2B services
- E) Creator / media
- F) Other
3. **What platform are you using (or considering)?**
- A) Omnisend
- B) Klaviyo
- C) Attentive
- D) Postscript
- E) Brevo
- F) ActiveCampaign
- G) Mailchimp
- H) Not decided yet
- I) Other
**If the user's request already provides most of this context, skip directly to the relevant step.** Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end.
## Step 2 — Strategy and approach
### When SMS marketing works best
SMS is highest-value for:
- **Time-sensitive offers** — flash sales, limited drops, expiring discounts
- **Transactional updates** — order confirmation, shipping, delivery
- **Cart abandonment** — 2-3x higher conversion than email for cart recovery
- **Welcome offers** — immediate discount delivery after opt-in
- **VIP/loyalty** — exclusive early access for top customers
- **Back-in-stock** — instant notification for high-demand products
SMS is lowest-value for:
- Long-form content (use email)
- Cold outreach (use email or LinkedIn)
- Non-time-sensitive announcements (use email or push)
- B2B enterprise sales (SMS is primarily B2C/DTC)
## Step 3 — SMS marketing reference
**Read `references/platform-guide.md`** for detailed compliance requirements, campaign types, copy best practices, platform-specific guidance, timing, and metrics.
*You no longer need the platform guide details — focus on the user's specific situation.*
## Step 4 — Actionable guidance
### SMS program launch checklist
1. **Set up compliance** — configure quiet hours, opt-out handling, sender identification
2. **Create opt-in forms** — multi-step popup (email → SMS), checkout checkbox, keyword opt-in
3. **Welcome SMS** — send immediately on opt-in with a discount or value
4. **Cart abandonment SMS** — set up automation (1 hour after cart creation, stop on purchase)
5. **Post-purchase SMS** — review request or cross-sell 7-14 days after delivery
6. **First campaign** — flash sale or exclusive offer to SMS list (test with a small segment first)
7. **Measure** — track opt-in rate, click rate, revenue per message, unsubscribe rate
## Gotchas
1. **SMS consent is separate from email consent.** Never send SMS to someone who only opted into email. This violates TCPA and can result in $500-$1,500 per message in fines. Always collect explicit SMS consent.
2. **Emojis triple your message cost.** A single emoji switches encoding from GSM-7 (160 chars) to Unicode (70 chars), potentially turning 1 segment into 3. Know the cost before adding that fire emoji.
3. **Carrier filtering is real.** US carriers (T-Mobile, AT&T, Verizon) actively filter marketing SMS. Avoid URL shorteners (bit.ly is flagged), ALL CAPS, excessive punctuation, and spammy language. Use your platform's built-in link shortener instead.
4. **SMS unsubscribes are final and expensive.** Unlike email where users might re-subscribe, SMS unsubscribes are permanent. Each lost subscriber cost you $2-$5+ to acquire. Quality over quantity — send fewer, better messages.
5. **International SMS costs vary wildly.** US: ~$0.01-$0.02/message. UK: ~$0.04. Australia: ~$0.06. Some countries: $0.10+. Always check per-country rates before launching international SMS campaigns.
- **Self-improving**: If you discover something not covered here, append it to `references/learnings.md` with today's date.
## Before recommending a specific platform skill
This skill covers a strategy domain across many platforms. **Before pointing the user to any specific platform skill** (any `/sales-{platform}` listed in `## Related skills`, e.g., `/sales-mailshake`, `/sales-klaviyo`, `/sales-apollo`), read that platform skill's actual `SKILL.md` first. The 1-line description in `## Related skills` is enough to *identify* a candidate — it's not enough to *commit* to it or to write a prompt that invokes it well.
**How to read it:**
- If `~/.claude/skills/{skill-name}/SKILL.md` exists locally, `Read` it.
- For `sales-*` skills, `WebFetch` directly from this repo: `https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md` — e.g., for `sales-mailshake`: `https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md`.
- For non-`sales-*` skills (third-party), look up `{org}/{repo}` in `~/.claude/skills/sales-do/references/skill-sources.md` if installed and fetch the same `skills/{skill-name}/SKILL.md` path under that repo.
**After reading,** ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its `argument-hint` shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's `argument-hint`. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.
## Related skills
- `/sales-omnisend` — Omnisend platform help (SMS + email + push in one ecommerce platform)
- `/sales-klaviyo` — Klaviyo platform help (SMS + email for e-commerce, predictive analytics)
- `/sales-brevo` — Brevo platform help (SMS + email + WhatsApp + push)
- `/sales-activecampaign` — ActiveCampaign platform help (SMS in marketing automation)
- `/sales-mailchimp` — Mailchimp platform help (SMS add-on)
- `/sales-sendpulse` — SendPulse platform help (SMS + email + chatbots + Automation 360)
- `/sales-email-marketing` — Email marketing strategy (coordinate SMS + email cadence)
- `/sales-push-notification` — Push notification strategy (another engagement channel)
- `/sales-audience-growth` — Growing your subscriber list (feeds SMS opt-in)
- `/sales-checkout` — Checkout optimization (checkout is a key SMS opt-in point)
- `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. Install: `npx skills add sales-skills/sales --skill sales-do`
## Examples
### Example 1: Launching SMS for a Shopify store
**User says**: "I run a Shopify clothing store on Omnisend. I want to start SMS marketing. Where do I begin?"
**Skill does**: Designs a launch plan — multi-step popup for SMS opt-in (collect email first, then phone), welcome SMS with 10% discount, cart abandonment SMS at 1 hour, and a weekly flash sale campaign. Explains Omnisend SMS credit costs and TCPA compliance setup. Recommends starting with 2 SMS/month and scaling based on engagement.
**Result**: User has an SMS launch plan with opt-in forms, 3 automations, and compliance configured
### Example 2: Choosing an SMS platform
**User says**: "We're on Klaviyo for email and considering adding SMS. Should we use Klaviyo SMS or switch to Attentive?"
**Skill does**: Compares Klaviyo SMS (integratedRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".