From bedrock
Manages Bedrock vault registry: lists vaults with path/status/default, sets default vault, removes vaults. Use for 'bedrock vaults', 'list vaults', 'set default vault', 'remove vault'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bedrock:vaultsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
The vault registry lives in the plugin root directory, not in any vault.
The vault registry lives in the plugin root directory, not in any vault. Use the "Base directory for this skill" provided at invocation to resolve paths:
<base_dir>/../../vaults.json<base_dir>/../../CLAUDE.md (auto-injected into context)Where <base_dir> is the path shown in "Base directory for this skill".
This skill manages the global vault registry — the file that maps vault names to filesystem paths and tracks which vault is the default.
You are a management agent. This skill is read-only with respect to vaults themselves —
it never reads or modifies vault entities, never runs git operations inside vaults, and
never touches .bedrock/config.json. It only reads and writes the registry file (vaults.json).
Parse the user's input to determine the command mode:
| Input pattern | Mode | Variables |
|---|---|---|
No flags / empty / list | list | — |
--set-default <name> | set-default | TARGET_NAME = <name> |
--remove <name> | remove | TARGET_NAME = <name> |
If the input doesn't match any pattern, default to list mode.
Resolve the registry path:
REGISTRY_PATH = <base_dir>/../../vaults.json
Read the registry file:
cat <REGISTRY_PATH> 2>/dev/null
If the file does not exist or is empty:
/bedrock:setup in a vault directory to register your first vault."If the file exists: parse the JSON. Expected schema:
{
"vaults": [
{
"name": "<string>",
"path": "<absolute-path>",
"default": true | false
}
]
}
Store the parsed vaults array as VAULTS.
For each vault in VAULTS, check if the path still exists on disk:
test -d "<vault_path>" && echo "exists" || echo "missing"
Present a table:
## Registered Vaults
| Name | Path | Default | Status |
|---|---|---|---|
| my-vault | /Users/me/vaults/my-vault | * | ok |
| team-vault | /Users/me/vaults/team-vault | | ok |
| old-vault | /Users/me/vaults/old-vault | | missing |
Default column shows * for the default vaultStatus column shows ok if the directory exists, missing if it does notIf any vault has status missing, add a note:
> Vaults marked as "missing" have paths that no longer exist on disk.
> Run `/bedrock:vaults --remove <name>` to clean up, or re-create the vault at the registered path.
name == TARGET_NAME in VAULTS<TARGET_NAME> is not registered. Available vaults:" followed by a list of names. Exit."default": false on all vaults"default": true on the matching vaultREGISTRY_PATH<TARGET_NAME> ()."name == TARGET_NAME in VAULTS<TARGET_NAME> is not registered. Available vaults:" followed by a list of names. Exit.VAULTSREGISTRY_PATH<TARGET_NAME> removed from registry. Files on disk were NOT deleted ()."When writing the registry (set-default or remove modes), use the Write tool to overwrite REGISTRY_PATH with the updated JSON:
{
"vaults": [
{ "name": "...", "path": "...", "default": true },
{ "name": "...", "path": "...", "default": false }
]
}
Format the JSON with 2-space indentation for readability.
| # | Rule |
|---|---|
| 1 | NEVER modify vault files — this skill only touches vaults.json |
| 2 | NEVER run git operations — no git pull, commit, push, or any git command |
| 3 | NEVER delete files on disk — --remove only removes the registry entry |
| 4 | ALWAYS validate vault name exists before set-default or remove |
| 5 | ALWAYS check path existence when listing vaults — flag missing paths |
| 6 | ALWAYS maintain exactly one default — if the default is removed, auto-assign the first remaining vault |
| 7 | Vault names are kebab-case — lowercase, no spaces, no special characters beyond hyphens |
npx claudepluginhub iurykrieger/claude-bedrock --plugin bedrockInitializes 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.
Validates Meta-Vault Markdown frontmatter and wiki-link integrity. Runs as a session-end gate, blocking close on errors. Supports hard, warn, and off modes.
Runs nightly vault maintenance: fixes broken wiki-links, detects orphan pages, syncs directory indexes, and flags stale GitHub issue tasks.