Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lord1egypt/obsidian
Read, search, create, and edit notes in the Obsidian vault.
Passed 8 of 15 test cases with the skill, and 5 of 15 without it.
and 2 more in the full report
5 fixed6 passed either way10 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to read a note called 'Meeting Notes.md' in my vault, but my environment variables are not set. What path should you check first?
| Checked | Without skill | With skill |
|---|---|---|
| Uses ~/Documents/Obsidian Vault as default path when environment variable is unset | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill for filesystem-first Obsidian vault work: reading notes, listing notes, searching note files, creating notes, appending content, and adding wikilinks.
Use a known or resolved vault path before calling file tools.
The documented vault-path convention is the OBSIDIAN_VAULT_PATH environment variable, for example from ~/.hermes/.env. If it is unset, use ~/Documents/Obsidian Vault.
File tools do not expand shell variables. Do not pass paths containing $OBSIDIAN_VAULT_PATH to read_file, write_file, patch, or search_files; resolve the vault path first and pass a concrete absolute path. Vault paths may contain spaces, which is another reason to prefer file tools over shell commands.
If the vault path is unknown, terminal is acceptable for resolving OBSIDIAN_VAULT_PATH or checking whether the fallback path exists. Once the path is known, switch back to file tools.
Use read_file with the resolved absolute path to the note. Prefer this over cat because it provides line numbers and pagination.
Use search_files with target: "files" and the resolved vault path. Prefer this over find or ls.
pattern: "*.md" under the vault path.Use search_files for both filename and content searches. Prefer this over grep, find, or ls.
search_files with target: "files" and a filename pattern.search_files with target: "content", the content regex as pattern, and file_glob: "*.md" when you want to restrict matches to markdown notes.Use write_file with the resolved absolute path and the full markdown content. Prefer this over shell heredocs or echo because it avoids shell quoting issues and returns structured results.
Prefer a native file-tool workflow when it is not awkward:
test cases passed, vs 5 / 15 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.