← ClaudeAtlas

meta-statuslisted

Diagnose the obsidian-mcp-router and all its configured vaults. Pings each vault, reports online/offline/auth status, and suggests fixes for each issue type. Use when the user says "check vault status", "diagnose the router", "are my vaults reachable", "status of obsidian", "what's wrong with the router", or asks to debug an obsidian connection issue.
tboome33/obsidian-mcp-router · ★ 1 · AI & Automation · score 74
Install: claude install-skill tboome33/obsidian-mcp-router
# meta-status Produces a one-shot diagnostic of the multi-vault Obsidian router. Run it when the user wants to know what's working, what isn't, and how to fix it. ## Steps 1. Call the router's `list_vaults` tool (no arguments). The router will ping each configured vault in parallel and return a structure like: ```json { "defaultVault": "tradingview", "configPath": "/Users/.../.claude/obsidian-mcp-router/config.json", "vaults": [ { "name": "tradingview", "type": "local", "baseUrl": "https://127.0.0.1:27125", "online": true, "latencyMs": 4, "missingApiKey": false, "isDefault": true }, { "name": "qnap", "type": "remote", "baseUrl": "https://qnap.tailnet.local:27125", "online": false, "latencyMs": 5012, "error": "[qnap] timed out after 5000ms calling /", "missingApiKey": false } ] } ``` 2. Render the result as a compact summary: - First line: `<n> vault(s) configured · <m> online · default: <name>` - Then a markdown table with columns: name | type | status | latency | path/baseUrl - Use ✅ for online, ❌ for offline, ⚠️ for missingApiKey or any partial issue 3. For each vault that is NOT fully healthy, add a short diagnostic block explaining the likely cause and the fix: | Symptom | Likely cause | Fix to suggest | |---|---|---| | `online: false` AND `type: local` | Obsidian not runnin