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
npx skills add AgriciDaniel/claude-blog --skill brain --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Claude Blog Brain Operate the vault first. Read `CODEX.md`, `wiki/hot.md`, and `wiki/index.md` before changing notes. ## Commands ```bash /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: ```bash 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 `reference
- Commands
- Required Operating Rules
- Script Mapping
- Quality Gates
- Research Refresh
- Community
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
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
How do I install it?
Run `npx skills add AgriciDaniel/claude-blog --skill brain --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From AgriciDaniel/claude-blog, a repository with 1,566 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.