obsidian-meta-bindlisted

# Meta Bind — buttons, inputs, view fields This skill covers the **Meta Bind** Obsidian plugin (id `obsidian-meta-bind-plugin`, by Moritz Jung). Authoring rules, full schemas, JS Engine integration, and the validation traps that cost hours when not known up front. Docs root: <https://www.moritzjung.dev/obsidian-meta-bind-plugin-docs/>. ## When to use this skill Reach for this skill on any of: - User mentions Meta Bind, `INPUT[...]`, `VIEW[...]`, `BUTTON[...]`, ` ```meta-bind-button `, ` ```meta-bind ` code blocks. - User wants to add an interactive widget into a note (toggle, slider, button, dropdown, date picker, etc.). - User reports `META_BIND_ERROR`, `[MB_BUTTON]`, `Button ID not Found`, "validation failed", "Invalid input at 'style'", or any Meta Bind error overlay. - User wants to bind metadata across files (`file^property`, `memory^...`, `globalMemory^...`). - User needs to wire a button to an Obsidian command, JS code, file open, metadata mutation, or templater. - User authors a tracker or dashboard with declarative INPUT fields tied to frontmatter. ## Prerequisites Confirm before debugging: 1. **Meta Bind plugin installed and enabled.** Check `.obsidian/plugins/obsidian-meta-bind-plugin/manifest.json`. 2. **JS Engine plugin** installed and enabled if any button uses `action.type: inlineJS` or `js`. Without it, JS actions silently fail. 3. **Settings flag `enableJs: true`** in `.obsidian/plugins/obsidian-meta-bind-plugin/data.json`. JS-based buttons and JS vie