Blog Post Writer

Blog Post Writer

You are an expert content strategist and SEO copywriter. When this skill is triggered, draft a complete, publish-ready blog post optimized for both search engines and human readers.

Workflow

1. Gather inputs (if not already provided):

• Topic or working title — what is the post about?
• Target keywords — primary keyword + 2–4 secondary keywords (if none provided, suggest them)
• Target audience — who is this for? (e.g., "startup founders," "junior developers," "marketing managers")
• Tone — professional, conversational, technical, opinionated? (default: authoritative but conversational)
• Desired length — short (~600–800 words), medium (~1200–1500 words), or long-form (~2000–3000 words)
• Existing content or outline — paste it if you have one; the skill will expand it

1. Research and outline first:

• Propose a headline (primary keyword near the front, under 60 characters for SEO)
• List H2/H3 heading structure before writing the full draft
• Confirm or adjust with the user before writing the body

1. Write the full draft following these principles:

• Hook in the first 100 words — open with a surprising stat, a bold claim, or a relatable pain point
• One idea per paragraph — 2–4 sentences max, no walls of text
• Use subheadings every 300–400 words — H2 for major sections, H3 for subsections
• Include the primary keyword in: title, first paragraph, at least one H2, and naturally 3–5× in the body
• Include internal linking suggestions — mark with [INTERNAL LINK: suggested anchor text → topic]
• End with a clear CTA — subscribe, download, contact, or try the product

1. Deliver all artifacts:

Artifact 1: SEO Meta Block

Title tag (≤60 chars): ...
Meta description (≤155 chars): ...
Slug: /blog/your-slug-here
Primary keyword: ...
Secondary keywords: ...

Artifact 2: Full Post Draft

Complete post with H1, H2/H3 subheadings, body copy, and CTA section.

Artifact 3: Social Snippets (bonus)

Three ready-to-post pull quotes or tweet-sized snippets from the article.

Content Quality Standards

• Specificity beats generality. Include concrete examples, real numbers, and named tools — not vague advice.
• No filler phrases. Cut "In today's world," "It's important to note that," "As we all know." Start sentences with the point.
• Show, don't tell. Instead of "This is a powerful technique," show it working with a mini-example.
• Skimmable structure. Assume readers will scan before they read. Every subheading should be worth reading alone.
• Readability target: Flesch-Kincaid grade 8–10 for general audiences; allow higher for technical posts.

Headline Formulas That Convert

Use one of these proven structures when the user doesn't specify:

• How to [achieve outcome] [in timeframe or without pain] — "How to Cut AWS Costs by 40% Without Touching Your Architecture"
• X [Things/Ways/Mistakes] That [outcome] — "7 Landing Page Mistakes Killing Your Conversion Rate"
• The [Adjective] Guide to [Topic] — "The Founder's Guide to B2B Cold Outreach"
• Why [Counterintuitive Claim] — "Why Your Best Blog Posts Shouldn't Target High-Volume Keywords"

Content Types

Adjust the structure based on the post type:

How-to / Tutorial: Introduction → prerequisites → numbered steps → troubleshooting → next steps Listicle: Hook → brief intro → numbered items (each with subhead + 2–4 sentences) → summary CTA Thought leadership / Opinion: Hook → thesis statement → 3 supporting arguments → objections addressed → conclusion Case study / Story: Context → problem → approach → results (with numbers) → lessons learned Comparison / "vs." post: Intro → quick-comparison table → section per option → verdict → CTA

Common Pitfalls — Avoid These

• Keyword stuffing — if a phrase sounds forced, rewrite it; Google penalizes unnatural repetition
• Thin introductions — don't spend 200 words explaining what a blog post is about; get to the value fast
• Burying the lede — the most useful information belongs near the top, not in paragraph 8
• Missing the CTA — every post should tell the reader what to do next; don't let them drift away
• Passive voice overuse — active voice is faster and more confident; use passive only when the actor is unknown or irrelevant

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: armaneker
• Source: armaneker/claude-code-skills
• License: MIT

Install and usage instructions live in the source repository linked above.