obsidian-vault
- Repo stars 130,981
- Forks 11,408
- Author updated Jun 12, 2026, 08:25 AM
- Author repo skills
- Domain
- Productivity
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @mattpocock · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: obsidian-vault
description: Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when…
category: productivity
runtime: no special runtime
---
# obsidian-vault output preview
## PART A: Task fit
- Use case: Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian. Mostly flat at root level. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Vault location / Naming conventions / Linking” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian. Mostly flat at root level. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Vault location / Naming conventions / Linking” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/mnt`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Vault location / Naming conventions / Linking”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: obsidian-vault
description: Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when…
category: productivity
source: mattpocock/skills
---
# obsidian-vault
## When to use
- Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, cr…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Vault location / Naming conventions / Linking” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "obsidian-vault" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Vault location / Naming conventions / Linking
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Obsidian Vault
Vault location
/mnt/d/Obsidian Vault/AI Research/
Mostly flat at root level.
Naming conventions
- Index notes: aggregate related topics (e.g.,
Ralph Wiggum Index.md,Skills Index.md,RAG Index.md) - Title case for all note names
- No folders for organization - use links and index notes instead
Linking
- Use Obsidian
[[wikilinks]]syntax:[[Note Title]] - Notes link to dependencies/related notes at the bottom
- Index notes are just lists of
[[wikilinks]]
Workflows
Search for notes
# Search by filename
find "/mnt/d/Obsidian Vault/AI Research/" -name "*.md" | grep -i "keyword"
# Search by content
grep -rl "keyword" "/mnt/d/Obsidian Vault/AI Research/" --include="*.md"
Or use Grep/Glob tools directly on the vault path.
Create a new note
- Use Title Case for filename
- Write content as a unit of learning (per vault rules)
- Add
[[wikilinks]]to related notes at the bottom - If part of a numbered sequence, use the hierarchical numbering scheme
Find related notes
Search for [[Note Title]] across the vault to find backlinks:
grep -rl "\\[\\[Note Title\\]\\]" "/mnt/d/Obsidian Vault/AI Research/"
Find index notes
find "/mnt/d/Obsidian Vault/AI Research/" -name "*Index*"
Decide Fit First
Design Intent
How To Use It
Boundaries And Review