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.
This skill enables Claude Code to create and edit valid Obsidian Flavored Markdown including wikilinks, embeds, callouts, properties, and all related syntax.
Paragraphs are separated by blank lines. Single line breaks within a paragraph are ignored unless you use:
<br> for explicit breaks# Heading 1
## Heading 2
### Heading 3
#### Heading 4
##### Heading 5
###### Heading 6
**Bold text**
*Italic text*
***Bold and italic***
~~Strikethrough~~
==Highlighted text==
[[Note Name]]
[[Note Name|Display Text]]
[[Folder/Note Name]]
[[Note Name#Heading]]
[[Note Name#Heading|Display Text]]
[[#Heading in Current Note]]
[[Note Name#^block-id]]
[[Note Name#^block-id|Display Text]]
[[#^block-id]]
Add a block ID at the end of any paragraph or list item:
This is a paragraph you can reference. ^my-block-id
- List item with ID ^list-block
![[Note Name]]
![[Note Name#Heading]]
![[Note Name#^block-id]]
![[image.png]]
![[image.png|400]]
![[image.png|400x300]]
![[audio.mp3]]
![[document.pdf]]
![[document.pdf#page=5]]
![[document.pdf#height=400]]
![[video.mp4]]
> [!note]
> This is a note callout.
> [!warning]
> This is a warning callout.
> [!tip] Custom Title
> This callout has a custom title.
| Type | Aliases | Description |
|---|---|---|
note | Default blue info box | |
abstract | summary, tldr | Abstract/summary |
info | Information | |
todo | Task/todo item | |
tip | hint, important | Helpful tip |
success | check, done | Success message |
question | help, faq | Question/FAQ |
warning | caution, attention | Warning message |
failure | fail, missing | Failure message |
danger | error | Error/danger |
bug | Bug report | |
example | Example content | |
quote | cite | Quotation |
> [!note]+ Expanded by default
> Content visible initially.
> [!note]- Collapsed by default
> Content hidden initially.
> [!question] Can callouts be nested?
> > [!answer] Yes!
> > Callouts can be nested inside each other.
- Item 1
- Item 2
- Nested item
- Another nested item
- Item 3
1. First item
2. Second item
1. Nested numbered item
3. Third item
- [ ] Uncompleted task
- [x] Completed task
- [ ] Another task
Use `inline code` for short snippets.
```javascript
function hello() {
console.log("Hello, world!");
}
```
Obsidian supports syntax highlighting for many languages including:
javascript, typescript, python, rust, go, java, c, cpp, csharp, ruby, php, html, css, json, yaml, markdown, bash, sql, and many more.
| Header 1 | Header 2 | Header 3 |
|----------|:--------:|---------:|
| Left | Center | Right |
| aligned | aligned | aligned |
The equation $E = mc^2$ is famous.
$$
\frac{-b \pm \sqrt{b^2 - 4ac}}{2a}
$$
```mermaid
graph TD
A[Start] --> B{Decision}
B -->|Yes| C[Do Something]
B -->|No| D[Do Something Else]
C --> E[End]
D --> E
```
This is a sentence with a footnote.[^1]
[^1]: This is the footnote content.
%%
This is a comment that won't be rendered.
%%
Inline %%comment%% within text.
---