agentleFS
tboome33tboome33/obsidian-mcp-router/skills/discover-list-vaults/SKILL.md

discover-list-vaults

Skill1 starsChanged 7 months agoApache-2.0View on GitHub

List all configured Obsidian vaults — active vaults with online status, latency, and metadata, AND disabled vaults (skipped by the disabledVaults config). Returns three fields: defaultVault, vaults[] (active), disabled[] (skipped).

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call the obsidian-router list_vaults MCP tool.

    line 16
  2. Very specific:

    Don't pass any arguments — list_vaults takes none.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

discover-list-vaults

Call the obsidian-router list_vaults MCP tool. It takes no arguments.

The tool pings every ACTIVE vault in parallel and returns:

  • defaultVault — vault used when calls omit a vault argument (resolved by the 5-tier cascade)
  • configPath — where the registry is loaded from
  • vaults[] — active vaults, each with name, type (local|remote), baseUrl, online, latencyMs, missingApiKey, error?, isDefault
  • disabled[] — vaults this session cannot use right now. NOT pinged. Each entry: name, type, reason, awaitingDeclaration — and that last field is the one that matters, because the array holds two different absences:
    • awaitingDeclaration: false — the operator said no: skipped by the disabledVaults config, or a malformed entry. Nothing the user does in a session changes it.
    • awaitingDeclaration: true — the vault is real, enabled and healthy; this router install has vaultReach: "declared" active and this workspace has simply never declared it. This is the case with a fix the user can act on in-session: confirm_workspace_binding binds this workspace to it (and opens it if its Obsidian is not running), which is what makes it answer. Never describe such a vault as unavailable — it is one call away, and config.json is not the way. /bind-workspace offers exactly these as candidates.

Adapt the response to what the user asked

  • "which vaults are active" → render only the vaults[] table, ignore disabled[]
  • "which vaults are disabled" → render only the disabled[] list, mention the count of active in one line
  • "list all my vaults" / "which vaults do I have" (default) → render BOTH: the active table at the top, then a "Disabled (N)" subsection below with the disabled list

Active table format

  • One status line: <n> active vault(s) · <m> online · default: <name>
  • A markdown table with columns: name | type | status (✅/⚠️/❌) | latency | path or baseUrl
  • Highlight any vault that is offline, has missingApiKey: true, or returns an error

For unhealthy active vaults, suggest the matching meta-status skill or a concrete fix.

Don't pass any arguments — list_vaults takes none.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.