# Blog Writer > Blog post creation covering outlines, SEO-optimized headlines, meta descriptions, content structures, and publication-ready drafting. This skill should be used when Cline needs to create blog posts from scratch — from outlining and headline generation through to full draft production with proper structure, SEO elements, and formatting. - Skill: `thearchitectit/blog-writer` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add thearchitectit/blog-writer` - Raw SKILL.md: https://api.skillmd.com/api/skills/thearchitectit/blog-writer/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Marketing & Growth - Author: TheArchitectit (https://skillmd.com/u/thearchitectit) - Updated: 2026-09-21 - Page: https://skillmd.com/skills/thearchitectit/blog-writer --- # Blog Writer This skill creates structured, publication-ready blog posts from scratch. It handles the full writing workflow: topic development, SEO headline generation, outline creation, meta description writing, section drafting, and final polish. Every output is optimized for readability, engagement, and search visibility. ## When to Use This Skill - Writing a complete blog post from a topic or brief - Creating blog post outlines with logical structure - Generating SEO-optimized headlines and title variants - Writing meta descriptions for search and social sharing - Drafting long-form content with proper section hierarchy - Creating listicles, how-to guides, comparisons, and opinion pieces - Repurposing existing content into blog format - Adding internal linking suggestions and call-to-action placement ## What This Skill Does 1. **Outline Generation**: Creates structured outlines with logical flow and section depth 2. **Headline Crafting**: Produces SEO-optimized, compelling headline variants 3. **Meta Description Writing**: Writes search-optimized summaries under 160 characters 4. **Full Draft Production**: Writes complete posts with proper formatting and structure 5. **SEO Integration**: Incorporates keyword targeting, header hierarchy, and readability optimization ## Process ### Step 1: Define the Blog Post Gather requirements before writing: ```markdown ## Blog Post Brief - **Topic**: [Main subject] - **Target audience**: [Who is this for?] - **Primary keyword**: [Main SEO target] - **Secondary keywords**: [Related terms to include] - **Post type**: [How-to / Listicle / Opinion / Comparison / Case Study / News] - **Target length**: [Word count goal] - **Tone**: [Professional / Conversational / Technical / Friendly / Authoritative] - **CTA**: [What should the reader do after?] - **Competitor references**: [Similar posts to differentiate from] - **Unique angle**: [What makes this post different?] ``` ### Step 2: Generate Headline Variants Create SEO-optimized headlines with multiple approaches: ```markdown ## Headline Options ### SEO-Focused (keyword-forward) 1. [Primary Keyword]: [Benefit/Promise] 2. How to [Achieve Outcome] with [Primary Keyword] 3. [Number] [Primary Keyword] Strategies for [Audience] ### Engagement-Focused (curiosity/emotion) 4. Why [Common Belief] About [Topic] Is Wrong 5. The [Topic] Mistake That's Costing You [Outcome] 6. What Nobody Tells You About [Primary Keyword] ### Listicle Format 7. [Number] [Primary Keyword] Tips That Actually Work ([Year]) 8. [Number] Ways to [Achieve Outcome] with [Primary Keyword] ### Comparison/Contrast 9. [Option A] vs [Option B]: Which Is Better for [Use Case]? 10. [Topic]: [Conventional Approach] vs [Better Approach] **Selection criteria**: - Primary keyword within first 60 characters - Clear value proposition for the reader - Specific over vague ("7 Strategies" > "Some Strategies") - Honest — don't overpromise ``` ### Step 3: Create the Outline Structure with proper hierarchy and word count allocation: ```markdown # Outline: [Selected Headline] **Target**: ~1,500 words | **Type**: How-to Guide ## Introduction (~150 words) - Hook: [Surprising stat / relatable problem / bold claim] - Problem statement - What this post covers - Who should read this ## Section 1: [First Major Point] (~300 words) ### What is [Concept]? - Definition in plain language - Why it matters for [audience] - Common misconception ### How to [First Step] - Step-by-step instructions - Example or case study - Common pitfall to avoid ## Section 2: [Second Major Point] (~300 words) - Builds on Section 1 - Introduces [next concept] - Practical application ## Section 3: [Third Major Point] (~300 words) - Advanced or nuanced aspect - Data/evidence supporting this point - Actionable takeaway ## Pro Tips / Best Practices (~200 words) - 3-5 quick actionable tips - Bonus advice from experience ## Conclusion (~150 words) - Summarize key takeaways (2-3 bullet points) - Reiterate main benefit - Call to action ## SEO Elements - **Primary keyword**: [keyword] — used in H1, first paragraph, 2-3 more times - **Secondary keywords**: [list] — naturally distributed - **Internal link suggestions**: [related content to link to] - **Image/visual suggestions**: [what diagrams or images would help] ``` ### Step 4: Write Meta Description ```markdown ## Meta Description Options **Option 1** (Benefit-focused): Learn [what/why/how] with [approach]. Discover [outcomes] in this [post type] covering [key topics]. [CTA implication]. **Option 2** (Problem-focused): Struggling with [common problem]? This guide covers [solutions] to help you [achieve outcome]. [CTA implication]. **Selection rules**: - Under 155 characters for full SERP display - Include primary keyword near the start - Include a reason to click (benefit, curiosity, urgency) - Match the tone of the post - No clickbait — deliver on the promise ``` ### Step 5: Draft the Post Write following the outline with proper formatting: ```markdown # [Headline] [Meta: meta-description-text] [Target keyword: primary-keyword] --- [Introduction — hook, problem, promise, roadmap] ## [Section 1 H2] [Content with short paragraphs (2-3 sentences max for web readability)] [Use **bold** for key terms, not excessive emphasis] > Pull quote for key insight or statistic — breaks up text visually ### [Subsection H3] [Bullet points for lists — scannable content:] - Point one with brief explanation - Point two with brief explanation - Point three with brief explanation [Code blocks for technical content:] ```python # Example code if applicable ``` [Transition to next section — connect the dots] ## [Section 2 H2] [Continue pattern: short paragraphs, varied formatting, visual breaks] | Column A | Column B | Column C | |----------|----------|----------| | Data | Comparison | Table | ## [Section N H2] [Final substantive section before conclusion] --- ## Key Takeaways - **[Takeaway 1]**: [Brief explanation] - **[Takeaway 2]**: [Brief explanation] - **[Takeaway 3]**: [Brief explanation] ## Ready to [Take Action]? [Call to action — what should the reader do next?] [Link to relevant resource, product, or next steps] ``` ### Step 6: Polish and Optimize Review checklist before publishing: ```markdown ## Pre-Publish Checklist ### SEO - [ ] Primary keyword in H1, first paragraph, and 2-3 additional times - [ ] Secondary keywords distributed naturally throughout - [ ] Meta description under 155 characters with primary keyword - [ ] Header hierarchy correct (H1 → H2 → H3, no skipped levels) - [ ] Image alt text suggestions provided - [ ] Internal linking opportunities identified ### Readability - [ ] Paragraphs are 2-3 sentences for web scanning - [ ] No walls of text — visual variety (lists, quotes, tables, code) - [ ] Transitions between sections are smooth - [ ] Jargon explained or linked - [ ] Active voice preferred over passive ### Content Quality - [ ] Opening hook creates curiosity or resonance - [ ] Each section delivers on the headline's promise - [ ] Examples and evidence support claims - [ ] No filler — every paragraph earns its place - [ ] CTA is clear and relevant ### Technical - [ ] Word count within 10% of target - [ ] No broken markdown formatting - [ ] Links are described (not "click here") - [ ] Consistent formatting throughout ``` ## Blog Post Types ### How-To Guide Structure: Problem → Prerequisites → Steps → Verification → Troubleshooting Tone: Instructional, encouraging Length: 1,500-2,500 words ### Listicle Structure: Intro → Numbered items with consistent depth → Summary Tone: Scannable, varied (mix serious and fun items) Length: 1,000-2,000 words (50-150 words per item) ### Opinion / Thought Leadership Structure: Bold thesis → Supporting arguments → Counter-argument → Conclusion Tone: Confident, thoughtful, slightly provocative Length: 800-1,500 words ### Comparison Structure: Context → Criteria → Side-by-side analysis → Verdict Tone: Objective, fair, decisive Length: 1,500-2,500 words ### Case Study Structure: Challenge → Approach → Results → Lessons learned Tone: Factual, evidence-based, specific Length: 1,000-2,000 words ## Error Handling - **Topic too broad**: Narrow scope to one specific angle; suggest breaking into series - **Insufficient word count**: Add examples, expand explanations, include a practical exercise - **Keyword stuffing detected**: Re-write with natural language; keywords should feel organic - **Weak conclusion**: End with actionable takeaways, not a generic summary - **Missing voice**: Ask for existing writing samples; match tone rather than defaulting to generic ## Common Pitfalls - ❌ Writing for search engines instead of humans — read it aloud; if it sounds robotic, rewrite - ❌ Burying the lede — the key point must appear in the first 2 paragraphs - ❌ Overusing subheadings — H2s every 200-300 words is plenty - ❌ Forgetting the CTA — every blog post should lead somewhere - ❌ Generic stock advice — be specific with examples, data, and real scenarios ## Cline Workflow Notes 1. **Install location**: Copy this skill directory to `.cline/skills/blog-writer/` (project-level) or `~/.cline/skills/blog-writer/` (global) 2. **Always start with a brief**: Even a minimal brief produces better results than no brief 3. **Headlines first**: Generate headline options before writing — the headline shapes everything 4. **Save versions**: Keep outline, draft-v1, and final as separate files 5. **Match existing voice**: If the user has a blog, read existing posts to match their style 6. **SEO awareness**: Include keyword and meta elements, but never sacrifice readability for SEO 7. **Content over format**: The writing quality matters more than template perfection ## Dependencies No external dependencies required. This skill uses Cline's native writing capabilities.