An active Obsidian vault steward: the vault-keeper agent maintains your vault to best practices through the Obsidian MCP (CLI or filesystem fallback) — captures and files notes into PARA, builds and refreshes MOC index notes, fixes broken [[links]] and finds orphans, normalizes frontmatter, safely dedupes/renames, and runs the archive lifecycle. Includes three skills — obsidian-vault (the official Obsidian style guide, PARA organization, MCP-aware maintenance workflows, Dataview/Templates), vault-conventions (this vault's own house rules: the folder map, where each incoming note goes, and capture-vs-reference for daily and meeting notes with on-demand promotion), and project-context (the employer-scoped repo ↔ vault bridge: coding sessions read the matching project note's business rules before changing domain logic, stay within that employer's folder plus its daily/meeting captures, and write discoveries back) — plus /vault-checkup (read-only health sweep) and /vault-wire (scaffold and wire a repo's project note) commands. Complements the required official obsidian plugin (by Steph Ango/kepano) — it owns vault stewardship and defers Obsidian authoring syntax (Markdown, Bases, Canvas) to that plugin's skills.
2 on GitHubby Danniel Liborv0.5.1MITupdated 19 days ago
/
Plugin obsidian-vault-keeper from marketplace danniel-claude-plugins in danniel-isiah-libor/danniel-claude-plugins. Commands read from the repo's manifest — 18 days ago.
What it installs
Skills (3)
obsidian-vault
Maintain and organize an Obsidian vault to best practices, and apply the official Obsidian writing style guide (voice, terminology, headings, callouts) when editing notes. Use when organizing or maintaining an Obsidian vault — capturing/filing into PARA, building/refreshing MOCs, fixing broken links
project-context
Pull the current repo's business rules and domain context from the Obsidian vault while coding — and write discoveries back. Use in any coding session in a work repo BEFORE implementing or changing domain/business logic (validations, calculations, state transitions, workflows, integrations), when as
vault-conventions
The house rules for THIS specific Obsidian vault (Danniel's) — the filing decisions, folder map, and conventions that say where an incoming note goes and how to write it. Use whenever capturing, writing, filing, converting, or routing any note into the vault (project notes, requirement docs turned i
Slash commands (2)
/obsidian-vault-keeper:vault-checkup
Run a read-only Obsidian vault health sweep — scan for orphans, broken links, frontmatter drift, misfiled/duplicate notes, and stale MOCs — then report findings and offer to fix.
/obsidian-vault-keeper:vault-wire
Wire the current repo to the vault — find or scaffold its project note (repo frontmatter key + Business Rules section) and add the one-line pointer to the repo's CLAUDE.md, so every future session pulls domain context automatically.
Subagents (1)
vault-keeper
Use to maintain and organize an Obsidian vault to best practices — capture and file notes into PARA, build and refresh MOC index notes, fix broken links and find orphans, normalize frontmatter, safely dedupe/rename, and run the employer/archive lifecycle. A senior Obsidian librarian you summon whene
Agentic SDLC team (requirements → design → implementation → testing → review → security → release → docs) with per-feature auto-merge to development, sprint close promoting to staging for UAT, a separate production release to main with semantic versioning + tagging, CI/CD pipeline scan-and-fix, and optional per-project Jira-Scrum Notion sync — per-project hub pages, backlog, sprint planning (Definition of Ready), and a scrum-master skill. All stage promotions are PR/MR-based with non-protected branch cleanup. A Playwright E2E layer records a per-feature review video — with a visible mouse cursor, never screenshots — that gates the merge to development.
A summonable dream team of senior expert agents — a DevOps engineer (Docker, industry-standard CI/CD with mandatory manual-approval gates and semver tags/releases for UAT & prod, GCP infra), a fullstack developer (SOLID/clean code, security-first, cross-platform UI/UX, database design), a QA engineer (unit, Playwright E2E, VAPT, code review), a security analyst (read-only CVE triage via OSV/NVD with EPSS + CISA KEV, reachability checks, routed fixes), and a technical writer (user guides, how-to/feature docs, FAQs, release notes for clients/stakeholders). Includes focused skills (project-adaptation, gcp-devops, senior-development, qa-testing, git-conventions, documentation) and a /dream-team-review command that routes QA findings to the dev/devops agents and re-verifies. Stack-agnostic; composes with each project's CLAUDE.md, skills, and agents.
HADS (Human-AI Document Standard) — semantic tagging convention for docs that work for both humans and AI models — plus the grounded-vault pattern for provenance-linked, drift-checked knowledge stores.
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.