obsidian-vault
by mattpocockobsidian-vault helps search, create, and connect Obsidian notes using Title Case filenames, [[wikilinks]], and index notes. It fits obsidian-vault for Knowledge Bases workflows where linking and note structure matter more than folders.
This skill scores 71/100, which means it is list-worthy but best presented with a caveat: it gives agents a usable, specific workflow for working inside an Obsidian vault, but the implementation guidance is fairly narrow and mostly file-path based. For directory users, that means it should reduce guesswork for note search, creation, and linking tasks, though it may not cover broader vault management scenarios.
- Clear trigger language for search, create, and organize note tasks in Obsidian.
- Concrete vault conventions are documented, including title case, flat root structure, wikilinks, and index notes.
- Provides direct shell commands for filename/content search and backlink discovery, which improves agent execution.
- Guidance is scoped to one hardcoded vault path, so portability to other vaults is limited.
- No install command, supporting files, or deeper workflow rules are provided, so agents may still need some manual interpretation.
Overview of obsidian-vault skill
What obsidian-vault does
The obsidian-vault skill helps you search, create, and connect notes inside an Obsidian vault using the vault’s own conventions: Title Case filenames, [[wikilinks]], and index notes. It is best for agents or users who need to work inside an existing knowledge base without breaking its structure.
Who should use it
Use the obsidian-vault skill if your job is to find related notes, add a new note that fits the vault, or map a topic into an index note. It is a strong fit for Obsidian-based research systems, especially obsidian-vault for Knowledge Bases workflows where linking matters more than folder depth.
What makes it different
This skill is not a generic “take notes” prompt. It encodes vault-specific rules: mostly flat storage, no folder-based organization, and index notes that act as curated link lists. That reduces guesswork when an assistant needs to place a note, name it, or connect it correctly.
How to Use obsidian-vault skill
obsidian-vault install and setup
Install with npx skills add mattpocock/skills --skill obsidian-vault. After install, confirm the vault path the skill expects: /mnt/d/Obsidian Vault/AI Research/. If your environment uses a different path, update the workflow before asking for file actions so the agent does not search the wrong directory.
What to provide in your prompt
For best obsidian-vault usage, give the agent a clear note goal, a target term, and the action you want: search, create, or link. Example: “Find existing notes about prompt evaluation, identify the best index note, and draft a new Title Case note with wikilinks to related entries.” This is better than “organize my notes” because it tells the skill what to do and what success looks like.
Files and paths to read first
Start with SKILL.md to learn the vault rules, then inspect any note titles that match your topic. The repository is sparse, so the main source of truth is the skill file itself. For vault work, the practical paths are the vault root, index notes, and any note names returned by filename search. If you need backlinks, search for [[Note Title]] patterns across the vault.
Workflow that gets reliable output
- Search by filename first when you know the topic.
- Search by content when the title is unclear.
- Open the relevant index note before drafting a new note.
- Write the note as a unit of learning, then add related links at the bottom.
- Use Title Case and avoid introducing folders unless the vault already does.
obsidian-vault skill FAQ
Is obsidian-vault only for Obsidian users?
Yes, primarily. The skill is designed around Obsidian conventions, so it is most useful when the target system uses [[wikilinks]], index notes, and a curated vault structure. If you only need a plain markdown draft, a generic writing prompt is usually enough.
When should I not use this skill?
Do not use obsidian-vault if the content is not meant to live in a knowledge base, or if you need database-style task management rather than linked notes. It is also a poor fit when the vault structure is unknown and you cannot verify naming or linking rules.
Is it beginner-friendly?
Yes, if you can describe a topic and accept a structured output. The main learning curve is not Obsidian itself but the vault’s conventions: Title Case naming, link-first organization, and index-note navigation. Those rules are simple, but they matter.
How does it compare with a normal prompt?
A normal prompt may produce a decent note, but the obsidian-vault skill adds workflow constraints that improve fit: where to search, how to name the note, and how to connect it to existing entries. That makes it more useful for obsidian-vault for Knowledge Bases work where consistency is part of the deliverable.
How to Improve obsidian-vault skill
Give the skill a sharper note intent
Stronger inputs reduce weak notes. Instead of “make an index note,” say “create an index note for RAG evaluation, using existing related titles and linking only the most relevant dependencies.” This helps obsidian-vault decide what belongs in the note and what should stay out.
Provide the existing note universe
The biggest quality gain comes from naming nearby notes, index notes, or terms you already know. If you can point to one anchor note, the skill can infer the right links and avoid duplicate titles. Without anchors, it may create a note that is technically valid but poorly integrated.
Check naming and link quality after the first draft
Review whether the title is Title Case, whether links point to real note titles, and whether the note bottom includes the right dependencies. If the draft feels isolated, ask for a second pass that adds backlinks, merges duplicates, or rewrites the title to match existing patterns.