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.
examples/sample-vault/wiki/meta/dashboard.md
View on GitHub---
type: "dashboard"
title: "Dashboard"
created: "2026-08-25"
updated: "2026-08-25"
status: "active"
domain: "Blog Content Brain"
tags: [meta, dashboard, active]
---
# Dashboard
## Visual Map
![[brain-relationship-map.svg]]
## Operating Links
- [[Source Intake Workflow]]
- [[Research Refresh Workflow]]
- [[Synthesis Workflow]]
- [[Reporting Workflow]]
- [[Approval Queue]]
- [[Health Scorecard]]
- [[Action Roadmap]]
## Dashboard status model
| Surface | State question | Evidence link |
|---|---|---|
| Sources | Are claims traceable and current? | [[Source Manifest Guide]] |
| Intake | Are new materials admitted safely? | [[Source Intake Workflow]] |
| Refresh | Are volatile sources within review date? | [[Research Refresh Workflow]] |
| Synthesis | Are facts distinct from recommendations? | [[Synthesis Workflow]] |
| Decisions | Are consequential actions authorized? | [[Approval Queue]] |
| Roadmap | Is work ordered by evidence and risk? | [[Action Roadmap]] |
| Health | Do statuses match direct gates? | [[Health Scorecard]] |
| Reporting | Can another operator verify the state? | [[Weekly Report]] |
## Attention lanes
### Now
One current action with an owner, evidence, and completion gate.
### Next
Actions whose prerequisites are satisfied but which are not started.
### Waiting
Items that require an owner decision or external dependency.
### Watching
Living sources, APIs, and release channels with refresh triggers.
### Closed
Actions whose named gate passed and whose evidence remains linked.
## Dashboard maintenance
1. Read the previous dashboard state.
2. Sample every “verified” evidence link.
3. Move stale claims to watching or at risk.
4. Remove completed actions from now.
5. Pull the next dependency-ready action forward.
6. Keep external decisions in waiting.
7. Update owners and dates.
8. Record the change in the log.
9. Regenerate visual navigation when links change.
10. Run vault lint.
## Warning indicators
| Indicator | Meaning | Response |
|---|---|---|
| Missing source date | Currentness unknown | Run refresh |
| Broken wikilink | Navigation or provenance gap | Repair link |
| Low confidence | Material limitation | Narrow claim |
| Dirty generated output | Determinism uncertain | Rebuild safely |
| Pending approval | Consequential action not authorized | Wait |
| Failed test | Implementation gate blocked | Diagnose |
| Skipped live check | External state unknown | Report boundary |
| Rights unknown | Public distribution blocked | Obtain review |
## Review questions
- Does the current action match the user’s outcome?
- Is the source authority correct for the claim?
- Is any confidence tag too strong?
- Is a local artifact being mistaken for external completion?
- Are private raw materials excluded from public surfaces?
- Is rollback still practical?
- Does the report expose all failures?
- Is the next action executable?
## Dashboard handoff
A new operator should be able to open this note, follow the operating links, and
understand what is current without reading a long chronology.
## Dashboard anti-patterns
Do not turn the dashboard into a backlog dump, a vanity score, a copied CI log,
or a collection of undated claims. Link evidence rather than duplicating it.
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: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |