$npx -y skills add indranilbanerjee/digital-marketing-pro --skill content-engineCreate or optimize marketing content. Use when: blog posts, ad copy, emails, social posts, landing pages, voice guidelines.
| 1 | # Content Engine |
| 2 | |
| 3 | ## When to Use This Skill |
| 4 | |
| 5 | Activate this module when the user's request involves any of the following: |
| 6 | |
| 7 | - **SEO Content**: Blog posts, pillar pages, topic clusters, or any content optimized for search |
| 8 | - **Ad Copy**: Headlines, descriptions, and creative for any paid platform (Google, Meta, LinkedIn, TikTok, etc.) |
| 9 | - **Email Marketing**: Email sequences, drip campaigns, newsletters, transactional emails, or cold outreach |
| 10 | - **Social Media Content**: Organic posts, captions, hashtag strategy, or content calendars for social platforms |
| 11 | - **Landing Pages**: Conversion-focused page copy, hero sections, CTAs, and page structure |
| 12 | - **Content Calendars**: Editorial planning, content scheduling, and theme mapping |
| 13 | - **Brand Voice**: Voice and tone guidelines, messaging frameworks, and brand language systems |
| 14 | - **Content Decay Detection**: Identifying content that has lost rankings, traffic, or relevance over time |
| 15 | - **AI Content Quality Management**: Ensuring AI-generated content meets quality, originality, and brand standards |
| 16 | - **Accessibility Compliance**: Making content accessible (WCAG standards, alt text, readability, screen reader compatibility) |
| 17 | - **Multilingual/Localization**: Adapting content for different languages, cultures, and regional markets |
| 18 | - **Email Infrastructure**: Deliverability, authentication (SPF, DKIM, DMARC), domain warming, and sender reputation |
| 19 | |
| 20 | **Trigger phrases**: "write a blog post," "ad copy," "email sequence," "social media calendar," "landing page," "content calendar," "brand voice," "content audit," "content decay," "AI content," "accessibility," "translate," "localize," "email deliverability," "subject line," "headline," "CTA," "newsletter" |
| 21 | |
| 22 | ## Brand Context (Auto-Applied) |
| 23 | |
| 24 | Before producing any marketing output from this module: |
| 25 | |
| 26 | 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. |
| 27 | 2. **If you need the full profile**, read: `~/.claude-marketing/brands/{slug}/profile.json` |
| 28 | 3. **Apply brand voice** — Formality, energy, humor, authority levels must shape all content tone and word choices |
| 29 | 4. **Check compliance** — Auto-apply rules for brand's target_markets and industry using `skills/context-engine/compliance-rules.md` |
| 30 | 5. **Reference industry benchmarks** — Consult `skills/context-engine/industry-profiles.md` for the brand's industry |
| 31 | 6. **Use platform specs** — Reference `skills/context-engine/platform-specs.md` for character limits and format requirements |
| 32 | 7. **Check campaign history** — Run `python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns` before planning new work |
| 33 | 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." |
| 34 | 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. |
| 35 | |
| 36 | Do not ask the user for information that already exists in their brand profile. |
| 37 | |
| 38 | ## Required Context |
| 39 | |
| 40 | Before executing content work, gather: |
| 41 | |
| 42 | 1. **Content Type**: Which specific content format is needed? |
| 43 | 2. **Audience**: Who is this content for? (Link to personas from Audience Intelligence if available) |
| 44 | 3. **Objective**: What should this content achieve? (Traffic, conversions, engagement, education, retention) |
| 45 | 4. **Brand Voice**: Does a brand voice guide exist? What is the tone? (Professional, casual, authoritative, playful, etc.) |
| 46 | 5. **Keywords/Topics**: For SEO content — target keywords, search intent, and competitive landscape |
| 47 | 6. **Platform**: Where will this content live? (Platform-specific requirements matter) |
| 48 | 7. **Funnel Stage**: Where does this content fit in the customer journey? |
| 49 | 8. **Existing Content**: What related content already exists? (Avoid cannibalization) |
| 50 | 9. **Constraints**: Word count limits, character limits, regulatory disclaimers, brand guidelines |
| 51 | 10. **Performance Benchmarks**: What does success look like for this content type? |
| 52 | |
| 53 | For quick requests (e.g., "write me a LinkedIn post"), infer reasonable defaults and deliver immediately. For strategic content work, gather full context. |
| 54 | |
| 55 | ## Capabilities |
| 56 | |
| 57 | - **SEO Content Creation**: Keyword-optimized blog posts, pillar pages, topic cluster design, meta titles/descrip |