assets/skills/marketing/content/SKILL.md
Create content writing strategy including blog posts, social media, newsletters, and SEO content plans. Use when user says "write content", "content strategy", "blog post", "social media content", "content plan", "seo content", "newsletter".
npx skillsauth add phuthuycoding/moicle marketing-contentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Workflow for creating content strategy: audience research, content pillars, SEO blog posts, social media plans, newsletters.
/docs-write or /docs-sync/marketing-videoRESEARCH → PLAN → WRITE → OPTIMIZE → DISTRIBUTE
Goal: understand audience, competitors, and SEO landscape.
Ask the user for (skip what's already known):
| Field | Example | |-------|---------| | Brand / Product | "Acme — DevOps platform for indie teams" | | Voice / Tone | "Casual but technical, no marketing fluff" | | Primary audience | "Solo / small-team DevOps engineers" | | Pain points | "Too many tools, none integrate well" | | Goals (pick ≤2) | SEO traffic, lead gen, brand awareness, education, community, thought leadership | | Current channels | Blog / X / LinkedIn / Dev.to / YouTube / Newsletter / Discord | | Competitors | 3–5 names + what they do well |
Goal: define content pillars + calendar.
Pick 3–5 themes that ladder up to the brand's positioning. Each pillar gets a mix of formats.
| Pillar | Why it matters to audience | Formats | |--------|---------------------------|---------| | {pillar 1} | {pain → outcome} | blog, social, newsletter | | {pillar 2} | ... | ... |
Plan 4–6 weeks ahead. Use a consistent cadence.
| Week | Blog (long-form) | Social (short-form) | Newsletter | |------|------------------|---------------------|------------| | W1 | {title} | 3 posts (1 educational, 1 hot take, 1 personal) | {topic} | | W2 | ... | ... | ... |
Goal: draft the actual content. One format at a time.
TITLE (≤60 chars, includes primary keyword)
META DESCRIPTION (≤155 chars, includes primary keyword + CTA)
H1 (matches title or close variant)
HOOK (2–3 sentences: the problem the reader has)
TL;DR (3 bullets: the answer up front)
H2: Problem context — why this matters now
H2: The solution — your main argument / approach
H3: Step 1 / Aspect 1
H3: Step 2
H3: Step 3
H2: Common pitfalls — what NOT to do
H2: Real example — actual code / screenshot / case
H2: Next steps — what to do today
CTA (1 line: try the product / subscribe / share)
Target length: 1200–2500 words for SEO; 500–1000 for opinion pieces.
HOOK (1–2 lines — must work alone in the feed)
↓
3–7 posts each ≤280 chars
- Each post stands alone if shared
- One idea per post
- Use line breaks
↓
CTA (link to blog / signup)
SUBJECT (≤50 chars, curiosity > clickbait)
PREVIEW TEXT (≤90 chars, complements subject)
GREETING (personal, 1–2 lines)
MAIN STORY (1 idea, 200–400 words)
LINKS (3–5 curated, with 1-line why-it-matters)
CTA (one ask only)
SIGNATURE
Goal: make the content perform.
Goal: get the content in front of the right people.
| Channel | Adaptation | |---------|------------| | Blog | Full piece, optimized for search | | X | Thread of 3–7 posts pulling key insights + link to blog | | LinkedIn | 1 long-form post (200–500 words), no link in body (link in comments) | | Dev.to / Hashnode | Republish blog with canonical link to original | | Reddit | Comment in relevant thread first, then share post only if community allows | | Newsletter | Featured story or short blurb + link | | YouTube Shorts / TikTok | 30–60 sec extract of key insight |
?utm_source=X&utm_medium=social&utm_campaign={pillar}## Content Plan: {brand / campaign}
### Strategy
- Pillars: {list}
- Audience: {one line}
- Goal: {primary}
### Calendar (next 4 weeks)
{table}
### Pieces Drafted
| Title | Format | Status | Channel |
|-------|--------|--------|---------|
| ... | blog | published | site + X + LinkedIn |
### Metrics to Watch
- {KPI 1, baseline → target}
- {KPI 2}
| When | Use |
|------|-----|
| Building brand identity (logo + colors) | /marketing-logo |
| Creating video scripts / storyboards | /marketing-video |
| Building a full marketing plan | /marketing (combines all three) |
| Writing project documentation | /docs-write |
| Phase | Agent | Purpose |
|-------|-------|---------|
| RESEARCH | @docs-writer | Document research findings |
| PLAN | @clean-architect | Structure pillars and calendar |
| WRITE | @docs-writer | Draft pieces |
| OPTIMIZE | @security-audit | Check for sensitive content / claims |
| DISTRIBUTE | @docs-writer | Channel adaptations |
development
Test-Driven Development workflow. Use when doing TDD, writing tests first, or when user says "tdd", "test first", "test driven", "red green refactor".
development
Thorough pull request review workflow with architecture compliance checks. Use when reviewing pull requests, checking code changes, or when user says "review pr", "check pr", "review code", "pr review", "review pull request".
development
Review local branch changes for architecture compliance, conventions, and code quality before pushing/PR. Stack-aware — detects the project stack and applies the matching rules. Use when user says "review changes", "review branch", "check branch", "check changes", "review my code", "review before pr".
testing
DDD architecture compliance review with automated checks and review loop. Use when user says "architect-review", "architecture review", "review architecture", "check architecture", "review ddd", "ddd review".