tboome33

Meta Audit Bridge Readiness — Security skill for Claude Code

Security community

Audit click-to-open readiness across all configured vaults — checks bridge ≥ 0.2.0, Local REST API ≥ 4.0.0, insecure HTTP enabled, AND a live probe that confirms /open/ is actually registered in-me.

How to install Meta Audit Bridge Readiness

Installs to ~/.claude/skills/tboome33-obsidian-mcp-router-meta-audit-bridge-readiness/SKILL.md

Terminal

mkdir -p ~/.claude/skills/tboome33-obsidian-mcp-router-meta-audit-bridge-readiness && curl -fsSL https://raw.githubusercontent.com/tboome33/obsidian-mcp-router/HEAD/commands/meta-audit-bridge-readiness.md -o ~/.claude/skills/tboome33-obsidian-mcp-router-meta-audit-bridge-readiness/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Meta Audit Bridge Readiness does

description: Audit click-to-open readiness across all configured vaults — checks bridge ≥ 0.2.0, Local REST API ≥ 4.0.0, insecure HTTP enabled, AND a live probe that confirms `/open/*` is actually registered in-memory. (Skill `meta-audit-bridge-readiness` handles natural-language triggers.)

meta-audit-bridge-readiness

Read-only diagnostic of the click-to-open feature (`http://127.0.0.1:/open/` links that open files in Obsidian). Complement of `meta-status`: that one check

Alternatives in Security

Free Code — The free build of Claude Code 8.1k ★
T3mp3st — autonomous red teaming platform; multi-agent offensive-security meta-harness 5.7k ★
Marketplace — Security-audited skills for Claude, Codex & Claude Code 247 ★