obsidian

Use search_files with target set to content, a content regex as the pattern, and file_glob set to *.md to restrict matches to markdown notes. This is preferred over grep or find because it returns structured results.

Use write_file with the resolved absolute vault path and the full markdown content. This avoids shell quoting issues from heredocs or echo and returns structured results, which matters because vault paths often contain spaces.

File tools do not expand shell variables, so passing $OBSIDIAN_VAULT_PATH directly to read_file or write_file fails. Resolve the variable first via the terminal or use the fallback path ~/Documents/Obsidian Vault, then pass a concrete absolute path.

Read the note with read_file, then use patch for an anchored append when stable context exists, such as adding a section after a known heading. For appends with no stable anchor, a terminal command is acceptable as the clearest safe option.

Yes, the skill declares support for linux, macos, and windows platforms. All operations use cross-platform file tools rather than platform-specific shell commands, so the workflow is consistent across operating systems.