Back to search
claude-bedrock
MarketplaceWorks with Claude CodeGitHub
Second Brain automation for Obsidian vaults — entity management, ingestion, compression, and sync via Claude Code skills
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Checked today
Badge for your README
Markdown
[](/listings/iurykrieger-claude-bedrock)HTML
<a href="/listings/iurykrieger-claude-bedrock"><img src="/api/listings/iurykrieger-claude-bedrock/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
/plugin marketplace add iurykrieger/claude-bedrock /plugin install bedrock@claude-bedrock
For local development:
claude --plugin-dir ./claude-bedrock
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 35 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- {
- "name": "claude-bedrock",
- "owner": {
- "name": "Iury Krieger"
- },
- "metadata": {
- "description": "Second Brain automation for Obsidian vaults — entity management, ingestion, compression, and sync via Claude Code skills"
- },
- "plugins": [
- {
- "name": "bedrock",
- "source": "./",
- "description": "Second Brain automation for Obsidian vaults — entity management, ingestion, compression, and sync via Claude Code skills",
- "version": "1.2.0",
- "author": {
- "name": "Iury Krieger",
- "url": "https://github.com/iurykrieger"
- },
- "homepage": "https://claude-bedrock.vercel.app",
- "repository": "https://github.com/iurykrieger/claude-bedrock",
- "license": "MIT",
- "keywords": [
- "obsidian",
- "second-brain",
- "knowledge-base",
- "zettelkasten",
- "vault",
- "knowledge-management",
- "knowledge-graph",
- "note-taking"
- ],
- "category": "knowledge-management"
- }
- ]
- }
README.md · README · 194 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- <p align="center">
- <img src="docs/banner.png" alt="Bedrock — Knowledge graph visualization" width="600">
- </p>
- <h1 align="center">Bedrock</h1>
- <p align="center">
- <strong>Turn any Obsidian vault into a structured Second Brain with AI agents</strong>
- </p>
- <p align="center">
- <a href="https://github.com/iurykrieger/claude-bedrock/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="License"></a>
- <a href="https://github.com/iurykrieger/claude-bedrock"><img src="https://img.shields.io/badge/claude--code-plugin-a882ff" alt="Claude Code Plugin"></a>
- <a href="https://github.com/iurykrieger/claude-bedrock"><img src="https://img.shields.io/github/v/tag/iurykrieger/claude-bedrock?label=version" alt="Version"></a>
- </p>
- ---
- Bedrock is a [Claude Code](https://docs.anthropic.com/en/docs/claude-code) plugin that automates Obsidian vault management through AI-powered skills. It organizes knowledge into **7 entity types** following adapted [Zettelkasten](https://zettelkasten.de/overview/) 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.
- ## Features
- - **8 AI-powered skills** — setup, ask, teach, preserve, compress, sync, healthcheck, and vaults
- - **7 entity types** — actors, people, teams, topics, discussions, projects, and fleeting notes
- - **External source ingestion** — Confluence, Google Docs, GitHub repositories, and any file format supported by [docling](https://github.com/docling-project/docling) (DOCX, PPTX, XLSX, PDF, HTML, EPUB, images, and more)
- - **Bidirectional wikilinks** — automatic cross-referencing with Obsidian graph view
- - **Hierarchical tags** — multi-dimensional filtering (`type/`, `status/`, `domain/`, `scope/`)
- - **Zettelkasten structure** — permanent, bridge, index, and fleeting note roles
- - **Trunk-based git workflow** — structured commit conventions built in
- ## Installation
- ```bash
- /plugin marketplace add iurykrieger/claude-bedrock
- /plugin install bedrock@claude-bedrock
- ```
- For local development:
- ```bash
- claude --plugin-dir ./claude-bedrock
- ```
- ## Quick Start
- After installing, run the setup wizard:
- ```
- /bedrock:setup
- ```
- This will guide you through:
- 1. **Language selection** — choose the vault content language (default: English)
- 2. **Dependency check** — verify `graphify` is installed (required)
- 3. **Vault objective** — pick a preset (engineering team, product management, company wiki, personal second brain, open source project, or custom)
- 4. **Scaffold** — create directories, templates, config, and connected example entities
- 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.
- ## Skills
- | 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 |
- ## Vault Structure
- ```
- 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.
- ## How It Works
- 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.
- ### First-time use
- 1. Open a folder you want to turn into a vault (or an existing Obsidian vault).
- 2. Run `/bedrock:setup` — answers a few questions and scaffolds directories, templates, and example entities.
- 3. Open the folder in Obsidian. You'll already see a connected graph.
- ### Day-to-day loops
- - **Capture knowledge from a source** — paste a Confluence page, Google Doc, GitHub repo, remote URL, or any local file (DOCX, PPTX, XLSX, PDF, HTML, EPUB, images, and any other docling-supported format) into `/bedrock:learn`. Bedrock extracts entities and writes them to the vault with bidirectional links.
- - **Ask the vault questions** — use `/bedrock:ask` for anything like *"who owns the billing API?"* or *"what's the status of project X?"*. It searches the graph, follows wikilinks, and answers with citations.
- - **Keep sources fresh** — run `/bedrock:sync` to re-pull external sources, or `/bedrock:sync --github` / `--people` to surface recent activity and contributors.
- - **Clean up drift** — run `/bedrock:compress` to fix broken backlinks, merge duplicates, and consolidate fragmented concepts. Run `/bedrock:healthcheck` for a read-only report.
- - **Manage multiple vaults** — register several vaults with `/bedrock:vaults`; target a specific one with `--vault <name>`.
- ### What you get in Obsidian
- Every entity has YAML frontmatter (type, status, domain, sources), hierarchical tags (`type/actor`, `status/active`, `domain/payments`), and bidirectional wikilinks. The graph view becomes a navigable map of people, systems, teams, topics, and projects — updated automatically as you teach Bedrock new content.
- ## Dependencies
- | Tool | Purpose | Required? |
- |---|---|---|
- | [graphify](https://github.com/iurykrieger/graphify) | Semantic code extraction and knowledge-graph pipeline used by `/bedrock:learn` and `/bedrock:sync` | Yes |
- | [docling](https://github.com/docling-project/docling) | Universal file → markdown converter used by `/bedrock:learn` to ingest DOCX, PPTX, XLSX, PDF, HTML, EPUB, images, and other non-markdown formats | Yes |
- Both `graphify` and `docling` are auto-installed by `/bedrock:setup` (and lazily by `/bedrock:learn` on first use if missing). You can also install them manually via `pipx install graphify` / `pipx install docling`.
- Confluence and Google Docs ingestion are built into the plugin as internal skills (`/bedrock:confluence-to-markdown`, `/bedrock:gdoc-to-markdown`) invoked by `/bedrock:learn` and `/bedrock:sync` — no external installation required.
- ## Configuration
- Configuration is stored in `.bedrock/config.json` inside your vault. Run `/bedrock:setup` again at any time to reconfigure.
- ## Error Reporting
- The `bedrock` plugin auto-reports framework errors as GitHub issues on
- [iurykrieger/claude-bedrock](https://github.com/iurykrieger/claude-bedrock) so
- maintainers learn about real-world failures.
- **What gets reported**
- - Python tracebacks from skill scripts
- - Non-zero exit codes from skill bash commands
- - Known logical-failure phrases in Claude's text (small auditable regex catalog)
- **What never gets reported**
- - Vault content (markdown bodies, frontmatter values)
- - Absolute filesystem paths (replaced with `.../`)
- - Vault entity names (people, teams, projects, etc.)
- - URLs from your vault (Confluence, Google Docs, internal repos)
- **How to opt out**
- Add `"error_reporting": false` to your vault's `.bedrock/config.json`:
- ```json
- {
- "error_reporting": false
- }
- ```
- Default is `true`. The hook silently skips reporting if `gh` is not installed
- or you're not authenticated, and logs the would-be report to
- `~/.claude-bedrock-cache/error-reporter.log`.
- ## Contributing
- Contributions are welcome! Here's how to get started:
- 1. **Fork** the repository
- 2. **Clone** your fork and install the plugin locally:
- ```bash
- claude --plugin-dir ./claude-bedrock
- ```
- 3. **Create a branch** for your feature or fix
- 4. **Make your changes** — skills live in `skills/`, entity definitions in `entities/`, templates in `templates/`
- 5. **Test** by running the plugin against a test vault
- 6. **Open a PR** against `main`
- ### Project Structure
- ```
- claude-bedrock/
- ├── .claude-plugin/ # Plugin manifest (plugin.json)
- ├── skills/ # Skill definitions (SKILL.md per skill)
- │ ├── setup/
- │ ├── query/
- │ ├── teach/
- │ ├── preserve/
- │ ├── compress/
- │ └── sync/
- ├── entities/ # Entity type definitions
- ├── templates/ # Frontmatter schema templates
- ├── docs/ # Documentation assets
- ├── CLAUDE.md # AI agent instructions
- └── README.md
- ```
- ## License
- [MIT](LICENSE) — Iury Krieger
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.