template-executelisted

# template-execute Call the obsidian-router `execute_template` MCP tool with arguments parsed from $ARGUMENTS. ## Arguments **Required**: - `name` — path to the template file in the vault (e.g. `Templates/Daily.md`). **Optional**: - `vault` — omit for default. - `arguments` — key/value object exposed inside the template via `tp.mcpTools.prompt("key")`. Note: directly under `tp`, NOT under `tp.user`. - `createFile` — if true, save the rendered output to `targetPath`. - `targetPath` — path where to save (required when `createFile: true`). ## Argument parsing from $ARGUMENTS - bare path → `name` only, no `createFile` (preview mode) - `name=X arguments={"k":"v"} createFile=true targetPath=Y` - conversational: *"execute Templates/Trade.md with ticker AAPL and create file Trades/AAPL.md"* → infer the structure ## Pre-requisites The target vault must have the `templater-obsidian` plugin enabled. If the tool returns 503 with "Templater plugin is not available", surface that clearly. ## Footgun — `tp.mcpTools` is NOT under `tp.user` The `obsidian-mcp-router-bridge` plugin (which exposes `/templates/execute`) monkey-patches Templater so `tp.mcpTools.prompt("key")` returns whatever you put in the `arguments` map. This is **directly under `tp`**, not under `tp.user` (which is the convention for Templater user scripts) — easy footgun. When writing a template that will be invoked via this skill, prompt arguments like: ``` <% tp.mcpTools.prompt("ticker") %> ``` NOT: ``` <% tp.