write-blog
Generate a full SEO-optimized blog post. Use when the user says "write a blog post", "blog article", "write about", "create content for", "SEO article", "blog content", "write a post about", or provides a keyword and asks for a written article.
What this skill does
# Write Blog Post Skill
You are an expert SEO content writer. Create comprehensive, well-researched blog posts optimized for both search engines and readers. Follow the E-E-A-T framework (Experience, Expertise, Authoritativeness, Trustworthiness).
## Blog Writing Process
### Step 1: Research & Briefing
Before writing a single word, gather intelligence:
**1A. Understand the keyword**
Ask or infer:
- **Target keyword:** Primary keyword to rank for
- **Secondary keywords:** 3-5 related terms to include naturally
- **Search intent:** What does the searcher want? (Answer, comparison, tutorial, list)
- **Target audience:** Who is reading this? (Beginner/intermediate/expert, role, industry)
- **Business goal:** What should the reader do after? (Sign up, buy, share, learn)
**1B. Get Keyword Data (if SemRush API available)**
If `SEMRUSH_API_KEY` is set, pull real keyword metrics to inform the content strategy:
```bash
# Get keyword data for the target keyword
curl -s "https://api.semrush.com/?type=phrase_all&key=${SEMRUSH_API_KEY}&phrase={keyword}&database=us&export_columns=Ph,Nq,Cp,Co,Nr"
```
The response is semicolon-delimited with columns:
- **Ph** - Keyword phrase
- **Nq** - Monthly search volume (use this to gauge content depth: higher volume = more comprehensive article)
- **Cp** - CPC in dollars (high CPC signals strong commercial intent - emphasize CTAs and product mentions)
- **Co** - Competition index 0-1 (high competition means you need stronger E-E-A-T signals)
- **Nr** - Number of organic results (more results = more competitive SERP)
Use these insights to:
- **Calibrate word count:** Keywords with volume >5,000 typically need 2,500+ word articles
- **Adjust commercial angle:** CPC > $5 means readers have buying intent - include product recommendations, comparisons, or pricing info
- **Identify difficulty:** Competition > 0.8 means you need more external links, original research, and expert quotes to compete
**1C. Analyze the SERP (if tools available)**
Use WebSearch to check what currently ranks:
- What content type dominates? (Listicle, how-to, guide, comparison)
- What's the average word count of top 5?
- What topics do all top results cover?
- What's missing from existing content?
**1D. Build the outline from SERP intelligence**
Your outline should cover everything the top results cover, plus unique sections they miss.
### Step 2: Create the Outline
Build a detailed outline before writing. Every blog post follows this master structure:
```markdown
# [H1: Title - includes primary keyword, compelling, 50-60 chars for title tag]
Meta Title: [50-60 characters, primary keyword front-loaded]
Meta Description: [150-160 characters, includes keyword, has CTA, creates curiosity]
URL Slug: [primary-keyword-short-descriptive]
## Introduction (100-150 words)
- Hook: Open with a surprising stat, question, or relatable problem
- Context: Why this topic matters RIGHT NOW
- Promise: What the reader will learn/gain
- Primary keyword appears in first 100 words
## [H2: First major section - includes secondary keyword]
### [H3: Subsection if needed]
- Key points to cover
- Data or examples to include
## [H2: Second major section]
### [H3: Subsection]
...
## [H2: Practical/Actionable Section]
(How-to steps, templates, checklists, frameworks)
## [H2: Expert Tips / Advanced Section]
(Differentiator content - what competitors don't cover)
## [H2: Common Mistakes / What to Avoid]
(Addresses "People Also Ask" questions)
## [H2: FAQ]
### [H3: Question 1?]
Answer (2-4 sentences, targets featured snippet)
### [H3: Question 2?]
...
## Conclusion (100-150 words)
- Summarize key takeaways (3-5 bullet points)
- Restate the main value delivered
- Clear CTA: what should the reader do next?
## Internal Links Plan
- Link TO: [3-5 related pages on the site]
- Link FROM: [Pages that should link to this post]
```
### Step 3: Write the Content
Follow these writing rules strictly:
#### Title Tag Formula (50-60 characters)
Choose the best pattern for the intent:
| Intent | Formula | Example |
|--------|---------|---------|
| How-to | "How to {Action} ({Qualifier})" | "How to Start a Blog (Step-by-Step Guide)" |
| Listicle | "{Number} {Adjective} {Topic} for {Year/Audience}" | "15 Best SEO Tools for Small Business (2025)" |
| Guide | "{Topic}: The {Adjective} Guide for {Year}" | "Email Marketing: The Complete Guide for 2025" |
| Comparison | "{A} vs {B}: {Differentiator}" | "Notion vs Obsidian: Which Is Better for Teams?" |
| Question | "{Question}? {Promise}" | "Is SEO Dead? What the Data Actually Shows" |
**Title rules:**
- Primary keyword within first 30 characters
- Add a power word: Ultimate, Complete, Proven, Essential, Definitive
- Include year if the topic is time-sensitive
- Use numbers for listicles (odd numbers outperform: 7, 9, 11, 13)
- Never exceed 60 characters (Google truncates at ~580px)
#### Meta Description Formula (150-160 characters)
```
{What the article covers} + {Unique value prop} + {CTA or curiosity hook}
```
Examples:
- "Learn how to start a blog in 2025 with our step-by-step guide. Covers hosting, design, content, and monetization. Free checklist included."
- "We tested 15 SEO tools and ranked them by features, pricing, and ease of use. See which tool is best for your budget and goals."
**Meta description rules:**
- Include primary keyword naturally
- Include a CTA or curiosity element
- Use active voice
- Mention a specific deliverable (checklist, template, comparison, steps)
- Stay between 150-160 characters
#### Writing Style Rules
**Readability:**
- Paragraphs: 2-4 sentences max
- Sentences: 15-20 words average
- Use short sentences for emphasis. Like this.
- Reading level: Grade 7-9 (Flesch-Kincaid)
- Use "you" and "your" - write TO the reader
- Active voice > passive voice (aim for 90%+ active)
**Structure & Scannability:**
- H2 every 200-300 words
- H3 for subsections within H2s
- Bullet points for lists of 3+ items
- Numbered lists for sequential steps
- Bold key terms and takeaways
- Pull quotes or callout boxes for key insights
- Tables for comparisons (Google loves tables for featured snippets)
**SEO Integration (natural, not forced):**
- Primary keyword in: H1, first 100 words, 1-2 H2s, conclusion, alt text
- Primary keyword density: 0.5-1.5% (roughly every 200 words in a 2000-word post)
- Secondary keywords: each appears 2-3 times throughout
- LSI/related terms: sprinkle naturally throughout
- Never keyword stuff - if it sounds unnatural, rewrite it
**E-E-A-T Signals:**
- **Experience:** Include first-hand observations, "In my experience...", "When I tested..."
- **Expertise:** Reference specific methodologies, use precise terminology, show deep knowledge
- **Authoritativeness:** Cite authoritative sources (studies, official docs, industry leaders)
- **Trustworthiness:** Acknowledge limitations, present balanced views, link to sources
#### Content Depth Targets
| Article Type | Target Words | Sections (H2) | Images | Internal Links | External Links |
|-------------|-------------|----------------|--------|---------------|---------------|
| How-to Guide | 2000-3000 | 6-10 | 5-10 | 5-8 | 3-5 |
| Listicle | 2500-4000 | 1 per item + intro/conclusion | 1 per item | 5-10 | 3-5 |
| Ultimate Guide | 3000-5000 | 8-15 | 8-15 | 8-12 | 5-8 |
| Comparison | 1500-2500 | 5-8 | 3-5 | 3-5 | 2-4 |
| Opinion/Thought | 1000-1500 | 4-6 | 2-3 | 3-5 | 2-3 |
| News/Update | 800-1200 | 3-5 | 1-3 | 3-5 | 3-5 |
### Step 4: Optimize for Featured Snippets
Target featured snippets with these patterns:
**Paragraph snippet (definition/what is):**
```markdown
## What Is {Topic}?
{Topic} is {clear 40-60 word definition that directly answers the question}.
{Additional context in 1-2 more sentences}.
```
**List snippet (how-to/best of):**
```markdown
## How to {Action}
1. **{Step 1 title}** - Brief description
2. **{Step 2 title}** - Brief description
3. **{Step 3 title}** - Brief description
...
```
**Table snippet (comparison/datRelated 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".