agentleFS
tboome33tboome33/obsidian-mcp-router/skills/meta-audit-bridge-readiness/SKILL.md

meta-audit-bridge-readiness

Skill1 starsChanged 7 months agoApache-2.0View on GitHub

Audit every Obsidian vault for click-to-open (`GET /mcp-router-bridge/open/<path>`, or `/open/<path>` before bridge 0.10.0) readiness. Verifies the FOUR prerequisites — mcp-router-bridge ≥ 0.2.0, Local REST API ≥ 4.0.0, `enableInsecureServer: true`, AND a live probe that confirms the route is actually registered in-memory (catches the "files on disk are right but Obsidian needs reload" case). Triggers (EN) `audit my click-to-open links`, `check bridge readiness`, `are my /open links working`, `audit vault click-to-open`, `which vaults need a reload`, `verify bridge plugin install`. Triggers (FR) `audite les liens cliquables`, `vérifie le bridge sur tous les vaults`, `est-ce que mes liens /open marchent`, `audit click-to-open`, `quels vaults ont besoin d'un reload`, `audit du bridge`.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the audit script and capture its JSON output:

    line 23
  2. Very specific:

    After npm run deploy:all in the bridge repo (the audit is the natural "did it actually take effect" check)

    line 84
  3. Distinctive:

    When the user creates several click-to-open links in a row to vaults you haven't recently verified

    line 86
  4. Distinctive:

    Don't auto-fix anything. Surface the problem with the specific command to run.

    line 90
  5. Very specific:

    Don't expose API keys (the script never reads them, but if you fall back to reading data.json directly, redact the apiKey field).

    line 91
  6. Very specific:

    Don't run a probe against the HTTPS port — the audit deliberately uses HTTP/insecurePort because that's what clickable links use on Windows …

    line 92
  7. Distinctive:

    If the audit script itself errors out (exit code 2 with stderr):

    line 96

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

meta-audit-bridge-readiness

Diagnostic read-only de la fonctionnalité click-to-open (http://127.0.0.1:<port>/mcp-router-bridge/open/<path> — /open/<path> avant le bridge 0.10.0 — qui ouvre un fichier dans Obsidian). C'est le complément de [[meta-status]] : meta-status vérifie que le router peut joindre chaque vault ; ce skill-là vérifie que les liens cliquables que tu mets dans le chat fonctionnent vraiment.

Quatre prérequis sont checkés par vault :

#CheckSi KO
1mcp-router-bridge plugin ≥ v0.2.0 installéroute handler click-to-open absent (sur Local REST API 5.4.0, il faut le bridge ≥ 0.10.0) → npm run deploy:all dans le bridge repo
2obsidian-local-rest-api plugin ≥ v4.0.0 installéméthode addPublicRoute() absente → update via Settings Community Plugins, ou copy v4.x dans .template + --sync-all --force
3enableInsecureServer: true + insecurePort set dans .obsidian/plugins/obsidian-local-rest-api/data.jsonserveur HTTP non-chiffré coupé → AV (Bitdefender etc.) va dropper les HTTPS auto-signés silencieusement
4Live probe : GET http://127.0.0.1:<insecurePort>/mcp-router-bridge/open/__nonexistent__.md, puis /open/__nonexistent__.md, retourne 404 (= route enregistrée) plutôt que 401 (= middleware auth catch-all = route pas registered)Obsidian a du code stale en mémoire → Ctrl+P → "Reload app without saving"

Le check #4 est le plus important — c'est lui qui détecte le cas où les fichiers sur disque sont corrects mais Obsidian tourne encore avec l'ancien code (n'a pas reload depuis le sync). Les checks 1-3 sont des static-version checks.

Steps

  1. Run the audit script and capture its JSON output:
    node "<router-repo>/scripts/meta-audit-bridge-readiness.mjs" --json
    (or for a single vault: --vault <slug-or-path>)
  2. Parse the JSON. Schema:
    {
      "minBridge": "0.2.0",
      "minLra": "4.0.0",
      "results": [
        {
          "vaultName": "DEDIBOX",
          "vaultPath": "C:\\VAULTS\\DEDIBOX",
          "httpsPort": 27131,
          "insecurePort": 27141,
          "bridgeVersion": "0.2.0",
          "lraVersion": "4.0.2",
          "enableInsecureServer": true,
          "checks": {
            "bridgeInstalled": true,
            "bridgeOk": true,
            "lraInstalled": true,
            "lraOk": true,
            "insecureEnabled": true,
            "routeLive": true,
            "probeResult": { "status": 404, "error": null }
          },
          "ready": true
        }
      ],
      "summary": { "total": 10, "ready": 3, "notReady": 7 }
    }
  3. Render as a compact table:
    • First line: <total> vault(s) audited · <ready> ready · <notReady> need attention
    • Table: vault | bridge | LRA | insecure | open route | ready? (la colonne dit quel préfixe a répondu)
    • ✅ for ready, ❌ for not ready, version numbers in yellow if below threshold
  4. For each vault with ready: false, output the first matching remediation in this order:
Failed checkRemediation to surface
!bridgeInstalledbridge plugin missing → node scripts/setup-vault.mjs "<vaultPath>" --sync-plugins --force
!bridgeOkbridge v<version> < v0.2.0 → in obsidian-mcp-router-bridge repo: npm run deploy:all
!lraInstalledLocal REST API missing → install via Obsidian Settings → Community plugins
!lraOkLRA v<version> < v4.0.0 → update via Obsidian Settings, OR copy v4.x main.js+manifest+styles into .template, then node scripts/setup-vault.mjs --sync-all --force
!insecureEnablededit .obsidian/plugins/obsidian-local-rest-api/data.json, set enableInsecureServer: true + a free insecurePort, reload Obsidian
routeLive === false AND probe error ECONNREFUSEDObsidian not running on this vault, OR Local REST API plugin disabled, OR insecure server toggle off
routeLive === false AND probe status 401files OK but stale code in memory → Ctrl+P → "Reload app without saving" in this vault's Obsidian
  1. End with one of:
    • All ready → 🎉 All <total> vaults are click-to-open ready.
    • Some not ready → Apply fixes above, then re-run /obsidian-router:meta-audit-bridge-readiness to verify.

When to nudge the user without being asked

Proactively offer this audit when:

  • The user mentions a 40101 / "Authorization required" error on a click-to-open link
  • After npm run deploy:all in the bridge repo (the audit is the natural "did it actually take effect" check)
  • After setup-vault.mjs --sync-all (same)
  • When the user creates several click-to-open links in a row to vaults you haven't recently verified

Don't

  • Don't auto-fix anything. Surface the problem with the specific command to run. The user decides what gets reloaded / re-synced.
  • Don't expose API keys (the script never reads them, but if you fall back to reading data.json directly, redact the apiKey field).
  • Don't run a probe against the HTTPS port — the audit deliberately uses HTTP/insecurePort because that's what clickable links use on Windows (AV intercepts self-signed HTTPS loopback silently — see wiki/obsidian-mcp-router-bridge/project-bridge.md "Troubleshooting" for the full rationale).

When this skill fails

If the audit script itself errors out (exit code 2 with stderr):

  • Config not found → ~/.claude/obsidian-mcp-router/config.json missing → run setup-vault.mjs --init-reference <path> first
  • Crash → relay the stack trace; this is a bug, not user error

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.