obsidian

Read, search, create, and edit notes in an Obsidian vault using native file tools.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill obsidian-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian
Source: https://github.com/yakeworld/Synthos/tree/main/skills/extended/external-automation/automation-skills/productivity/obsidian
Command: npx skills add https://github.com/yakeworld/Synthos --skill obsidian-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working with an Obsidian vault through shell commands breaks on paths with spaces, unexpanded environment variables, and quoting issues. This Skill standardizes note operations and vault initialization using native file tools with a resolved absolute vault path. ## Core Features & Use Cases - Tier 1 Note Operations: Read, list, search (by filename or content), create, append, and patch notes inside an existing vault using read_file, write_file, patch, and search_files instead of cat, find, grep, or ls. - Tier 2 Vault Initialization: Convert a project directory into an Obsidian knowledge base with .obsidian/ config, _INDEX.md MOC chains, YAML frontmatter, wikilink reference sections, and symlinks to external source files. - Use Case: Turn a research repository full of Markdown, TeX, and PDF files into a navigable Obsidian knowledge base with graph view, backlinks, and a fact_store sync script, without copying source files. ## Quick Start Resolve the vault path from the OBSIDIAN_VAULT_PATH environment variable, then use this skill to search all markdown notes in the vault for a given keyword.

Frequently Asked Questions about obsidian

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search note contents in an Obsidian vault?

Use the search_files tool with target set to content, a regex pattern, and file_glob set to *.md to restrict matches to markdown notes. This replaces grep or find and returns matching files with line numbers inside the vault.

How do I convert a project directory into an Obsidian knowledge base?

Add a .obsidian/ config enabling graph, backlinks, and search, create an _INDEX.md MOC in each subdirectory, add YAML frontmatter with array-format tags, and symlink external source files like PDFs and TeX instead of copying them.

Why do file operations fail with $OBSIDIAN_VAULT_PATH in the path?

File tools do not expand shell variables, so paths containing $OBSIDIAN_VAULT_PATH fail. Resolve the variable via terminal first, or fall back to ~/Documents/Obsidian Vault, then pass the concrete absolute path.

Should I use shell commands or file tools for Obsidian notes?

Prefer native file tools: read_file, write_file, patch, and search_files over cat, echo, grep, find, or ls. Vault paths often contain spaces, and file tools avoid shell quoting and escaping problems while returning structured results.

When should I use patch versus write_file to edit a note?

Use patch for anchored appends or targeted edits when the note has stable context, such as adding a section after an existing heading. Use write_file only when rewriting the entire note is clearer than constructing a fragile patch.