AgriciDaniel/claude-blog / brain
claude-blog-brain
UnverifiedScaffold 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.
PUBLISHING_NOTICE.md
View on GitHub# Publishing notice
## Rights boundary
The Brain contains original operating guidance, source metadata, and source
evidence. The repository is public and the Brain is MIT licensed, but a public
website may expose only reviewed wiki content and the public-facing notices
expressly selected by the sanitizer. Source ownership does not transfer merely
because a URL or paraphrase appears in this repository.
## What can be on the public website
- Reviewed Markdown under `wiki/`, after local-path and secret scanning.
- Public navigation assets generated from reviewed wiki links.
- The license, attribution, and third-party notices required for distribution.
- High-level methods that do not reproduce source captures or internal review
notes.
## What stays out of the public website
These files are tracked in the repository as public evidence, so anyone can
audit them there. They must stay out of the website projection the sanitizer
builds:
- Everything under `.raw`, including captures, manifests, and ingestion history.
- `references/source-ledger.json`, `references/claim-ledger.md`, source-review
decisions, and other source evidence used for verification.
## What never goes into the repository
- Credentials, tokens, and other secrets.
- Customer data, account identifiers, unpublished drafts, operator-only
decision records, and local absolute build paths.
The public projection is a separate sanitized artifact. Do not point a web
publisher directly at the Brain root. Run `site/scripts/sanitize-public.mjs`,
inspect its manifest, scan the resulting directory, and obtain the rights
holder's approval before publishing. The sanitizer is a safety control, not a
license grant or publication authorization.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |