draft-content
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.
What this skill does
# Draft Content > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Generate marketing content drafts tailored to a specific content type, audience, and brand voice. ## Trigger User runs `/draft-content` or asks to draft, write, or create marketing content. ## Inputs Gather the following from the user. If not provided, ask before proceeding: 1. **Content type** — one of: - Blog post - Social media post (specify platform: LinkedIn, Twitter/X, Instagram, Facebook) - Email newsletter - Landing page copy - Press release - Case study 2. **Topic** — the subject or theme of the content 3. **Target audience** — who this content is for (role, industry, seniority, pain points) 4. **Key messages** — 2-4 main points or takeaways to communicate 5. **Tone** — e.g., authoritative, conversational, inspirational, technical, witty (optional if brand voice is configured) 6. **Length** — target word count or format constraint (e.g., "1000 words", "280 characters", "3 paragraphs") ## Brand Voice - 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. - 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." - Apply the specified or default tone consistently throughout the draft. ## Content Generation by Type ### Blog Post - Engaging headline (provide 2-3 options) - Introduction with a hook (question, statistic, bold statement, or story) - 3-5 organized sections with descriptive subheadings - Supporting points, examples, or data references in each section - Conclusion with a clear call to action - SEO considerations: suggest a primary keyword, include it in the headline and first paragraph, use related keywords in subheadings ### Social Media Post - Platform-appropriate format and length - Hook in the first line - Hashtag suggestions (3-5 relevant hashtags) - Call to action or engagement prompt - Emoji usage appropriate to brand and platform - If LinkedIn: professional framing, paragraph breaks for readability - If Twitter/X: concise, punchy, within character limit - If Instagram: visual-first language, story-driven, hashtag block ### Email Newsletter - Subject line (provide 2-3 options with open-rate considerations) - Preview text - Greeting - Body sections with clear hierarchy - Call to action button text - Sign-off - Unsubscribe note reminder ### Landing Page Copy - Headline and subheadline - Hero section copy - Value propositions (3-4 benefit-driven bullets or sections) - Social proof placeholder (suggest testimonial or stat placement) - Primary and secondary CTAs - FAQ section suggestions - SEO: meta title and meta description suggestions ### Press Release - Headline following press release conventions - Dateline and location - Lead paragraph (who, what, when, where, why) - Supporting quotes (provide placeholder guidance) - Company boilerplate placeholder - Media contact placeholder - Standard press release formatting ### Case Study - Title emphasizing the result - Customer overview (industry, size, challenge) - Challenge section - Solution section (what was implemented) - Results section with metrics (prompt user for data) - Customer quote placeholder - Call to action ## SEO Considerations (for web content) For blog posts, landing pages, and other web-facing content: - Suggest a primary keyword based on the topic - Recommend keyword placement: headline, first paragraph, subheadings, meta description - Suggest internal and external linking opportunities - Recommend a meta description (under 160 characters) - Note image alt text opportunities ## Output Present the draft with clear formatting. After the draft, include: - A brief note on what brand voice and tone were applied - Any SEO recommendations (for web content) - Suggestions for next steps (e.g., "Review with your team", "Add customer quotes", "Pair with a visual") Ask: "Would you like me to revise any section, adjust the tone, or create a variation for a different channel?"
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".