/newsletter-signup
When the user wants to design, optimize, or audit newsletter signup forms. Also use when the user mentions "newsletter," "email signup," "subscribe form," "email capture," "lead magnet," "newsletter form," "email opt-in," "subscribe CTA," "newsletter signup," or "email list
$ npx -y skills add kostja94/marketing-skills --skill newsletter-signup --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/newsletter-signup
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to design, optimize, or audit newsletter signup forms. Also use when the user mentions "newsletter," "email signup," "subscribe form," "email capture," "lead magnet," "newsletter form," "email opt-in," "subscribe CTA," "newsletter signup," or "email list
SKILL.md
newsletter-signup.SKILL.mdname: newsletter-signup-generator
description: When the user wants to design, optimize, or audit newsletter signup forms. Also use when the user mentions "newsletter," "email signup," "subscribe form," "email capture," "lead magnet," "newsletter form," "email opt-in," "subscribe CTA," "newsletter signup," or "email list building." For email strategy, use email-marketing.
metadata:
version: 1.0.1
Components: Newsletter Signup
Guides newsletter signup form design for list growth. Email subscribers spend 138% more than non-subscribers; top popups convert at 23%+.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
Initial Assessment
**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for audience and value proposition.
Identify: 1. **Placement**: Header, footer, popup, inline, sidebar 2. **Incentive**: What subscribers receive 3. **Platform**: Web, mobile, both
Form Design
Minimal Fields
- **Email only** when possible; highest conversion
- Add name only if needed for personalization
- Wrong number of fields significantly impacts conversion
Value Proposition
- Clear: what subscribers receive, how often
- Transparent: avoid disappointing subscribers
- Incentive: lead magnet, discount, exclusive content
Visual Design
- Clearly clickable submit button
- Mobile-first; responsive layout
- Appropriate input types (e.g., `type="email"` for mobile keyboards)
- Trust marks or security indicators
Placement
| Placement | Best For | Pros | Cons | |-----------|----------|------|------| | **Header** | High visibility | Always visible | Limited space | | **Footer** | Secondary capture | Non-intrusive | Lower visibility | | **Footer bar** | Persistent | Sticky | Can annoy | | **Popup** | High intent | High conversion | Intrusive | | **Inline** | Content pages | Contextual | Depends on scroll |
- Avoid hiding forms behind unclicked buttons/links
- Don't place competing forms nearby
Accessibility
| Requirement | Practice | |-------------|----------| | **Labels** | `<label>` for each input; `for`/`id` association | | **Placeholders** | Don't replace labels; supplement only | | **Error messages** | Clear, associated with field | | **Keyboard** | Full tab order; submit via Enter | | **Touch targets** | ≥44×44px for submit button |
Technical
- **Validation**: Client-side; server-side required
- **Privacy**: Link to privacy policy; GDPR/CCPA compliance
- **Double opt-in**: When required by jurisdiction or best practice
Output Format
- **Form structure** (fields, copy)
- **Placement** recommendation
- **Value proposition** suggestions
- **Accessibility** checklist
Related Skills
- **signup-login-page-generator**: Full account signup; form design principles apply
- **landing-page-generator**: Lead capture landing page contains signup form; LP exchanges value for email
- **email-marketing**: Full email marketing strategy; EDM, newsletter, deliverability, content types
- **footer-generator**: Footer often hosts signup forms
- **cta-generator**: Submit button is a CTA
- **trust-badges-generator**: Trust marks near form
Read more
name: newsletter-signup-generator description: When the user wants to design, optimize, or audit newsletter signup forms. Also use when the user mentions "newsletter," "email signup," "subscribe form," "email capture," "lead magnet," "newsletter form," "email opt-in," "subscribe CTA," "newsletter signup," or "email list building." For email strategy, use email-marketing. metadata: version: 1.0.1
Components: Newsletter Signup
Guides newsletter signup form design for list growth. Email subscribers spend 138% more than non-subscribers; top popups convert at 23%+.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
Initial Assessment
**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for audience and value proposition.
Identify: 1. **Placement**: Header, footer, popup, inline, sidebar 2. **Incentive**: What subscribers receive 3. **Platform**: Web, mobile, both
Form Design
Minimal Fields
- **Email only** when possible; highest conversion
- Add name only if needed for personalization
- Wrong number of fields significantly impacts conversion
Value Proposition
- Clear: what subscribers receive, how often
- Transparent: avoid disappointing subscribers
- Incentive: lead magnet, discount, exclusive content
Visual Design
- Clearly clickable submit button
- Mobile-first; responsive layout
- Appropriate input types (e.g., `type="email"` for mobile keyboards)
- Trust marks or security indicators
Placement
| Placement | Best For | Pros | Cons | |-----------|----------|------|------| | **Header** | High visibility | Always visible | Limited space | | **Footer** | Secondary capture | Non-intrusive | Lower visibility | | **Footer bar** | Persistent | Sticky | Can annoy | | **Popup** | High intent | High conversion | Intrusive | | **Inline** | Content pages | Contextual | Depends on scroll |
- Avoid hiding forms behind unclicked buttons/links
- Don't place competing forms nearby
Accessibility
| Requirement | Practice | |-------------|----------| | **Labels** | `<label>` for each input; `for`/`id` association | | **Placeholders** | Don't replace labels; supplement only | | **Error messages** | Clear, associated with field | | **Keyboard** | Full tab order; submit via Enter | | **Touch targets** | ≥44×44px for submit button |
Technical
- **Validation**: Client-side; server-side required
- **Privacy**: Link to privacy policy; GDPR/CCPA compliance
- **Double opt-in**: When required by jurisdiction or best practice
Output Format
- **Form structure** (fields, copy)
- **Placement** recommendation
- **Value proposition** suggestions
- **Accessibility** checklist
Related Skills
- **signup-login-page-generator**: Full account signup; form design principles apply
- **landing-page-generator**: Lead capture landing page contains signup form; LP exchanges value for email
- **email-marketing**: Full email marketing strategy; EDM, newsletter, deliverability, content types
- **footer-generator**: Footer often hosts signup forms
- **cta-generator**: Submit button is a CTA
- **trust-badges-generator**: Trust marks near form
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill

