This skill enables AI agents to create and edit Obsidian Flavored Markdown with proper syntax for wikilinks, callouts, embeds, properties, and other Obsidian-specific features.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "obsidian-markdown". Create a note with a callout, wikilink, and property
Expected outcome:
---
title: Project Update
date: 2024-01-15
tags:
- project
- status
---
# Project Update
> [!warning] Important
> This project requires review.
See [[Previous Notes]] for history.
Using "obsidian-markdown". Add task list with embeds
Expected outcome:
## Tasks
- [x] Complete initial draft
- [ ] Review content
- [ ] Check links
- [ ] Verify embeds
- [ ] Finalize
Security Audit
SafeAll static security findings are false positives. The skill is a documentation/reference guide for Obsidian Markdown syntax. The 'external_commands' alerts are markdown backtick syntax being misidentified as shell commands. The 'network' findings are legitimate documentation URLs (commonmark.org, help.obsidian.md) used as references. The 'weak_crypto' and 'system_reconnaissance' alerts are YAML frontmatter and Obsidian block IDs being misinterpreted.
Detected Patterns
Quality Score
What You Can Build
Generate Knowledge Base Notes
Create interconnected notes with wikilinks for building a personal knowledge management system
Format Technical Documentation
Write documentation with code blocks, callouts, and embedded files using proper syntax
Create Project Tracking Notes
Set up project notes with properties, task lists, and status tracking
Try These Prompts
Create an Obsidian note with title 'Meeting Notes', add frontmatter with date and tags, include a callout for action items, and link to other notes using wikilinks.
Create a note that links to a specific heading in another note using the wikilink syntax. Include an embed of a code block from a third note.
Create a note with multiple property types: text, number, checkbox, date, list of tags, and related links using Obsidian properties syntax.
Create a note with a foldable callout that shows a warning, includes nested content, and collapses by default.
Best Practices
- Use consistent naming conventions for wikilinks to maintain vault organization
- Add frontmatter properties to enable Obsidian queries and organization features
- Use descriptive aliases in wikilinks for readability in published notes
- Use appropriate callout types to communicate information hierarchy
Avoid
- Using standard Markdown links instead of wikilinks when linking to vault notes
- Forgetting to URL-encode spaces in Markdown-style links
- Using incorrect YAML syntax in frontmatter properties
- Not using block IDs when needing precise links to specific content
Frequently Asked Questions
What is Obsidian Flavored Markdown?
What is the difference between wikilinks and Markdown links?
How do I link to a specific heading in another note?
What are Obsidian properties?
Can I embed entire notes or just parts?
What callout types does Obsidian support?
Developer Details
Author
ZhanlinCuiLicense
MIT
Repository
https://github.com/ZhanlinCui/Ultimate-Agent-Skills-Collection/tree/main/obsidian-markdownRef
main
File structure
📄 SKILL.md