SKILL

Obsidian Markdown

Use Obsidian-specific syntax accurately. Do not spend tokens explaining ordinary
CommonMark or GFM unless the user asks.

Workflow

1. Preserve existing frontmatter keys and formatting when editing a note.
2. Use wikilinks for vault notes and Markdown links for external URLs.
3. Use embeds, callouts, properties, tags, comments, and block references only
   when they improve the requested note.
4. Check link targets, YAML validity, and block IDs after editing.
5. Read the focused reference file when the task needs more syntax detail.

Wikilinks and block references

[[Note Name]]
[[Note Name|Display Text]]
[[Note Name#heading|Heading]]
[[Note Name#^block-id|^block-id]]
[[#heading-in-this-note|Heading in this note]]
 
This paragraph is addressable. ^block-id

Put a block ID on its own line after a list or quote block.

Embeds

Prefix a wikilink with !:

![[Note Name]]
![[Note Name#heading|Heading]]
![[image.png|300]]
![[document.pdf#page=3|page=3]]

See Embeds for media, PDF, and query forms.

Callouts

> [!warning] Custom title
> 
> Important content.
 
> [!faq]- Collapsed by default
> 
> Foldable content.

See Callouts for types, aliases, folding, and nesting.

Properties, tags, and comments

---
title: My Note
date: 2026-07-21
tags:
  - project
aliases:
  - Alternate Name
related: "[[Other Note]]"
---

Quote wikilinks used as YAML values. See
Properties for supported property types and tag rules.

Use tag for inline tags. Hide content from reading view with
or a matching pair of %% markers on
separate lines.

Attribution

Adapted from kepano/obsidian-skills at revision
a1dc48e68138490d522c04cbf5822214c6eb1202. See LICENSE.