ab-test-plan
Design a statistically rigorous A/B or multivariate test plan — If/Then/Because hypothesis, control and variant specs, required sample size per variant…
Audience research module — builds six-dimension buyer personas (demographic, psychographic, behavioral, need-state, information, decision), Jobs-to-Be-Done maps, RFM/behavioral/lifecycle segmentation models, anti-personas with exclusion criteria, B2B buying-committee maps, and
$ npx -y skills add indranilbanerjee/digital-marketing-pro --skill audience-intelligence --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/audience-intelligenceContext preview
The summary Claude sees to decide when to auto-load this skill.
Audience research module — builds six-dimension buyer personas (demographic, psychographic, behavioral, need-state, information, decision), Jobs-to-Be-Done maps, RFM/behavioral/lifecycle segmentation models, anti-personas with exclusion criteria, B2B buying-committee maps, and
name: audience-intelligence description: "Audience research module — builds six-dimension buyer personas (demographic, psychographic, behavioral, need-state, information, decision), Jobs-to-Be-Done maps, RFM/behavioral/lifecycle segmentation models, anti-personas with exclusion criteria, B2B buying-committee maps, and lookalike seed specs. Triggers on \"/digital-marketing-pro:audience-intelligence\", \"who are our customers\", \"build buyer personas\", \"segment our audience\", \"run a JTBD analysis\". Reads the brand profile, industry benchmarks, and campaign history, and works from CRM/survey/analytics data when supplied — or labels hypothesis personas explicitly when data is thin. For a single quick persona document, /digital-marketing-pro:audience-profile is the lighter sibling."
Activate this module when the user's request involves any of the following:
**Trigger phrases**: "buyer persona," "target audience," "who are our customers," "customer profile," "segmentation," "audience segments," "Jobs-to-Be-Done," "JTBD," "psychographic," "ideal customer profile," "ICP," "anti-persona," "lookalike audience," "audience research," "buying committee," "customer avatar"
Before producing any marketing output from this module:
1. **Check session context** — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels, goals, compliance, and competitors shown there. 2. **If you need the full profile**, read: `~/.claude-marketing/brands/{slug}/profile.json` 3. **Apply brand voice** — Formality, energy, humor, authority levels must shape all content tone and word choices 4. **Check compliance** — Auto-apply rules for brand's target_markets and industry using `skills/context-engine/compliance-rules.md` 5. **Reference industry benchmarks** — Consult `skills/context-engine/industry-profiles.md` for the brand's industry 6. **Use platform specs** — Reference `skills/context-engine/platform-specs.md` for character limits and format requirements 7. **Check campaign history** — Run `python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns` before planning new work 8. **If no brand exists**, say: "No brand profile found. Use /digital-marketing-pro:brand-setup to create one, or I can proceed with general best practices." 9. **Check brand guidelines** — If `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` exists, load and enforce: `restrictions.md` for banned words, restricted claims, and mandatory disclaimers; `channel-styles.md` for channel-specific tone overrides (may differ from base voice); `messaging.md` for approved key messages, taglines, and positioning language; `voice-and-tone.md` for detailed voice rules beyond the 4 numeric scores. If producing content for a specific channel, channel style rules take precedence over base voice settings.
Do not ask the user for information that already exists in their brand profile.
Before executing audience intelligence work, gather:
1. **Business Description**: What does the company sell, to whom, and what problem does it solve? 2. **Existing Customer Data**: Any analytics, CRM data, survey results, or customer interviews available 3. **Product/Service Details**: Features, pricing, positioning, and key differentiators 4. **Current Audience Assumptions**: Who does the team think their customers are today? 5. **Market Context**: Industry, competitive landscape, market maturity 6. **Geographic Scope**: Local, regional, national, or global audience 7. **Business Model**: B2B, B2C, B2B2C, D2C — this fundamentally shapes persona structure 8. **Sales Process**: Self-serve, sales-assisted, enterprise sales — determines decision-maker mapping
If the user has minimal data, build hypothesis-driven personas based on business model, product, and market analysis. Label these clearly as hypotheses to be validated.
Your agency just signed a 50-brand client. The previous agency left no playbook. Three brands are bleeding budget, two have stale positioning, one is launching in a regulated jurisdiction next month. Where do you start?
Repo: indranilbanerjee/digital-marketing-pro
Design a statistically rigorous A/B or multivariate test plan — If/Then/Because hypothesis, control and variant specs, required sample size per variant…
Generate 3-5 ad copy variations per platform — headlines, descriptions, and CTAs formatted to Google, Meta, LinkedIn, TikTok, X, and Pinterest specs — each…
Walk through adding a custom MCP server integration to the plugin — searches npm for an existing MCP package (or scaffolds a custom server from the plugin's…
Audit how a brand appears across the 6 canonical AI answer surfaces — ChatGPT, Perplexity, Google AI Mode, AI Overviews, Gemini, Copilot — probing 10-25…
Strategy module for Answer Engine / Generative Engine Optimization — audits AI visibility, restructures content for citation, runs entity-consistency checks…
Generate a portfolio-level dashboard across ALL client brands — per-client RAG health scores, campaign activity, budget pacing, aggregate KPIs, team…