blog

What this skill does

# Blog: Content Engine for Rankings & AI Citations

Full-lifecycle blog management: strategy, briefs, outlines, writing, analysis,
optimization, schema generation, repurposing, and editorial planning. Dual-optimized
for Google's December 2025 Core Update and AI citation platforms (ChatGPT,
Perplexity, Google AI Overviews, Gemini).

## Quick Reference

| Command | What it does |
|---------|-------------|
| `/blog write <topic>` | Write a new blog post from scratch |
| `/blog rewrite <file>` | Rewrite/optimize an existing blog post |
| `/blog analyze <file-or-url>` | Audit blog quality with 0-100 score |
| `/blog brief <topic>` | Generate a detailed content brief |
| `/blog calendar [monthly\|quarterly]` | Generate an editorial calendar |
| `/blog strategy <niche>` | Blog strategy and topic ideation |
| `/blog outline <topic>` | Generate SERP-informed content outline |
| `/blog seo-check <file>` | Post-writing SEO validation checklist |
| `/blog schema <file>` | Generate JSON-LD schema markup |
| `/blog repurpose <file>` | Repurpose content for other platforms |
| `/blog geo <file>` | AI citation readiness audit |
| `/blog audit [directory]` | Full-site blog health assessment |
| `/blog cannibalization [dir]` | Detect keyword cannibalization across posts |
| `/blog factcheck <file>` | Verify statistics against cited sources |
| `/blog image [generate\|edit\|setup]` | AI image generation and editing via Gemini |
| `/blog persona [create\|list\|use\|show]` | Manage writing personas and voice profiles |
| `/blog brand [init\|show\|update]` | Generate BRAND.md + VOICE.md context files auto-loaded by all sub-skills |
| `/blog discourse <topic>` | Research what people are actually saying about a topic in last 30 days; produces DISCOURSE.md (v1.8.0, API-free) |
| `/blog taxonomy [suggest\|sync\|audit]` | Tag/category management across CMS platforms |
| `/blog notebooklm <question>` | Query NotebookLM for source-grounded research |
| `/blog audio [generate\|voices\|setup]` | Generate audio narration of blog posts |
| `/blog google [command] [args]` | Google API data: PSI, CrUX, GSC, GA4, NLP, YouTube, Keywords |
| `/blog update <file>` | Update existing post with fresh stats (routes to rewrite) |
| `/blog cluster [plan\|execute] <seed-or-plan>` | Semantic topic-cluster planning + execution (hub and spoke) |
| `/blog multilingual <topic> --languages <codes>` | Write + translate + localize + emit hreflang in one command |
| `/blog translate <file> --to <codes>` | SEO-optimized translation with format preservation |
| `/blog localize <file> --locale <code>` | Cultural deep-adaptation (DACH, FR, ES, JA, custom) |
| `/blog locale-audit <directory>` | Multilingual content QA (completeness, hreflang, parity, freshness) |
| `/blog flow [find\|optimize\|win\|prompts\|sync]` | FLOW framework prompts (evidence-led, 30 blog-applicable) |

## Orchestration Logic

### Command Routing

1. Parse the user's command to determine the sub-skill
2. If no sub-command given, ask which action they need
3. Route to the appropriate sub-skill:
   - `write` → `blog-write` (new articles from scratch)
   - `rewrite` → `blog-rewrite` (optimize existing posts)
   - `analyze` → `blog-analyze` (quality scoring)
   - `brief` → `blog-brief` (content briefs)
   - `calendar` / `plan` → `blog-calendar` (editorial calendars)
   - `cannibalization` → `blog-cannibalization` (keyword overlap detection)
   - `factcheck` → `blog-factcheck` (statistics and source verification)
   - `strategy` / `ideation` → `blog-strategy` (positioning and topics)
   - `outline` → `blog-outline` (SERP-informed outlines)
   - `persona` → `blog-persona` (writing voice and style management)
   - `brand` → `blog-brand` (durable brand + voice context for cross-skill consumption)
   - `discourse` / `voice-of-customer` / `social-listening` / `trend-research` → `blog-discourse` (last-30-days API-free discourse research)
   - `seo-check` / `seo` → `blog-seo-check` (SEO validation)
   - `schema` → `blog-schema` (JSON-LD generation)
   - `repurpose` → `blog-repurpose` (cross-platform content)
   - `taxonomy` → `blog-taxonomy` (tags, categories, CMS sync)
   - `geo` / `aeo` / `citation` → `blog-geo` (AI citation audit)
   - `audit` / `health` → `blog-audit` (site-wide assessment)
   - `image` → `blog-image` (AI image generation and editing)
   - `notebooklm` / `notebook` / `query-notebook` → `blog-notebooklm` (source-grounded notebook queries)
   - `audio` / `narrate` / `tts` → `blog-audio` (audio narration generation)
   - `google` / `gsc` / `psi` / `pagespeed` / `crux` / `cwv` → `blog-google` (Google API data and reports)
   - `update` → `blog-rewrite` (with freshness-update mode)
   - `cluster` / `topic-cluster` / `pillar` / `hub-and-spoke` → `blog-cluster` (semantic clustering + execution)
   - `multilingual` / `international` → `blog-multilingual` (write + translate + localize + hreflang)
   - `translate` → `blog-translate` (SEO-optimized translation)
   - `localize` / `cultural-adaptation` → `blog-localize` (cultural deep-adaptation)
   - `locale-audit` / `translation-audit` → `blog-locale-audit` (multilingual QA)
   - `flow` / `find-leverage-optimize-win` → `blog-flow` (FLOW framework prompts)

### Platform Detection

Detect blog platform from file extension and project structure:

| Signal | Platform | Format |
|--------|----------|--------|
| `.mdx` files, `next.config` | Next.js/MDX | JSX-compatible markdown |
| `.md` files, `hugo.toml` | Hugo | Standard markdown |
| `.md` files, `_config.yml` | Jekyll | Standard markdown with YAML front matter |
| `.html` files | Static HTML | HTML with semantic markup |
| `wp-content/` directory | WordPress | HTML or Gutenberg blocks |
| `ghost/` or Ghost API | Ghost | Mobiledoc or HTML |
| `.astro` files | Astro | MDX or markdown |
| `.njk` files, `.eleventy.js` | 11ty | Nunjucks/Markdown |
| `gatsby-config.js` | Gatsby | MDX/React |

Adapt output format to detected platform. Default to standard markdown if unknown.

## Core Methodology: The 6 Pillars

Every blog post targets these 6 optimization pillars:

| Pillar | Impact | Implementation |
|--------|--------|---------------|
| Answer-First Formatting | Strong AI citation lift | Every H2 opens with 40-60 word stat-rich paragraph |
| Real Sourced Data | E-E-A-T trust | Tier 1-3 sources only, inline attribution |
| Visual Media | Engagement + citations | Pixabay/Unsplash images + AI generation via Gemini + built-in SVG charts + YouTube video embeds |
| FAQ Schema | AI citation signal | Structured FAQ with 40-60 word answers |
| Content Structure | AI extractability | 50-150 word chunks, question headings, proper H hierarchy |
| Freshness Signals | 76% of top citations | Updated within 30 days, dateModified schema |

### How the 6 Pillars map to the FLOW framework (v1.7.0)

claude-blog adopts the FLOW evidence-led model (`github.com/AgriciDaniel/flow`, CC BY 4.0). The 6 Pillars stay as-is; they become the operational expression of FLOW's principles. Mapping:

| Pillar | FLOW concept it implements | claude-blog adds beyond FLOW |
|--------|---------------------------|------------------------------|
| Answer-First Formatting | "Extraction-readable" passages for AI Overviews and assistant citations | Concrete 40-60 word format spec |
| Real Sourced Data | The FLOW evidence triple: year anchor in prose + inline citation (publisher + title) + URL with retrieval date | Tier 1-3 source classification, `blog-factcheck` automation |
| Visual Media | (Outside FLOW scope; FLOW is asset-agnostic) | Full pipeline: Gemini image gen, SVG charts, stock libraries, YouTube embeds |
| FAQ Schema | Structured Q&A as an AI-citation surface signal | JSON-LD generation via `blog-schema` |
| Content Structure | "AI-readable document" with clear headings, direct answers, source labels | 50-150 word chunk rule, proper H hierarchy enforcement |
| Freshness Signals | Year anchor in prose; source retrieval dates | dateModified schema, 30-day freshness threshold, `