By iurykrieger
Turn any Obsidian vault into a searchable, syncable second brain that ingests content from Confluence, Google Docs, and GitHub, auto-links entities, answers natural-language questions, and enforces a code-review gate on session stop.
Initialize any folder as a Bedrock-powered Obsidian vault. Creates entity directories, copies templates, configures language and domain taxonomy, scaffolds connected example entities, and checks dependencies. Use when: "bedrock setup", "bedrock-setup", "/bedrock:setup", "initialize vault", "setup vault", "create vault", "bootstrap vault", or when a user wants to start a new Second Brain with Bedrock.
Adaptive vault reader skill. Receives a natural language question, uses graph.json as the primary index (Phase 2.0) before any glob/grep, then self-assesses whether more context is needed. Escalates to live /graphify only when graph coverage is insufficient, or to /bedrock:learn for remote content ingestion. Answers simple questions with zero graphify calls. Use when: "bedrock ask", "bedrock-ask", "/bedrock:ask", any question about the vault, "what do we know about", "who owns", "what's the status of", "tell me about", "how does it work", or any Second Brain query.
Vault alignment engine. Detects and fixes 5 types of structural misalignments: broken backlinks, concept fragmentation, entity miscategorization, duplicated entities, and misnamed entities. Delegates all writes to /bedrock:preserve. Supports interactive mode (user confirmation) and cron mode (autonomous mechanical fixes + queued semantic proposals). Use when: "bedrock compress", "bedrock-compress", "align vault", "fix backlinks", "fix misalignments", "/bedrock:compress".
Internal fetcher module for Confluence pages. Fetches content via Atlassian MCP (preferred), REST API with Basic Auth (fallback), or browser DOM extraction via Claude in Chrome (last resort) and returns Markdown. Used by /bedrock:learn and /bedrock:sync — not intended for direct user invocation.
Internal fetcher module for Google Docs and Sheets. Fetches content via MCP (preferred, when available), Google API with bearer token or public URL export (fallback), or browser DOM extraction via Claude in Chrome (last resort) and returns Markdown. Used by /bedrock:learn and /bedrock:sync — not intended for direct user invocation.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Turn any Obsidian vault into a structured Second Brain with AI agents
Bedrock is a Claude Code plugin that automates Obsidian vault management through AI-powered skills. It organizes knowledge into 7 entity types following adapted Zettelkasten principles — entity detection, bidirectional linking, ingestion from external sources, deduplication, and sync.
No build system. No runtime. Just markdown files, AI agents, and your Obsidian vault.
type/, status/, domain/, scope/)/plugin marketplace add iurykrieger/claude-bedrock
/plugin install bedrock@claude-bedrock
For local development:
claude --plugin-dir ./claude-bedrock
After installing, run the setup wizard:
/bedrock:setup
This will guide you through:
graphify is installed (required)The setup creates all entity directories, copies templates, generates a vault-level CLAUDE.md, and scaffolds example entities with bidirectional wikilinks so you can see the graph in Obsidian immediately.
| Skill | Purpose |
|---|---|
/bedrock:setup | Interactive vault initialization and configuration |
/bedrock:ask | Orchestrated vault reader — decomposes questions, searches graph and vault, cross-references entities |
/bedrock:learn | Ingest external sources — extract and create entities |
/bedrock:preserve | Single write point — detect, match, create/update entities with bidirectional links |
/bedrock:compress | Deduplication and vault health — broken links, orphans, stale content |
/bedrock:sync | Re-sync entities with external sources |
/bedrock:healthcheck | Read-only vault health diagnostic — graphify-out integrity, orphans, dangling content, stale entries |
/bedrock:vaults | Manage registered vaults — list, set default, remove |
your-vault/
├── actors/ # Systems, services, APIs (permanent notes)
├── people/ # Contributors, team members (permanent notes)
├── teams/ # Squads, organizational units (permanent notes)
├── topics/ # Cross-cutting subjects with lifecycle (bridge notes)
├── discussions/ # Meeting notes, conversations (bridge notes)
├── projects/ # Initiatives with scope and deadline (index notes)
└── fleeting/ # Raw ideas, unstructured captures (fleeting notes)
Each directory contains a _template.md defining the frontmatter schema for that entity type.
Bedrock turns your vault into a living knowledge graph by combining 8 skills you invoke from Claude Code. You never write entities by hand — skills detect, create, and link them for you, with Obsidian rendering the result as a graph.
/bedrock:setup — answers a few questions and scaffolds directories, templates, and example entities.npx claudepluginhub iurykrieger/claude-bedrock --plugin bedrockGoverned adversarial development for AI agents — v5.0 dual Phase-1 entry path (`/yoke:discover` for product-shaped tasks, `/yoke:fix` for engineering-shaped fixes) atop the v4.0 acceptance-criteria QA cutover and the v3.0 agent council protocol. Phase 1 now offers two authoring entrypoints producing interchangeable Phase-1 artifacts (`.yoke/prds/<slug>.md` or `.yoke/fixes/<slug>.md`); downstream skills read whichever exists via `wm_phase1_artifact_path` without branching on the artifact kind. Phase 3 produces a binding Acceptance Criteria document organised as User Stories → Definition of Done → Acceptance Criteria → Sensor pool, authored through an interactive Senior-QA grill. Three runtime persona subagents (Sr Eng, Sr QA, Sr Staff) spawn in parallel each cycle behind a deterministic sync barrier (Phase A), exchange réplicas inside a bounded council loop with a contradiction-detection arbiter (Phase B), and either advance on consensus or escalate Trigger 4 on cap-exhausted divergence (Phase C). Sensor selection per Acceptance Criterion is a runtime council decision, not an authoring-time tag. All inside a binding human contract. Canonical-memory reads and writes dispatch through providers.yaml to a peer plugin (claude-bedrock is the reference implementation); pluggable canonical-memory providers ship via the documented working-memory contract. The Orchestrator subagent survives in canonize-only mode at full-run termination. Manifesto: yoke.md.
Bidirectional knowledge flow between Claude Code and Obsidian — 20 MCP tools, skills, and hooks for PKM
Create and edit Obsidian vault files including Markdown, Bases, and Canvas. Use when working with .md, .base, or .canvas files in an Obsidian vault.
AI thinking partner for your Obsidian vault — process, recall, synthesize, research with evidence-backed learning science
Second Brain OS — 16 skills for knowledge management, deep thinking, and vault operations powered by Obsidian.
Persistent Obsidian-based memory for coding agents. Automatically orients from a knowledge vault at session start, navigates project architecture via graph traversal, and writes discoveries back to the vault.
Knowledge management for Obsidian vaults and structured markdown repositories