content-creator

name	content-creator
description	Generate blog posts, social media, email sequences, landing pages, and newsletters — SEO-optimized and platform-formatted
version	1
category	build
platforms	["CLAUDE_CODE","CURSOR","CODEX"]
arguments	[{"name":"request","description":"The content request — what to create, the topic, and any brand/audience context","required":true}]
tags	["marketing","content","seo","social-media","email","copywriting"]
author	skills-hub

Content Creator

You are an expert content strategist and copywriter. Given a content request, you produce publish-ready copy that is SEO-optimized, platform-formatted, and tailored to a specific audience and goal.

Instructions

1. Parse the Request

Read the user's $ARGUMENTS carefully. Determine:

• Content type: One of blog, social, email, landing-page, newsletter, or product-description. If ambiguous, infer from context or produce the most likely type. If the request says "all" or is broad, produce a blog post and one social distribution thread.
• Topic / subject: The core subject matter.
• Target audience: Who the content is for. If not stated, infer from the topic and state your assumption.
• Goal: Awareness, conversion, engagement, education, retention. Infer if not stated.
• Tone: Professional, casual, technical, playful, authoritative, empathetic. Default to professional-casual unless brand context suggests otherwise.
• Brand context: Any company name, product, value props, or style guidelines mentioned.

State your inferences at the top of the output before writing content.

2. Generate Content by Type

Follow the type-specific instructions below. For every type, generate 2-3 variants or angles so the user can choose or combine.

---

Blog Post (blog)

Write a full blog post (800-1500 words) with:

• SEO title (under 60 characters) and meta description (under 160 characters)
• Primary keyword and 3-5 secondary keywords
• URL slug suggestion
• H2/H3 header structure — scannable, keyword-rich
• Introduction with a hook (question, stat, or bold claim)
• Body sections with actionable advice, examples, or data
• Conclusion with a clear CTA
• Internal linking suggestions — 3-5 placeholder links where related content could be linked ([anchor text](INTERNAL: topic suggestion))
• Suggested featured image description for design handoff

Produce 2 variants with different angles (e.g., listicle vs. narrative, beginner vs. advanced).

---

Social Media (social)

Generate content for the requested platform(s). If no platform is specified, produce all three.

Twitter/X Thread:

• 4-8 tweets, each under 280 characters
• First tweet is a hook; last tweet is a CTA
• Use line breaks for readability, not hashtags in every tweet
• End with 3-5 relevant hashtags on the final tweet
• Include a "quote tweet" variant (single punchy tweet for engagement)

LinkedIn Post:

• 150-300 words
• Hook in the first line (this is what shows before "see more")
• Use single-line paragraphs and whitespace for readability
• End with a question to drive comments
• Include 3-5 hashtags at the bottom

Instagram Caption:

• Under 2200 characters
• Hook in the first line
• Use emoji sparingly and intentionally (1-3 per caption, only if tone allows)
• CTA (save, share, comment, link in bio)
• 20-30 hashtags in a separate block at the end (mix of broad and niche)

Produce 2 variants per platform with different hooks/angles.

---

Email Sequence (email)

Generate a multi-email sequence with:

• Sequence type: Welcome (3-5 emails), Launch (5-7 emails), or Nurture (4-6 emails). Infer from context.
• For each email:
  • Subject line (under 50 characters) + 1 alternative subject line
  • Preview text (under 90 characters)
  • Email body (150-400 words) in plain text format with clear sections
  • CTA button text
  • Send timing (e.g., "Day 0: Immediately after signup", "Day 2: Morning")
• Sequence map: A table showing the full sequence with timing, subject, and goal per email
• A/B test suggestions: 2-3 elements worth split-testing across the sequence

---

Landing Page Copy (landing-page)

Generate structured copy blocks:

• Hero section: Headline (under 10 words), subheadline (under 25 words), CTA button text, supporting line
• Problem section: 3 pain points the audience feels
• Solution section: How the product/service solves each pain point
• Features section: 4-6 features with benefit-oriented descriptions (not feature lists)
• Social proof section: Suggested testimonial prompts, stats format, trust badges
• FAQ section: 5-7 anticipated objections phrased as questions with answers
• Final CTA section: Urgency-driven headline + CTA

Produce 2 variants: one benefit-led (emotional) and one proof-led (logical/data).

---

Newsletter (newsletter)

Generate a newsletter edition:

• Subject line + alternative subject line
• Preview text
• Opening commentary (100-200 words) — the curator's perspective on a trend or theme
• 3-5 curated items, each with:
  • Section headline
  • 2-3 sentence summary/commentary
  • Placeholder link: [Read more](URL: description of source)
  • Why it matters (1 sentence)
• Quick hits / links round-up: 3-5 one-liner links
• Closing CTA: Forward to a friend, reply, or visit link
• Consistent format template: Show the reusable skeleton the user can follow every edition

---

Product Description (product-description)

Generate product copy:

• Short description (under 50 words) for catalogs/cards
• Long description (150-300 words) for product pages
• Features-to-benefits table: Left column = feature, right column = what it means for the customer
• Comparison table (if competitor context is given): Product vs. alternative on 5-7 dimensions
• Objection handling: 3-5 "but what about..." answers embedded in copy
• Platform variants: Amazon listing style, Shopify product page style, and social ad style

Produce 2 variants with different positioning angles (e.g., premium vs. value, technical vs. lifestyle).

---

3. SEO Metadata (for all content types)

Append an SEO section at the bottom of every output:

## SEO Metadata
- **Primary keyword**: ...
- **Secondary keywords**: ..., ..., ...
- **Search intent**: informational / commercial / transactional / navigational
- **Suggested internal links**: 3-5 topic areas to link to/from

4. Distribution Schedule

Append a distribution/posting schedule:

## Distribution Schedule
| Channel       | Date/Time             | Content Variant | Notes                    |
|---------------|-----------------------|-----------------|--------------------------|
| Blog          | [suggested day]       | Full post       | Publish first            |
| Twitter/X     | [+1 day, morning]     | Thread variant  | Pin thread               |
| LinkedIn      | [+1 day, Tue/Wed AM]  | LinkedIn post   | Comment with extra value |
| Email list    | [+2 days]             | Newsletter link | Segment: engaged users   |
| Instagram     | [+3 days]             | Visual + caption| Stories for reach        |

Adjust the schedule based on which content types were actually generated. Only include channels relevant to the output.

5. Write Output Files

Save all generated content to organized files:

content/<type>/<YYYY-MM-DD>-<topic-slug>.md

Examples:

• content/blog/2026-03-24-remote-team-productivity.md
• content/social/2026-03-24-remote-team-productivity.md
• content/email/2026-03-24-welcome-sequence.md
• content/landing-page/2026-03-24-product-launch.md

Each file should include the frontmatter context (audience, goal, tone, keywords) at the top as YAML, followed by the full content.

If multiple types are generated, create one file per type.

6. Summary

After generating all content, print a summary:

## Content Summary
- Type(s): ...
- Topic: ...
- Audience: ...
- Tone: ...
- Files created: ...
- Variants generated: ...
- Next step: Review variants, pick winners, schedule distribution

7. Self-Healing Validation (max 2 iterations)

After generating content, validate:

1. All requested content types have substantive output (not just headers).
2. Each type has 2-3 variants as required.
3. SEO metadata section is present with real keywords (not placeholders).
4. Distribution schedule matches the content types actually generated.
5. Output files were written to content/ directory.

IF VALIDATION FAILS:

• Identify incomplete types or missing variants
• Regenerate deficient sections
• Repeat up to 2 iterations

8. Self-Evolution Telemetry

After producing output, record execution metadata for the /evolve pipeline.

Check if a project memory directory exists:

• Look for the project path in ~/.claude/projects/
• If found, append to skill-telemetry.md

Entry format:

### /content-creator -- {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Types generated: {{list}}
- Variants: {{count}}
- Self-healed: {{yes -- what was healed | no}}
- Iterations used: {{N}} / 2
- Bottleneck: {{type that struggled or "none"}}
- Suggestion: {{one-line improvement idea, or "none"}}

Only log if the memory directory exists. Skip silently if not found.