Claude Skill for Obsidian: Turn Claude Into an Obsidian Note Agent

Out of the box, an AI assistant writes plain Markdown that ignores everything that makes Obsidian powerful: [[wikilinks]], embeds, callouts, and properties. A Claude skill for Obsidian fixes that. It gives Claude a set of instructions for Obsidian's specific syntax, so the notes it produces link, embed, and render the way your vault expects. This guide explains what a Claude skill for Obsidian is, how to install one, and how to use it to turn Claude into a genuine note-taking agent. The skill works with the models Claude currently spans — the latest ones being Opus 4.8, Sonnet 4.6, and Haiku 4.5 — and setup takes under 10 minutes, so we review these steps regularly to keep them accurate.

What is a Claude skill for Obsidian?

An Agent Skill is a small package of instructions and resources that teaches Claude to do a specific job well. A Claude skill for Obsidian is exactly that, focused on Obsidian's flavor of Markdown. The best-known one is the open-source obsidian-skills project from kepano (Steph Ango, Obsidian's own CEO), which teaches Claude to use Obsidian's file formats and CLI.

The point is fidelity. Without the skill, ask Claude to "link this note to my project note" and it writes a standard [text](path.md) link that Obsidian treats as a plain file reference. With a Claude skill for Obsidian, Claude knows to write [[Project]] — a real wikilink that shows up in the graph, in backlinks, and in autocomplete. The skill encodes dozens of these Obsidian-specific rules so the AI works with your vault rather than against it.

What a Claude skill for Obsidian teaches Claude

A good Claude skill for Obsidian covers the syntax that generic Markdown misses:

• Wikilinks — [[Note Name]] for internal links, including [[Note#Heading]] and [[Note#^block-id]] for headings and blocks.
• Embeds — ![[Note]] to transclude a whole note, section, image, or PDF into another.
• Callouts — typed blockquotes like > [!note] that render as styled alert boxes.
• Properties (frontmatter) — YAML metadata such as title, tags, and aliases at the top of a note.
• Tags and comments — inline #tags and %% comments %% that Obsidian understands.
• Advanced formats — newer Obsidian features like Bases and JSON Canvas.

Crucially, the skill also teaches the one rule most AIs get wrong: use [[Note Name]], never [link](path/to/note.md), for internal links. That single habit is the difference between a vault that stays connected and one that quietly fills with broken references.

How to install a Claude skill for Obsidian

There are two common ways to get a Claude skill for Obsidian working, depending on whether you use Claude Code or want it inside the Obsidian app.

Option A — with Claude Code in your vault. Add the skill files to a .claude folder in the root of your Obsidian vault (or the folder you point Claude Code at). Cloning the obsidian-skills repository into that location is enough — the next time you run Claude Code there, it picks up the skill and applies Obsidian's rules automatically.

Option B — inside the Obsidian app. The Claude Code Skills community plugin brings the same idea into Obsidian's interface: highlight text in a note, right-click to pick a skill, and get a streaming Claude response in a side panel without leaving the app. That's the smoother route if you live in Obsidian and don't want to switch to a terminal.

Either way, once the Claude skill for Obsidian is in place, you don't invoke it manually — Claude reads the skill and follows Obsidian's conventions whenever it touches a note.

How to use it: Claude as an Obsidian agent

With the skill installed, you can hand Claude the kind of note work that used to be tedious:

• Draft and link. "Create a note on this topic and link it to my related notes" produces a note with proper [[wikilinks]] into your existing vault.
• Restructure. "Split this long note into an index plus linked sub-notes" gives you connected notes with embeds, not a wall of text.
• Add metadata. "Add tags and aliases to these notes" writes correct frontmatter properties Obsidian can query.
• Clean up. "Convert these callouts and fix the broken links" repairs syntax at scale.

Pair a Claude skill for Obsidian with Claude's memory and you get an assistant that understands both your vault's structure and your ongoing context. If you want to build your own skills for other tools the same way, our guides on Claude skills and making Claude Code do anything show the pattern — the Claude skill for LinkedIn is another real-world example of the same idea applied to a different platform.

Tips for getting the best results

A Claude skill for Obsidian works best with a little setup on your side:

• Point Claude at the whole vault. Run it from your vault root so it can see existing notes and link into them, rather than from a single-file view where it can't discover [[targets]].
• Name notes the way you link them. Obsidian wikilinks resolve by note title, so consistent, human-readable filenames make Claude's links land correctly.
• Ask for structure, not just text. Prompts like "create an index note that links to these five" or "add properties and tags to these notes" get the most out of the skill's Obsidian awareness.
• Review the graph after big edits. After a large restructure, open Obsidian's graph view to confirm the new [[links]] connected the way you intended.

Because a Claude skill for Obsidian only changes how Claude writes — not your vault's data — it's safe to experiment. Worst case, you undo an edit. That low risk is what makes it worth trying even on an established vault, and it's a big reason the pattern caught on so quickly among Obsidian power users.