Individual skill
prismer-obsidian
Read, search, create, and edit notes in the Obsidian vault.
sdk/cloud/catalog/skills/prismer-obsidian/SKILL.md
Source commit f83b859a173802a73d978197e92328ab2bf57a6e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,364
- Repository last updated
- Oct 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-communication Repository topic
- agent-memory Repository topic
- ai-agents Repository topic
- claude Repository topic
- cursor Repository topic
- docker Repository topic
- knowledge-base Repository topic
- llm-tools Repository topic
- mcp Repository topic
- mcp-server Repository topic
- productivity Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
LICENSEasset · 1,070 bytesLICENSE.hermesasset · 1,070 bytesPROVENANCE.mddoc · 659 bytesSKILL.mdcore · 4,473 bytesprovenance/category-DESCRIPTION.mddoc · 146 bytesscripts/write_note.pyruns · 3,662 bytes
Read excerpt
# Obsidian Vault
Use this skill for filesystem-first Obsidian vault work: reading notes, listing notes, searching note files, creating notes, appending content, and adding wikilinks.
## Vault path
Use a known or resolved vault path before calling file tools.
Require an explicitly configured OBSIDIAN_VAULT_PATH or a vault path supplied by the user. If absent, report missing configuration; do not create or write to a fallback 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 validating the user-supplied path. Once the path is known, switch back to file tools.
