Obsidian - read, search, write and edit direct to obsidian vault.

**Judgement:** This skill is a strong choice for users who already maintain an Obsidian vault on the same machine and want an agent to treat it as a first-class knowledge base. It offers robust search and structured editing tailored to Obsidian conventions, making it more reliable than generic file-editing skills for this niche. **Key strengths:** - Obsidian-native model (vault structure, frontmatter, tags, wikilinks) rather than generic markdown handling. - Fast and capable search (ripgrep + fuzzy/phonetic) across titles, tags, and content, suitable for retrieval-augmented answering. - Structured edit operations (append/prepend/replace/replace-section) that map well to typical note-edit workflows. - Support for auto-folder detection and folder suggestions, reducing hard-coded path logic. **Main risks / limitations:** - **Destructive edits:** `replace` and `replace-section` can overwrite content; if the agent hallucinates or misinterprets instructions, valuable notes may be damaged. Agents should be prompted to: (a) read notes before major edits, (b) confirm with the user for large or irreversible changes, and (c) prefer append/prepend for low-risk modifications. - **Privacy/authority scope:** The skill exposes the entire vault to the agent. On sensitive vaults, this is a data-leak risk if the agent is not carefully permissioned or if logs are stored externally. - **Environment assumptions:** Correct function depends on the vault path and `OBSIDIAN_VAULT` being configured properly. Misconfiguration will cause failures or work on an unexpected vault. - **Obsidian-local only:** It operates on a local filesystem vault; it does not manage remote sync, conflicts, or Obsidian plugins. **Recommended scenarios:** - Power users using Obsidian as a personal or team knowledge base, who want an agent to search, cite, and update notes safely. - Workflows where the agent turns chat sessions, research results, or documents into well-organized Obsidian notes with tags and wikilinks. - Incremental note-refinement tasks (summarizing notes, adding conclusions sections, updating project status) where reading-then-editing individual notes is acceptable. **Less ideal scenarios:** - Highly sensitive vaults where any broad programmatic access is unacceptable without strong sandboxing and audit trails. - Situations requiring complex, multi-file refactors or bulk transformations across the vault (the skill can be used, but risk of unintended large-scale changes increases and should be tightly constrained).