Guide for creating and editing Obsidian notes using Obsidian Flavored Markdown (OFM). Covers wikilinks, embeds, callouts, YAML properties, and knowledge organization best practices.
NewMaintained
Automatic
◆Knowledge Management pack
Last verified 8/13/2026
What it changes
Passed 20 of 23 test cases with the skill, and 20 of 23 without it.
Without skill87%
With skill87%
Checks it passed that the model alone missed
Asks the user to clarify or confirm the daily note folder location before generating the entry.
1 fixed19 passed either way2 still failing1 broke
Pass-rate lift
0 pp
Tokens
+13%
Agent turns
0%
Response time
-40%
Model gemini-3.6-flashMeasured 8/13/2026v120 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
Can you set up today's daily note entry for my Obsidian vault? I need a structured document to track my daily tasks, log meeting notes throughout the day, and write down end-of-day reflections.
What was checked, without and with the skill
Checked
Without skill
With skill
Asks the user to clarify or confirm the daily note folder location before generating the entry.
Missed
Passed
case-02 · gemini-3.6-flash · 8/13/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md108 linessingle file
Obsidian Flavored Markdown Guide
When creating or editing notes in the user's Obsidian vault, follow these conventions.
Core Principles
Ask before creating — confirm the save location and vault structure first.
Use OFM syntax — prefer wikilinks, callouts, and embeds over standard Markdown equivalents.
Atomic notes — one concept per note, connected through links.
Metadata-driven — use YAML frontmatter for searchability and Dataview queries.
Wikilinks
[[Note Name]] # link to a note
[[Note Name|Display Text]] # custom display text
[[Note Name#Heading]] # link to a heading
[[Note Name#^block-id]] # link to a block
Use descriptive, unique note names. Avoid special characters: [ ] # ^ | \
Prefer full note names over path-based links (Obsidian auto-resolves)