{
  "schema": "https://ai-atoms.com/schemas/skill-v1.json",
  "type": "skill",
  "id": "skill/draft-content",
  "version": "1.0.0",
  "name": "draft-content",
  "description": "Draft blog posts, social media, email newsletters, landing pages, press releases, and case studies with channel-specific formatting and SEO recommendations. Use when writing any marketing content, when you need headline or subject line options, or when adapting a message for a specific platform, audience, and brand voice.",
  "system_prompt_fragment": "# Draft Content\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).\n\nGenerate marketing content drafts tailored to a specific content type, audience, and brand voice.\n\n## Trigger\n\nUser runs `/draft-content` or asks to draft, write, or create marketing content.\n\n## Inputs\n\nGather the following from the user. If not provided, ask before proceeding:\n\n1. **Content type** — one of:\n   - Blog post\n   - Social media post (specify platform: LinkedIn, Twitter/X, Instagram, Facebook)\n   - Email newsletter\n   - Landing page copy\n   - Press release\n   - Case study\n\n2. **Topic** — the subject or theme of the content\n\n3. **Target audience** — who this content is for (role, industry, seniority, pain points)\n\n4. **Key messages** — 2-4 main points or takeaways to communicate\n\n5. **Tone** — e.g., authoritative, conversational, inspirational, technical, witty (optional if brand voice is configured)\n\n6. **Length** — target word count or format constraint (e.g., \"1000 words\", \"280 characters\", \"3 paragraphs\")\n\n## Brand Voice\n\n- If the user has a brand voice configured in their local settings file, apply it automatically. Inform the user that brand voice settings are being applied.\n- If no brand voice is configured, ask: \"Do you have brand voice guidelines you'd like me to follow? If not, I'll use a neutral professional tone.\"\n- Apply the specified or default tone consistently throughout the draft.\n\n## Content Generation by Type\n\n### Blog Post\n- Engaging headline (provide 2-3 options)\n- Introduction with a hook (question, statistic, bold statement, or story)\n- 3-5 organized sections with descriptive subheadings\n- Supporting points, examples, or data references in each section\n- Conclusion with a clear call to action\n- SEO considerations: suggest a primary keyword, include it in the headline and first paragraph, use related keywords in subheadings\n\n### Social Media Post\n- Platform-appropriate format and length\n- Hook in the first line\n- Hashtag suggestions (3-5 relevant hashtags)\n- Call to action or engagement prompt\n- Emoji usage appropriate to brand and platform\n- If LinkedIn: professional framing, paragraph breaks for readability\n- If Twitter/X: concise, punchy, within character limit\n- If Instagram: visual-first language, story-driven, hashtag block\n\n### Email Newsletter\n- Subject line (provide 2-3 options with open-rate considerations)\n- Preview text\n- Greeting\n- Body sections with clear hierarchy\n- Call to action button text\n- Sign-off\n- Unsubscribe note reminder\n\n### Landing Page Copy\n- Headline and subheadline\n- Hero section copy\n- Value propositions (3-4 benefit-driven bullets or sections)\n- Social proof placeholder (suggest testimonial or stat placement)\n- Primary and secondary CTAs\n- FAQ section suggestions\n- SEO: meta title and meta description suggestions\n\n### Press Release\n- Headline following press release conventions\n- Dateline and location\n- Lead paragraph (who, what, when, where, why)\n- Supporting quotes (provide placeholder guidance)\n- Company boilerplate placeholder\n- Media contact placeholder\n- Standard press release formatting\n\n### Case Study\n- Title emphasizing the result\n- Customer overview (industry, size, challenge)\n- Challenge section\n- Solution section (what was implemented)\n- Results section with metrics (prompt user for data)\n- Customer quote placeholder\n- Call to action\n\n## SEO Considerations (for web content)\n\nFor blog posts, landing pages, and other web-facing content:\n- Suggest a primary keyword based on the topic\n- Recommend keyword placement: headline, first paragraph, subheadings, meta description\n- Suggest internal and external linking opportunities\n- Recommend a meta description (under 160 characters)\n- Note image alt text opportunities\n\n## Output\n\nPresent the draft with clear formatting. After the draft, include:\n- A brief note on what brand voice and tone were applied\n- Any SEO recommendations (for web content)\n- Suggestions for next steps (e.g., \"Review with your team\", \"Add customer quotes\", \"Pair with a visual\")\n\nAsk: \"Would you like me to revise any section, adjust the tone, or create a variation for a different channel?\"",
  "applicable_domains": [
    "marketing",
    "content"
  ],
  "invocation": [
    "/draft-content",
    "/draft-content <content type and topic>"
  ],
  "tags": [
    "marketing",
    "anthropics",
    "knowledge-work"
  ],
  "authored_by": "anthropics",
  "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/marketing/skills/draft-content/SKILL.md",
  "lifecycle": "stable",
  "category": "marketing",
  "provenance": {
    "source": "anthropics/knowledge-work-plugins",
    "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/marketing/skills/draft-content/SKILL.md",
    "author": "Anthropic",
    "license": "Apache-2.0",
    "notes": "Imported by scripts/import-anthropic-skills.py."
  }
}