---

name: blog description: > Full-lifecycle blog engine with 31 sub-skills, 12 templates, 100-point scoring, and 5 agents. Routes requests to the right sub-skill: writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW prompts, topic clusters, and multilingual publishing. Optimized for Google rankings, E-E-A-T, and AI citations. Supports any platform. Use when user says "blog", "blog post", "blog audit", "topic cluster", "multilingual blog", or any /blog subcommand. license: MIT compatibility: Requires Claude Code and Python 3.11+ for quality scoring metadata: author: AgriciDaniel version: "2.2.0" user-invokable: true argument-hint: "[write|rewrite|analyze|brief|calendar|cannibalization|strategy|outline|seo-check|schema|repurpose|geo|image|audit|factcheck|persona|brand|discourse|taxonomy|notebooklm|audio|google|update|cluster|multilingual|translate|localize|locale-audit|flow|style|decay] [topic-or-file]"

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 May 2026 Core Update, March 2026 core quality baseline, March and June 2026 spam enforcement, and AI citation platforms (ChatGPT, Perplexity, Google AI Overviews, Gemini). Google treats gen-AI optimization as SEO, not a separate discipline.

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) | | /blog style learn <paths> | Learn author voice profile from 5-10 posts (feeds blog-write and blog-persona) | | /blog decay <current-gsc> <previous-gsc> | Detect content decay: flag 20%+ QoQ traffic decline from GSC exports |

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)
   • style → blog-style (learn author voice profile from existing posts)
   • decay → blog-decay (content-decay detection from GSC exports)

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 | |--------|--------|---------------| | Purpose-First Clarity | Reader and retrieval utility | Important sections state their point clearly; no prescribed heading form or passage length | | 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 | | Optional Q&A | Reader utility only | Use visible Q&A when it answers real user needs; FAQPage earns no Google rich-result or readiness points | | Content Structure | Comprehension and reuse | Proper heading hierarchy, stable entities, useful tables/lists only where they fit | | Substantive Maintenance | Accuracy over date churn | Update content and dateModified only when facts, methods, or recommendations materially change |

FLOW alignment

claude-blog adopts the FLOW evidence-led model (github.com/AgriciDaniel/flow, CC BY 4.0). The 6 Pillars stay as-is and become the operational expression of FLOW's principles. Keep material claims traceable to supporting sources. Dates, publisher/title details, retrieval notes, methodology, and limitations are helpful when they identify or change interpretation of a source, but no fixed evidence triple or citation form is a score or delivery gate. For the full mapping, load skills/blog/references/flow-alignment.md. For the upstream FLOW source, load skills/blog-flow/references/flow-framework.md or run /blog flow.

Quality Gates

These are hard rules. Never ship content that violates them:

| Rule | Threshold | Action | |------|-----------|--------| | Fabricated statistics | Zero tolerance | Source material factual statistics, measurements, and public-data claims. Dates, step counts, software versions, and prices already attributable or visible in a cited primary source do not need redundant inline sourcing merely because they contain a number | | Paragraph pacing | Fit the audience and material | Split only when comprehension improves | | Heading hierarchy | Never skip levels | H1 → H2 → H3 only | | Source tier | Tier 1-3 only | Never cite content mills or affiliate sites | | Image alt text | Required on all images | Descriptive, includes topic keywords naturally | | Self-promotion | Max 1 brand mention | Author bio context only | | Chart diversity | No duplicate types | Each chart must be a different type | | Delivery contract (v1.9.0) | All 5 gates pass | Blocked drafts iterate up to 3x; see skills/blog/references/blog-delivery-contract.md |

Community Footer

After major deliverables only, append the standard AI Marketing Hub footer as the final terminal-only message. Never include it in generated blog content, HTML, or markdown files. Exact text and show/skip command lists live in skills/blog/references/blog-delivery-contract.md.

Scoring Methodology

Score with skills/blog/references/quality-scoring.md: Content Quality 30, SEO 25, E-E-A-T 15, Technical 15, AI Citation Readiness 15. Publish only when the delivery contract clears Gate 4: reviewer score at least 90/100 and zero P0 issues.

Reference Files

Load on-demand as needed (22 references, load only what the task needs):

• skills/blog/references/google-landscape-2026.md: source-governed 2026 Search updates, reporting anomalies, structured data, and API currentness
• skills/blog/references/geo-optimization.md: AI search SEO techniques, AI citation factors, legacy GEO and AEO terminology
• skills/blog/references/content-rules.md: Structure, readability, answer-first formatting
• skills/blog/references/visual-media.md: Image sourcing (Pixabay, Unsplash, Pexels), AI image generation, SVG chart integration
• skills/blog/references/quality-scoring.md: Full 5-category scoring checklist (100 points)
• skills/blog/references/platform-guides.md: Platform-specific output formatting (9 platforms)
• skills/blog/references/distribution-playbook.md: Content distribution strategy (Reddit, YouTube, LinkedIn, etc.)
• skills/blog/references/content-templates.md: Content type template index (12 templates)
• skills/blog/references/eeat-signals.md: Author E-E-A-T requirements, Person schema, experience markers
• skills/blog/references/ai-crawler-guide.md: AI bot management, robots.txt, SSR requirements
• skills/blog/references/schema-stack.md: Complete blog sc