Skills obsidian-markdown
📦

obsidian-markdown

Safe

Create Obsidian Markdown Notes

Also available from: kepano

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.

Supports: Claude Codex Code(CC)
🥉 73 Bronze
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

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

Safe
v1 • 2/24/2026

All 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.

1
Files scanned
621
Lines analyzed
0
findings
1
Total audits
No security issues found

Detected Patterns

False Positive: Markdown Backtick Syntax Flagged as Shell CommandsFalse Positive: Documentation URLs Flagged as Network RequestsFalse Positive: YAML Frontmatter and Block IDs Misidentified
Audited by: claude

Quality Score

38
Architecture
100
Maintainability
87
Content
50
Community
100
Security
87
Spec Compliance

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

Basic Note Creation
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.
Link to Specific Section
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.
Complex Property Setup
Create a note with multiple property types: text, number, checkbox, date, list of tags, and related links using Obsidian properties syntax.
Callout with Foldable Content
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?
Obsidian Flavored Markdown extends standard Markdown with features like wikilinks, callouts, embeds, and frontmatter properties for note metadata.
What is the difference between wikilinks and Markdown links?
Wikilinks use double brackets [[Note Name]] and automatically create links to notes. Markdown links use [text](url) syntax and require full file paths or URLs.
How do I link to a specific heading in another note?
Use wikilink syntax with # symbol: [[Note Name#Heading]]. The heading must exist in the target note.
What are Obsidian properties?
Properties are YAML key-value pairs at the top of a note (frontmatter) that add metadata like tags, dates, aliases, and custom fields.
Can I embed entire notes or just parts?
You can embed full notes with ![[Note Name]], specific headings with ![[Note Name#Heading]], or specific blocks with ![[Note Name#^block-id]].
What callout types does Obsidian support?
Obsidian supports: note, abstract, info, todo, tip, success, question, warning, failure, danger, bug, example, and quote.

Developer Details

File structure

📄 SKILL.md