← ClaudeAtlas

obsidian-markdownlisted

Explain, draft, or validate Obsidian Flavored Markdown: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid. Use when the user asks for Obsidian note formatting or syntax help, not for general Markdown or broad vault operations.
nathanaday/atlas-obsidian · ★ 0 · Data & Documents · score 72
Install: claude install-skill nathanaday/atlas-obsidian
# Obsidian Flavored Markdown A compact fallback for Obsidian-specific syntax. Prefer a separately installed `kepano/obsidian-skills` `obsidian-markdown` skill when available, then [Obsidian Help](https://help.obsidian.md/), for detailed or version-sensitive questions. Answer syntax questions read-only. If the user asks for a vault edit, draft the complete page, then build one plan of kind `markdown` with only `wiki/` targets as [operations.md](../wiki/references/operations.md) describes. A new canonical page also joins the index or a MOC in that plan. Never write a page directly. ## Properties Use flat YAML properties and `YYYY-MM-DD` dates. Quote wikilinks inside YAML. ```yaml --- type: concept title: "Contextual Retrieval" created: 2026-09-12 updated: 2026-09-12 status: developing tags: - retrieval - ai/knowledge aliases: - Context-aware retrieval related: - "[[Retrieval]]" sources: - "[[Anthropic Contextual Retrieval]]" --- ``` Do not nest objects in generated properties. Use block lists rather than inline arrays. Quote numeric-only tag values, for example `- "2026"`. Keep unknown existing properties unless the requested edit changes them. ## Wikilinks and embeds ```markdown [[Note Name]] [[Note Name|Display text]] [[Note Name#Heading]] [[Note Name#^block-id]] [[Folder/Note Name]] This paragraph is addressable. ^evidence-block ![[Note Name#Summary]] ![[diagram.png|480]] ![[paper.pdf#page=3]] ``` Match the target file name exactly. Use a folder-qualifie