read-frontmatterlisted

Read frontmatter (the whole object or one key) from a file. Types are preserved (numbers stay numbers, arrays stay arrays). EN triggers: "what's the frontmatter of X", "show me the metadata of X", "read the properties of X", "what's the status of X", "get the tags on X". FR triggers : "quel est le frontmatter de X", "montre les méta de X", "lis les properties de X", "quel est le statut de X", "récupère les tags de X". Example / Exemple: EN: "what's the status of Trades/AAPL.md" FR: "quel est le statut de Trades/AAPL.md"
tboome33/obsidian-mcp-router · ★ 1 · AI & Automation · score 72

Install: claude install-skill tboome33/obsidian-mcp-router

# read-frontmatter Call the obsidian-router `get_frontmatter` MCP tool with arguments parsed from $ARGUMENTS. ## Arguments **Required**: - `path` — file path relative to vault root. **Optional**: - `vault` — vault name. Omit for default. - `key` — specific frontmatter property to retrieve. Omit to get the whole frontmatter object. ## Argument parsing from $ARGUMENTS - bare path → `path`, returns whole frontmatter - `<path> <key>` → `path` + `key` - `path=X key=Y vault=Z` ## Render the result - If a single key was requested: `<key>: <value>` with the type-preserved value (number stays number, boolean stays boolean, array shown as YAML list, etc.). If `exists: false`, say so explicitly. - If the whole frontmatter was returned: show it as a YAML-formatted code block. Note: this tool reads via `application/vnd.olrapi.note+json` content negotiation, so values keep their type (numbers, booleans, arrays, nested objects) — they aren't all flattened to strings.