From obsidian-forge
obsidian-forge (alias `of`) CLI skill for creating and managing Obsidian vaults, processing inbox notes with AI classification, strengthening knowledge graphs, syncing plugins across vaults, and running the background daemon. Use when initializing vaults, automating PARA routing, managing MOCs, or debugging vault sync and graph operations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-forge:obsidian-forgeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```bash
of)# New vault
of init my-vault --path ~/Documents
of vault add ~/Documents/my-vault
of daemon install # macOS: auto-start background watcher
# Check state
of vault list
of daemon status
Always run these first when user reports a problem:
of vault list # registered? enabled? watched?
of settings status # .obsidian store populated?
of daemon status # daemon running?
RUST_LOG=debug of sync # verbose output for errors
of process-all [--vault <name>]
Reads Inbox/, calls AI provider, injects frontmatter, moves file to PARA folder.
AI provider must be configured in vault.toml [ai]. If it fails, read the error — unknown provider or missing base_url will have a clear message.
of update-mocs [--vault <name>] # rebuild hub files
of strengthen-graph [--vault <name>] # backlinks, bridge notes, auto-tags
of sync [--vault <name>] # MOC + graph + git in one shot
All idempotent — safe to re-run.
of settings import <vault> # vault → global store
of settings push-all # global store → all vaults
of vault disable/enable <name> # exclude/include from sync + watch
of vault pause/resume <name> # daemon toggle only; manual sync still works
of vault remove <name> # unregister (files kept)
vault.toml (per-vault) overrides nothing — it IS the source of truthInbox/ → 01-Projects/ 02-Areas/ 03-Resources/ 99-Archives/~/.obsidian-forge/logs/of/forge.loggraph.* bools in vault.toml gate each graph operation individuallyGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
npx claudepluginhub epicsagas/plugins --plugin obsidian-forge