Claude Blog Brain
A source-traceable Obsidian workspace for planning, creating, optimizing, and managing blog content.
The skill requires reading CODEX.md, wiki/hot.md, and wiki/index.md first; preserving raw sources, avoiding credentials, and remaining advisory/read-only toward CMS, GSC, and GA4. However, the plugin allows Read, Grep, Glob, Bash, Write, and Edit, which is broad, while per-command confirmation, fine-grained path isolation, and explicit rollback procedures are not specified. The repository contains an MIT LICENSE, but the skill and plugin metadata say Custom license, creating an attribution and licensing inconsistency. No malware, credential theft, or covert exfiltration red line is evident.
brain/SKILL.md supplies command mappings, operating order, quality gates, and failure-oriented tests; CI declares brain tests, vault linting, and audit execution, while tests cover determinism, malformed JSON, field validation, and temporary outputs. Nothing was executed for this review. The skill does not clearly document Python/Obsidian/runtime prerequisites, dependency installation, diagnosable user-facing failure messages, or recovery procedures, so static calibration limits the score to 10.
The target is a local Obsidian vault operated through Claude Blog Brain; scenarios, commands, and arguments are broadly specified, and blog, SEO, and GEO scope is described. Non-fit scenarios, semantic trigger boundaries, input/output contracts, and unsupported environments are not sufficiently defined. There is no evidence of Chinese-language UX or content support, and community support plus some workflows may depend on overseas GitHub or external services, warranting a mid-low score.
The skill has concise structure with commands, script mapping, operating rules, quality gates, refresh cadence, and public defect channels. The plugin declares version 0.1.0, while the repository provides an MIT license, CI, and issue templates. Points are deducted because the skill's Custom license conflicts with repository MIT metadata, and because installation, dependency setup, parameter stability, input/output examples, FAQs, maintenance ownership, and a clear changelog/update path are incomplete.
Committed tests indicate that scaffolding, ingestion, synthesis, visuals, reporting, linting, and blog adapters can produce structured reports, with JSON error envelopes for invalid input. This review did not execute them, and source inspection cannot establish actual output quality, source freshness, Obsidian compatibility, or marginal benefit over manual alternatives. With no third-party execution results, static calibration limits effectiveness to 7.
The evidence includes a pinned revision, command-to-script mappings, committed tests, CI configuration, deterministic-output assertions, and requirements for source ledgers. However, there are no results from this review, independent replication, coverage data, or third-party reports; repository marketing claims cannot substitute for selected-skill evidence, so static calibration limits the score to 5.
- The Custom license in the skill metadata conflicts with the repository MIT license; confirm licensing before installation or redistribution.
- Bash, Write, and Edit permissions are broad; run in an isolated vault and manually confirm paths and data scope before writes or external calls.
- Chinese support and mainland-China network reachability are not sufficiently evidenced; separately verify workflows involving GitHub, Google, Gemini, or NotebookLM.
- CI and committed tests are static evidence only; they were not executed in this review and should not be treated as verified runtime results.
What does this skill do, and when should you use it?
Claude Blog Brain is the standalone skill at brain/SKILL.md in the claude-blog repository. It organizes blog research, strategy, editorial planning, topic clusters, multilingual publishing, and content operations inside a persistent Obsidian vault. Before changing notes, it reads CODEX.md, wiki/hot.md, and wiki/index.md, while maintaining research evidence and adapter manifests. It fits creators, teams, and agencies that need an auditable workflow, but it is advisory and cannot guarantee rankings, traffic, or AI citations.
It creates client vaults with new, builds a demo vault with demo, imports source files with ingest, synthesizes vault content with synthesize, renders reports with report, generates vault visuals with visuals, checks vault quality with lint, and recommends the next action with next. It reads <vault>/CODEX.md, wiki/hot.md, and wiki/index.md before operating; preserves .raw/ as immutable source material; keeps hot, index, overview, and log current; and records evidence in references/source-ledger.json plus adapter completion in references/adapter-manifest.json. The command mappings call scaffold_vault.py, build_demo_vault.py, ingest_source.py, synthesize_brain.py, render_brain_report.py, generate_vault_visuals.py, lint_vault.py, and guide_next_action.py.
- A solo blogger wants one persistent vault for source material, research evidence, editorial planning, and content decisions.
- A marketing team needs to coordinate editorial calendars, strategy, semantic topic clusters, and multilingual publishing for client blogs.
- An agency needs a pre-delivery audit trail for citations, source freshness, factual support, and vault completeness.
- A Claude Code skill builder wants a reference workflow for evidence led content operations with explicit read-only and quality rules.
What are this skill's strengths and limitations?
- Uses a persistent Obsidian vault rather than treating each content task as an isolated draft.
- Requires dated, trustworthy evidence and records research in a source ledger, supporting auditability.
- Covers ingestion, synthesis, reporting, visuals, linting, and next-action guidance in one workflow.
- Explicitly prohibits storing credentials and writing to CMS, GSC, GA4, or publishing platforms.
- It is an advisory vault operating system, not a direct CMS, analytics, or publishing integration.
- The skill frontmatter says Custom license while the repository README describes the collection as MIT-licensed; adopters should verify the applicable license scope.
- The source does not document a standalone brain package installer, separate test coverage, or a platform validation matrix for this skill.
- Keeping the workflow current requires ongoing refreshes for Google policies, algorithm changes, schema guidance, and GEO/AEO evidence.
How do you install this skill?
The source says this skill ships with the public AgriciDaniel/claude-blog repository and requires the Claude Code CLI plus Python 3.11+. Following the README, install the public plugin in Claude Code with /plugin marketplace add AgriciDaniel/claude-blog, then /plugin install claude-blog@agricidaniel-claude-blog, and restart Claude Code. The source does not document a standalone installation command or fixed destination for brain/SKILL.md.
How do you use this skill?
In Claude Code, invoke claude-blog-brain or use the documented commands: /claude-blog-brain new <client-slug> --owner <name>, demo, ingest --vault <path> --file <source>, synthesize --vault <path>, report --vault <path>, visuals --vault <path>, lint --vault <path>, and next --vault <path>. Start with a vault containing CODEX.md, wiki/hot.md, and wiki/index.md so the required operating checks can run.