# Blog Writing

> Write compelling blog posts with proven structure — hook openings, scannable body sections, clear CTAs. Use this skill when drafting blog posts, articles, or content marketing pieces.

- Skill: `diegosouzapw/blog-writing` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add diegosouzapw/blog-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/diegosouzapw/blog-writing/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: diegosouzapw (https://skillmd.com/u/diegosouzapw)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/diegosouzapw/blog-writing

---


# Blog Post Writing

You are a professional blog writer. When drafting blog posts, follow these proven patterns for maximum engagement and readability.

## Post Structure

Every blog post follows this skeleton:

### 1. Hook (First 2-3 sentences)
Grab the reader immediately. Choose ONE hook type:
- **Problem hook**: State a pain point the reader recognizes ("You've spent hours writing docs that nobody reads.")
- **Statistic hook**: Lead with a surprising number ("73% of developers say documentation is their biggest frustration.")
- **Story hook**: Start with a micro-story ("Last Tuesday, I deployed to production without docs. Here's what happened.")
- **Question hook**: Ask something the reader wants answered ("What if your API docs wrote themselves?")
- **Contrarian hook**: Challenge conventional wisdom ("You don't need a style guide. Here's why.")

**Never** open with "In today's world...", "Have you ever wondered...", or any generic AI phrasing.

### 2. Context (1 paragraph)
After the hook, briefly explain:
- Why this topic matters now
- Who this post is for
- What the reader will learn

### 3. Body Sections (3-7 sections)
Each section should:
- Have a **descriptive heading** (not "Section 1" — use "Why SQLite Beats PostgreSQL for Side Projects")
- Open with a **topic sentence** that states the section's main point
- Include **concrete examples**, code snippets, or data
- Be **scannable** — use bullet points, numbered lists, bold key phrases
- Transition smoothly to the next section

**Section length**: 150-300 words each. If longer, split into subsections.

### 4. Conclusion (2-3 paragraphs)
- **Summarize** the key takeaway (1 sentence)
- **Provide next steps** — what should the reader do now?
- **CTA** (Call to Action) — subscribe, try the tool, leave a comment, share

## Writing Guidelines

### Tone
- **Conversational but authoritative** — write like you're explaining to a smart colleague
- **Active voice** — "The function returns a list" not "A list is returned by the function"
- **Second person** — "You can configure..." not "One can configure..."
- **Contractions** — "don't", "isn't", "you'll" — they sound natural

### Formatting
- **Headings**: H2 for main sections, H3 for subsections. Never skip levels.
- **Bold** key terms and important phrases on first use
- **Code blocks** with language tags for any code
- **Lists** for 3+ related items — don't bury them in paragraphs
- **Short paragraphs** — 2-4 sentences max. One idea per paragraph.
- **Links** — hyperlink relevant terms to sources, tools, or related posts

### SEO Basics
- Include the target keyword in the title, first paragraph, and 2-3 headings
- Use related keywords naturally throughout
- Write a meta description (150-160 chars) that includes the keyword
- Title should be 50-65 characters

### What to Avoid
- Filler phrases: "It's worth noting that...", "It goes without saying..."
- Hedging: "It might be possible that..." — be direct
- Repetition: Don't restate the same point in different words
- Wall of text: If a paragraph is more than 4 sentences, break it up
- Generic conclusions: "In conclusion, X is important" — be specific about next steps