- Home
- Skills
- Kepano
- Obsidian Skills
- Obsidian Markdown
obsidian-markdown_skill
8.3k
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill kepano/obsidian-skills --skill obsidian-markdown- SKILL.md10.6 KB
Overview
This skill creates and edits Obsidian Flavored Markdown, including wikilinks, embeds, callouts, frontmatter, tags, and other Obsidian-specific syntax. It produces valid .md content optimized for Obsidian vaults and reading/editing in the Obsidian app. Use it to author notes, convert content to Obsidian format, or modify existing notes while preserving Obsidian features.
How this skill works
The skill generates or transforms Markdown using CommonMark/GFM plus Obsidian extensions: [[wikilinks]], ![[embeds]], YAML frontmatter, callouts (>[!type]), block IDs (^id), inline and block math, Mermaid diagrams, task lists, and hidden comments. It respects URL encoding for Markdown links, escapes characters for tables and pipes, and creates syntactically correct examples for use in Obsidian.
When to use it
- Author new Obsidian notes with frontmatter, tags, and aliases
- Convert plain Markdown or HTML into Obsidian-compatible markdown
- Create internal links, anchors, and block references for a vault
- Embed images, PDFs, audio, or other notes using Obsidian embeds
- Build callouts, foldable sections, or task lists for project notes
- Add Mermaid diagrams, LaTeX math, or footnotes in notes
Best practices
- Put metadata in YAML frontmatter at the top of the file for properties and tags
- Use wikilinks ([[Note]]) for internal navigation and URL-encoded Markdown links for external paths
- Assign block IDs (^id) to paragraphs or lists you want to reference directly
- Escape pipes and special characters inside tables and inline code to avoid rendering issues
- Prefer embeds (![[file]]) for reusing note content and use size hints for images (![[image.png|300]])
- Use callout types consistently and add custom CSS classes for visual customization when needed
Example use cases
- Create a project note with frontmatter, tasks, and related note embeds
- Transform meeting minutes into a note with block-linked decisions and action items
- Author a technical note with code blocks, math, and a Mermaid architecture diagram
- Add tags and aliases to a collection of notes for better vault organization
- Produce a shareable Markdown snippet with Obsidian callouts and embedded images
FAQ
Use a wikilink with a hash: [[Note Name#Heading]] or add a display alias [[Note Name#Heading|Text]].
How do I reference a specific block?
Add a block ID at the end of the paragraph (e.g., ^my-block) and reference it with [[Note Name#^my-block]].
Can I include LaTeX and diagrams in the same note?
Yes. Use $...$ for inline math, $$...$$ for block math, and fenced ```mermaid blocks for diagrams.