blog-post
Generates engaging blog posts from source materials or topic briefs. Supports listicles, tutorials, how-to guides, narrative essays, and thought leadership. Handles research, outlining, drafting, SEO optimization, and polishing. Use when writing a blog post, creating a listicle, turning research into an article, writing a tutorial, or asking "write a blog post about this."
What this skill does
# Blog Post
Research, draft, and polish publication-ready blog posts.
## Workflow
```text
Blog post progress:
- [ ] Step 1: Clarify topic and format
- [ ] Step 2: Research and gather sources
- [ ] Step 3: Extract key insights and outline
- [ ] Step 4: Write the post
- [ ] Step 5: SEO and polish
- [ ] Step 6: Validate quality
```
### Step 1: Clarify topic and format
Determine the post type before writing. Ask the user if unclear:
| Format | Best for | Structure |
|--------|----------|-----------|
| **Listicle** | Surprising takeaways from sources | Numbered insights with analysis |
| **Tutorial / how-to** | Teaching a process step by step | Problem → steps → result |
| **Narrative** | Personal experience or journey | Story arc with tension and resolution |
| **Thought leadership** | Industry commentary or opinion | Thesis → evidence → implications |
### Step 2: Research and gather sources
Read files, fetch URLs, or accept pasted text. If the user provides a topic without sources, research the topic before writing. Read every source completely before outlining.
Accept messy input — scattered thoughts, bullet points, brain dumps, random observations. The mess is the input; structure is the output.
### Step 3: Extract key insights and outline
- Identify the most surprising, counter-intuitive, or impactful takeaways.
- Rank insights by reader value — lead with the strongest.
- Select 2-4 powerful quotes for blockquotes (only the best).
- Find a relatable problem or curiosity gap to anchor the introduction.
- Check for narrative potential: is there a journey from one understanding to another?
Create a section outline before drafting. Each section should have a clear purpose.
### Step 4: Write the post
Load the matching template from [references/format-templates.md](references/format-templates.md) and follow its structure. Only load the template for the chosen format — not all four.
### Step 5: SEO and polish
- **Title**: under 60 characters, include the main keyword.
- **Meta description**: 150-160 characters summarizing the post's value.
- **Keyword placement**: naturally in the title, first paragraph, and 2-4 times throughout.
- **Headers**: descriptive H2/H3 tags that work as standalone scan points.
- **Internal links**: suggest 2-3 related links if the user has other content.
### Step 6: Validate quality
```text
Before finalizing, verify:
- [ ] Hook grabs attention in the first 1-2 sentences
- [ ] Headline is specific and delivers on its promise
- [ ] Every paragraph is 2-4 sentences maximum
- [ ] Each section has analysis or insight, not just summary
- [ ] Blockquotes are limited to 2-4 total
- [ ] Conclusion looks forward with a question, CTA, or provocative takeaway
- [ ] Tone is conversational throughout — no academic language
- [ ] Title is under 60 characters with the main keyword
- [ ] Post includes a meta description (150-160 chars)
- [ ] Markdown renders correctly (headings, blockquotes, bold, code)
```
## Blog-specific voice
- Write to a smart friend, not a committee. Authenticity beats authority.
- Bold key phrases for scannability — readers skim before they read.
- Show, don't tell: specific examples with real details beat vague claims.
- Admit uncertainty when genuine. Never bluff expertise.
## Headline patterns
- **Number + insight**: "7 Things [Sources] Reveal About [Topic]"
- **Surprising tension**: "Why [Common Belief] Gets [Topic] Wrong"
- **How-to framing**: "How to [Achieve Outcome] with [Method]"
- **Question format**: "What If [Provocative Reframe]?"
Under 60 characters for SEO. Sentence case, no trailing period. Must deliver on its promise.
## Anti-patterns
- Generic headlines ("Interesting Findings About X").
- Conclusions that just summarize what was already said.
- Clickbait headlines the content does not deliver on.
- Blockquoting every source instead of choosing the 2-4 most powerful.
- Skipping research and writing from assumptions.
## Skill handoffs
| When | Run |
|------|-----|
| After blog post is written, audit prose quality | `docs-writing` |
| If post needs to become a presentation | `presentation-creator` |
| Edit and polish the copy | `copy-editing` |
| Optimize SEO beyond basics | `optimise-seo` |
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".