sales-mailerlite
MailerLite platform help — email campaigns, automation workflows, landing pages, signup forms, websites, e-commerce, digital products, paid newsletters, transactional email, and email verification. Use when emails aren't reaching subscribers, automation workflow isn't triggering, landing page conversion is low, signup forms aren't collecting leads, MailerLite account got suspended or rejected, domain authentication (SPF/DKIM) setup is failing, free plan limits are too restrictive, or you need help with the MailerLite API. Do NOT use for cross-platform email strategy (use /sales-email-marketing) or general deliverability (use /sales-deliverability).
What this skill does
# MailerLite Platform Help
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated platform knowledge.
1. **What do you need help with?**
- A) Email campaigns — creating, sending, templates, A/B testing
- B) Automation — workflows, triggers, delays, conditions
- C) Landing pages — building, optimizing, forms
- D) Signup forms & pop-ups — design, targeting, embedding
- E) E-commerce — Shopify/WooCommerce integration, abandoned cart, product emails
- F) Paid newsletter — setting up subscriber payments via Stripe
- G) Digital products — selling ebooks, downloads
- H) Transactional email — order confirmations, password resets
- I) Account issues — suspension, approval, domain auth, deliverability
- J) API integration — connecting MailerLite to your app
- K) Something else
2. **Which plan are you on?**
- A) Free (500 subscribers, 12K emails/mo)
- B) Growing Business ($10/mo)
- C) Advanced ($20/mo)
- D) Enterprise
- E) Not sure
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
## Step 2 — Route or answer directly
| Problem domain | Route to |
|---|---|
| Email marketing strategy (not MailerLite-specific) | Run: `/sales-email-marketing {user's question}` |
| SPF/DKIM/DMARC setup, inbox placement, warmup | Run: `/sales-deliverability {user's question}` |
| Newsletter monetization strategy | Run: `/sales-newsletter {user's question}` |
| Growing subscriber list strategy | Run: `/sales-audience-growth {user's question}` |
| Landing page / funnel conversion strategy | Run: `/sales-funnel {user's question}` |
| Selling digital products strategy | Run: `/sales-digital-products {user's question}` |
| Transactional email provider comparison | Run: `/sales-transactional-email {user's question}` |
| Connecting MailerLite to other tools | Run: `/sales-integration {user's question}` |
If the question is MailerLite-specific, continue to Step 3.
## Step 3 — MailerLite platform reference
**Read `references/platform-guide.md`** for the full platform reference — modules, pricing, integrations, data model, workflows.
Answer the user's question using only the relevant section. Don't dump the full reference.
**If the question involves the API**, also read `references/mailerlite-api-reference.md` for endpoint details.
## Step 4 — Actionable guidance
You no longer need the platform guide — focus on the user's specific situation.
- For campaign issues: check subscriber status, segment targeting, schedule settings
- For automation issues: verify triggers are set, check subscriber eligibility, review step conditions
- For deliverability: check domain authentication status, review bounce rate, check spam complaint rate
- For account issues: review MailerLite's anti-spam policy, check subscriber import quality, verify domain ownership
- For API issues: verify API key permissions, check rate limits (120 req/min), validate JSON payloads
If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.
## Gotchas
> *Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.*
1. **Account approval is strict** — MailerLite manually reviews every new account. If your website is "under construction" or your domain is brand new, expect rejection. Have a live site with clear opt-in methods before signing up.
2. **Free plan reduced to 500 subscribers** (Sep 2025) — was 1,000. No templates on the free plan either. If you're outgrowing free, Growing Business at $10/mo unlocks unlimited emails and templates.
3. **Automation is basic** — no branching logic or multi-path workflows. If/else conditions exist but flows are linear. For complex automation, consider ActiveCampaign or Klaviyo.
4. **No spam/design testing** — MailerLite has no inbox rendering preview across email clients and no spam score testing. Use Litmus or Mail Tester externally.
5. **Account suspension without warning** — importing a list with high bounce rates can trigger immediate suspension. Always clean lists with MailerCheck or ZeroBounce before importing.
6. **Customer support is email-only on lower plans** — live chat requires Advanced plan ($20/mo). Response times can be slow on Free/Growing Business.
7. **Digital products and paid newsletters require Stripe** — no PayPal or other payment processor support for selling through MailerLite.
8. **API rate limit is 120 requests/minute globally** — not per endpoint. Batch operations help (up to 50 requests per batch call).
## Related skills
- `/sales-email-marketing` — Email marketing strategy across all platforms (campaigns, automation, segmentation)
- `/sales-deliverability` — Cross-platform deliverability (SPF/DKIM/DMARC, warmup, reputation)
- `/sales-newsletter` — Newsletter monetization (paid subscriptions, sponsorships, ad sales)
- `/sales-audience-growth` — Growing your subscriber list (lead magnets, cross-promotion, referrals)
- `/sales-funnel` — Sales funnel strategy (landing pages, conversion paths)
- `/sales-digital-products` — Selling digital products (ebooks, templates, courses)
- `/sales-transactional-email` — Transactional email (provider comparison, API setup)
- `/sales-kit` — Kit platform help (MailerLite alternative for creators)
- `/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: Account rejected
**User says**: "MailerLite rejected my account and I don't know why"
**Skill does**: Explains the manual review process, common rejection reasons (new domain, under-construction site, unclear opt-in), and how to appeal with a live site and clear opt-in documentation
**Result**: User understands what to fix and how to resubmit
### Example 2: Automation not triggering
**User says**: "My welcome automation isn't sending emails to new subscribers"
**Skill does**: Walks through trigger verification (form vs API vs import), subscriber status check (must be "active"), automation status (must be "active" not "draft"), and common gotchas (subscriber already in the automation)
**Result**: User identifies the misconfiguration and fixes it
### Example 3: API integration
**User says**: "How do I add subscribers to a group via the MailerLite API?"
**Skill does**: Shows the POST /api/subscribers endpoint with groups array, explains upsert behavior, provides code example with Bearer auth, notes the 120 req/min rate limit
**Result**: User has working API integration code
## Troubleshooting
### Emails going to spam
**Symptom**: Campaign emails landing in spam for subscribers
**Cause**: Domain not authenticated, shared IP reputation, or content triggers
**Solution**: 1) Authenticate domain — add DKIM (CNAME) + SPF (TXT) records in DNS, verify in MailerLite. 2) Check subscriber engagement — remove inactive subscribers (no opens in 90+ days). 3) Avoid spam trigger words in subject lines. 4) On Enterprise, request dedicated IP for better reputation control.
### High bounce rate on import
**Symptom**: Importing a list triggers high bounce rate warning or account suspension
**Cause**: List contains invalid, disposable, or stale email addresses
**Solution**: Clean the list with MailerCheck (MailerLite's built-in verifier) or ZeroBounce before importing. Remove addresses that haven't engaged in 6+ months. Start with your most engaged segment and gradually import the rest.
### Automation skipping subscribers
**Symptom**: Some subscribers enter the automation but skip certain steps
**Cause**: Subscriber status changed mid-workflow, or step conditions exclude them
**Solution**: Check each step's conditions. Verify subscriber status is "active" throughout. Check if the subscriber was removed from the triggering group. Review the automation activity log for specific subscriber paths.
Related 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".