Help us improve
Share bugs, ideas, or general feedback.
From obsidian-forge
Obsidian vault diagnostics — runs `of doctor` and reports vault status, AI connectivity, inbox state, and git health. Trigger: vault health check, diagnose vault, vault status.
npx claudepluginhub epicsagas/plugins --plugin obsidian-forgeHow this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-forge:vault-healthThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run `of doctor` to diagnose the current vault's health.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Run of doctor to diagnose the current vault's health.
--vault <name>.vault.toml), omit the flag (auto-detect).of vault list first to show registered vaults.of doctor --vault <name>
Skip the AI connectivity test if the user only wants structural checks:
of doctor --vault <name> --no-ping
Parse the output. Report in Korean:
Based on findings:
inbox-process skillgraph-strengthen skillvault-sync skillvault-fix skill| Excuse | Rebuttal | What to do instead |
|---|---|---|
| "I know the vault state already" | Vault state changes between sessions | Run of doctor every time |
| "AI provider is definitely fine" | Config drift, key rotation happen | Check actual output, don't assume |
| "Everything looks fine" | No evidence = not checked | Show concrete metrics from command output |
of doctorNo evidence = not done.
of doctor fails entirely → vault may not be registered or vault.toml is missing~/.obsidian-forge/.env for API keysof init repair