Obsidian Markdown Skill: check the rendered note, not just the file
Steph Ango’s instructions for Obsidian-specific Markdown, including properties, wikilinks, embeds and callouts. Start with a test note and verify links and rendering.
Original author: Steph Ango (@kepano) and contributors
Source: Obsidian Skills · kepano
Give the agent a note with an expected result
The obsidian-markdown Skill in kepano/obsidian-skills explains Obsidian-specific syntax on top of standard Markdown. It covers properties, wikilinks, embeds and callouts. For a first task, ask for a test note with a title property, a link to an existing note and a warning callout. Check the target and the reading view before moving the result into a working vault.
Separate writing from rendering
The official workflow ends with verification in Obsidian’s reading view. A successful file save does not prove that an embed resolves or a diagram is displayed. The repository documents Claude Code, Codex and OpenCode installation paths; review the current instructions for your host rather than assuming their directory layouts are identical.
Learn from the reported boundaries
In issue 149, g524843184-maker describes checks in Obsidian 1.14.4 on macOS. They report working wikilinks and callouts, but note a first-use Mermaid trust prompt and tags ending at a space. These are useful checks for a generated note, not a reason to bypass the prompt. Boloop has not repeated that vault test or installed the Skill. This recommendation focuses on Markdown; it does not validate the collection’s CLI, Bases or other components.
Sources and further reading
- Obsidian Skills repository and host-specific installationOfficial documentation · Steph Ango and contributors
- obsidian-markdown SKILL.mdOfficial documentation · Steph Ango and contributors
- Rendered note checks and reported limitations #149Usage record · g524843184-maker
- Collection MIT licenseOfficial documentation · Steph Ango
- Obsidian supported application and project markOfficial documentation · Obsidian