Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
Install with Tessl CLI
npx tessl i github:kepano/obsidian-skills --skill obsidian-markdown95
Does it follow best practices?
Validation for skill structure
Frontmatter properties and wikilinks
Frontmatter present
100%
100%
Title property
100%
100%
Date property format
100%
100%
Numeric property
100%
100%
Checkbox property
100%
100%
Tags in frontmatter
100%
100%
Nested tags
100%
100%
Aliases property
100%
100%
Wikilinks for internal notes
100%
100%
Custom display text wikilink
100%
100%
External link uses markdown syntax
100%
100%
Highlight syntax
100%
100%
Comment syntax
100%
100%
Without context: $0.1860 · 56s · 13 turns · 19 in / 2,575 out tokens
With context: $0.3940 · 1m 25s · 22 turns · 735 in / 3,937 out tokens
Callouts and embedded content
Callout basic syntax
100%
100%
Warning/danger callout type
100%
100%
Tip callout type
100%
100%
Collapsed callout
100%
100%
Custom callout title
100%
100%
Nested callout
100%
100%
Image embed with width
100%
100%
Section embed
100%
100%
Block ID definition
100%
100%
Heading link
100%
100%
Frontmatter present
100%
100%
Without context: $0.2907 · 1m 23s · 16 turns · 23 in / 4,041 out tokens
With context: $0.3278 · 1m 14s · 18 turns · 727 in / 3,279 out tokens
Mermaid diagrams with Obsidian node links
Mermaid diagram present
100%
100%
Mermaid internal-link class
0%
100%
Multiple nodes linked
0%
100%
Block ID on paragraph
100%
100%
Block ID placement for non-paragraph
100%
100%
Same-note block reference
0%
100%
Cross-note heading link
100%
100%
Cross-note block link
100%
100%
Embedded search query
0%
100%
Frontmatter with custom property
100%
100%
Without context: $0.2352 · 59s · 12 turns · 19 in / 2,942 out tokens
With context: $0.3931 · 1m 31s · 20 turns · 766 in / 4,650 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.