---

name: claude-blog-brain description: > Scaffold and operate Claude Blog Brain, a source-cited Obsidian brain for blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill. Use when the user says "claude-blog-brain", "Claude Blog Brain", "create a blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill brain", "import sources", "synthesize plan", "render report", or wants a persistent vault-backed operating system for blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill. argument-hint: "new | demo | ingest | synthesize | report | visuals | lint | next" license: Custom license

Claude Blog Brain

Operate the vault first. Read CODEX.md, wiki/hot.md, and wiki/index.md before changing notes.

Commands

/claude-blog-brain new <client-slug> --owner <name>
/claude-blog-brain demo
/claude-blog-brain ingest --vault <path> --file <source>
/claude-blog-brain synthesize --vault <path>
/claude-blog-brain report --vault <path>
/claude-blog-brain visuals --vault <path>
/claude-blog-brain lint --vault <path>
/claude-blog-brain next --vault <path>

Source checkout equivalent:

claude-blog-brain new <client-slug> --owner <name>
claude-blog-brain demo
claude-blog-brain ingest --vault <path> --file <source>
claude-blog-brain synthesize --vault <path>
claude-blog-brain report --vault <path> --html-only

Required Operating Rules

1. Read <vault>/CODEX.md.
2. Read <vault>/wiki/hot.md.
3. Read <vault>/wiki/index.md.
4. Preserve .raw/ as immutable source material.
5. Never store credentials in the vault.
6. Never make domain-specific claims without dated trustworthy sources.
7. Keep hot, index, overview, and log current.
8. Record research evidence in references/source-ledger.json.
9. Record domain adapter completion in references/adapter-manifest.json.

Script Mapping

• new -> python scripts/scaffold_vault.py
• demo -> python scripts/build_demo_vault.py
• ingest -> python scripts/ingest_source.py
• synthesize -> python scripts/synthesize_brain.py
• report -> python scripts/render_brain_report.py
• visuals -> python scripts/generate_vault_visuals.py
• lint -> python scripts/lint_vault.py
• next -> python scripts/guide_next_action.py

Quality Gates

• No ranking or traffic guarantee; content outcomes are probabilistic and never certain
• No credentials, tokens, API keys, or private client content in repo artifacts
• No mutation of a CMS, GSC, GA4, or publishing platform; the brain is advisory and read-only
• No recommendation without a dated source, confidence level, and rollback note
• No deprecated advice (HowTo schema, retired FAQ rich results, FID) presented as current
• No fabricated or unsourced statistics and no generic, unsupported, or low-quality generated filler presented as fact

Do not call this brain market-ready unless scripts/audit_brain.py --require market-ready passes. A scaffold is not a finished brain.

Research Refresh

monthly for Google algorithm updates and Search Central policy; before every release for E-E-A-T framing, schema deprecations, and GEO/AEO citation claims; on-changelog for the claude-blog skill

Community

Use public project Discussions for questions and support: https://github.com/AgriciDaniel/claude-blog/discussions. Report reproducible defects through public Issues: https://github.com/AgriciDaniel/claude-blog/issues.