Stats
Actions
Tags
From obsidian-blueprint
Applies incremental methodology updates to an Obsidian vault previously configured with obsidian-blueprint plugin. Use when user says "update vault tools", "upgrade methodology", "sync with latest obsidian-blueprint", or after updating the plugin to get new recommendations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-blueprint:vault-updateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- `skills/shared/references/methodology-framework.md` — shared principles, hook architecture, exit codes
skills/shared/references/methodology-framework.md — shared principles, hook architecture, exit codesskills/vault-setup/references/methodology.md — current methodology (latest version)skills/vault-setup/templates/ — current templatesskills/vault-setup/references/workflow-catalog.md — current GitHub workflow categoriesFollow the 6-step update workflow below. Vault-specific: preserve existing .gitignore customizations, hook customizations, workflow customizations, and spelling dictionary entries.
Same analysis as the audit skill — inventory existing tools, hooks, CI, and configuration. Identify which methodology version was previously applied by reading existing hook scripts and config.
Compare current state against the latest methodology:
Show the user what would change before making any modifications. Wait for approval.
Apply approved changes one dimension at a time:
.gitignore entries, custom spelling words, frontmatter field customizations)Run the quality gate to confirm no breakage. Distinguish methodology improvements from regressions.
Summarize updates applied and any manual steps remaining.
.gitignore entries, spelling dictionary additions, workflow customizations)npx claudepluginhub ondrasek/cc-plugins --plugin obsidian-blueprintUpgrades existing workflow scaffolding files (README, mods) to match the current Spacedock version. Detects version stamps, classifies files by upgrade strategy, and guides through five phases.
Initializes any folder as a Bedrock-powered Obsidian vault by creating entity directories, copying templates, configuring language/domain taxonomy, scaffolding example entities, and checking dependencies. Use for 'bedrock setup' or new vault bootstrapping.
Migrates an existing Obsidian vault to the obsidian-master-kit structure without destroying current layout. Detects vault state, backs up automatically, clusters notes via HDBSCAN embeddings, proposes adaptive folder-to-area mapping, and executes migration in human-approved batches with rollback.