Bedrock
Turn any Obsidian vault into a structured Second Brain.
7 entity types. 6 skills. Zero config.
Requires Obsidian and Claude Code
/plugin marketplace addiurykrieger/claude-bedrock/plugin installbedrock@claude-bedrock/bedrock:setupHow It Works
Teach, preserve, compress, ask
Four steps to turn scattered knowledge into a living, queryable graph.
Teach it your sources
Point Bedrock at a Confluence page, a GitHub repo, a Google Doc, or a CSV. It reads the source, extracts entities — people, systems, teams, topics — and classifies them automatically.
/bedrock:teachIt preserves the knowledge
Every entity is written to your vault with structured YAML frontmatter, hierarchical tags, and bidirectional wikilinks. One single write point — no conflicts, no duplicates, no orphans.
/bedrock:preserveCompress and maintain
Over time, knowledge drifts. Compress scans your vault for duplicates, broken links, stale content, and entity misalignment — then heals it. Your Second Brain stays clean.
/bedrock:compressAsk anything, anytime
Once your Second Brain is established, query it from any Claude session. Ask about systems, people, decisions, or dependencies — Bedrock searches the graph, cross-references entities, and answers with linked context.
/bedrock:askCommands
Six skills, one toolkit
Every skill is a specialized agent. Set up your vault, ingest sources, query knowledge, and keep everything in sync.
/bedrock:setupInitialize vault structure and templates
/bedrock:teachIngest from Confluence, GDocs, GitHub
/bedrock:preserveCreate entities with bidirectional links
/bedrock:askSearch and cross-reference your vault
/bedrock:compressDeduplicate and consolidate entities
/bedrock:syncRe-sync with external sources
/bedrock:setup
Interactive vault initialization and configuration. Guides you through language selection, dependency checks, vault objective, and scaffolds directories, templates, config, and connected example entities.
Invoke with
/bedrock:setupBuilt For
Your knowledge, structured
Bedrock adapts to any team or individual workflow where knowledge sprawl is a problem.
Engineering Team Wiki
Track systems, APIs, services, and team knowledge. Every repo becomes an entity with owners, dependencies, and status — automatically linked.
Product Management
Capture decisions, roadmaps, and cross-team context. Bridge notes connect people to projects to the discussions that shaped them.
Open Source Project
Document contributors, architecture decisions, and discussions. Ingest from GitHub PRs and issues directly into structured entities.
Personal Second Brain
Fleeting ideas get captured, promoted to permanent notes, and linked into your growing knowledge graph. Zettelkasten principles, automated.
The Output
Your vault, visualized
See how Bedrock organizes your knowledge into a structured, navigable graph in Obsidian.
Get Started
Up and running in seconds
Three commands. That's it.
/plugin marketplace addiurykrieger/claude-bedrock/plugin installbedrock@claude-bedrock/bedrock:setup