
claude-blog-brain
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, dist
- Installs
- 200
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/agricidaniel/claude-blog --skill claude-blog-brain- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads claude-blog-brain automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- Read
<vault>/CODEX.md. - Read
<vault>/wiki/hot.md. - Read
<vault>/wiki/index.md. - Preserve
.raw/as immutable source material. - Never store credentials in the vault.
- Never make domain-specific claims without dated trustworthy sources.
- Keep
hot,index,overview, andlogcurrent. - Record research evidence in
references/source-ledger.json. - Record domain adapter completion in
references/adapter-manifest.json.
Script Mapping
new->python scripts/scaffold_vault.pydemo->python scripts/build_demo_vault.pyingest->python scripts/ingest_source.pysynthesize->python scripts/synthesize_brain.pyreport->python scripts/render_brain_report.pyvisuals->python scripts/generate_vault_visuals.pylint->python scripts/lint_vault.pynext->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.
FAQ
What does the claude-blog-brain skill do?
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, dist
How do I install claude-blog-brain?
Run npx skills add https://github.com/agricidaniel/claude-blog --skill claude-blog-brain in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/claude-blog-brain/ (personal) or .claude/skills/claude-blog-brain/ (project).
Which AI agents can use claude-blog-brain?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is claude-blog-brain safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains claude-blog-brain?
It is published by agricidaniel in agricidaniel/claude-blog. It has 200 recorded installs.
More from agricidaniel/claude-blog
blog
agricidaniel/claude-blog
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 the user asks to create, revise, analyze, plan, translate, localize, audit, or repurpose blog content, or invokes a /blog subcommand. Do not activate merely because the word "blog" appears in an unrelated coding, theme-debugging, database, log-analysis, or definition request.
blog-seo-check
agricidaniel/claude-blog
Post-writing SEO validation with pass/fail checklist covering title tag length and keyword placement, meta description quality, heading hierarchy and keyword density, internal/external link audit with anchor text analysis, canonical URL verification, Open Graph meta tags (og:title, og:description, og:image), Twitter Card validation, structured data presence and validity, URL structure optimization, and image alt text presence. Produces prioritized fix list with specific recommendations. Use for ONE finished post when the user says "seo check", "validate seo", "on-page seo", "title tag check", "link audit". Not for a whole-site audit (blog-audit, claude-seo), AI-citation scoring (blog-geo), schema generation (blog-schema), or the delivery gates (blogpreflight.py).
blog-factcheck
agricidaniel/claude-blog
Verify statistics and claims in blog posts by fetching cited source URLs and checking if the claimed data actually appears on the page. Extracts all load-bearing claims (statistics, product or policy claims, ranking and comparative claims, named sources), validates cited URLs before fetching, and scores match confidence (exact match 1.0, paraphrase 0.7-0.9, not found 0.0). Flags uncited claims as UNVERIFIED and marks a claim verified only when this run fetched the source and found the passage. Checks that a source says what the post says it says; it cannot prove the source is true or verify first-hand experience. Use when the user says "fact check", "verify statistics", "check sources", "factcheck". Report only; not for rewriting posts (blog-rewrite).
blog-analyze
agricidaniel/claude-blog
Score one blog post (or a folder of posts) on a 5-category 100-point scale covering content quality, SEO, E-E-A-T, technical elements, and AI citation readiness. Runs the deterministic analyzer first, then adds judgment and prioritized Critical/High/Medium/Low fixes. Advisory style diagnostics never infer authorship or affect the score. Exports markdown, JSON or table; works with MDX, markdown, HTML or a URL. Use when the user asks to analyze, score, rate or check the quality of specific posts ("analyze blog", "blog score", "check blog quality", "rate this post"). For a site-wide health check (orphan pages, cannibalization, stale content, schema across all posts) use blog-audit instead.
blog-audit
agricidaniel/claude-blog
Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when the user asks for a site-wide blog health check across many posts ("blog audit", "blog health", "audit all posts", "site audit of the blog"). For one post, or a quality score with fixes for a few named files, use blog-analyze instead.
blog-brief
agricidaniel/claude-blog
Create a content brief for ONE planned post: target and secondary keywords, search intent, template choice, competitor gaps from the live SERP, sourced statistics to include, section plan, internal-link targets, and distribution ideas. Use when the user says "content brief", "blog brief", "SEO brief", "article brief". Not a skeleton only (blog-outline), a multi-post plan (blog-strategy, blog-calendar, blog-cluster), or the article itself (blog-write).
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.