claude-blog-brain

Featured

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 d

AI & Automation 1,491 stars 260 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 `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...

Details

Author
AgriciDaniel
Repository
AgriciDaniel/claude-blog
Created
5 months ago
Last Updated
3 days ago
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

obsidian-second-brain

Operate any Obsidian vault as a living, self-rewriting second brain (an evolution of Karpathy's LLM Wiki pattern: sources rewrite existing pages, contradictions reconcile automatically, scheduled agents maintain the vault while you sleep). Use this skill whenever the user asks Claude to read, write, update, search, or manage their Obsidian vault - including saving notes from conversation, creating daily entries, updating kanban boards, logging dev work, managing people notes, capturing decisions, tracking deals, or maintaining any vault structure. Also triggers when the user wants to bootstrap a new vault from scratch, run a vault health check, or drop a _CLAUDE.md into their vault so all Claude surfaces share the same operating rules. Includes a research toolkit (7 commands: /x-read, /x-pulse, /research, /research-deep, /notebooklm, /youtube, /podcast) for AI-powered research via Grok, Perplexity, NotebookLM, YouTube, and podcast feeds - findings save to the vault automatically following the AI-first vault r

3,650 Updated today
eugeniughelbur
AI & Automation Listed

second-brain

Set up and operate a file-based second brain — a knowledge vault that every Claude Code session reads on start and writes back to before it ends, so context compounds across sessions instead of evaporating. Use "second-brain setup" to bootstrap a new vault (folder structure, brain CLAUDE.md, note templates, optional session-log hook), and follow the OPERATE rules in every session once a vault exists. Built for Obsidian-flavored markdown but works with any plain-markdown folder.

3 Updated 2 days ago
josherau
AI & Automation Featured

second-brain

When you want to capture into, compile, query, lint, or connect your personal Second Brain. Wraps the Karpathy LLM Wiki schema (Obsidian or any markdown vault) — raw/ (unprocessed sources), wiki/ (AI-compiled interlinked topic pages), outputs/ (generated artifacts). Tool-agnostic in design but defaults to a vault at ${SECOND_BRAIN_VAULT:-$HOME/Documents/SecondBrain}/. Six modes — capture (drop something into raw/), compile (process unprocessed raw files into wiki pages, update INDEX.md), query (answer a question from the wiki, save to outputs/), lint (orphans / contradictions / stale / unprocessed raw / topic gaps), connect (suggest new wikilinks between pages), search (quick lookup). Triggers on "/second-brain," "/sb," "capture this," "save this to my brain," "compile the wiki," "process raw notes," "query my wiki," "ask my brain," "lint the wiki," "find connections," "search my notes." Complements deep-research (external corpus) — this is the internal corpus.

225 Updated yesterday
coreyhaines31