From research
Use when reading, searching, creating, appending to, or editing notes in a filesystem-first Obsidian vault
How this skill is triggered — by the user, by Claude, or both
Slash command
/research:obsidianThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill for filesystem-first Obsidian vault work: reading notes, listing
Use this skill for filesystem-first Obsidian vault work: reading notes, listing notes, searching note files, creating notes, appending content, targeted edits, and adding wikilinks.
Before using harness-specific tools, identify the active assistant harness. When the active harness matches one metadata-linked reference above, load exactly that one reference and skip the non-matching harness files. Use the shared workflow below for decisions and the harness reference only to translate file, search, shell, and edit operations into the active toolset.
Use a known or resolved vault path before calling file tools.
The vault-path convention is OBSIDIAN_VAULT_PATH. If it is unset, use
~/Documents/Obsidian Vault.
File tools do not expand shell variables. Do not pass paths containing
$OBSIDIAN_VAULT_PATH to file tools; resolve the vault path first and pass a
concrete absolute path. Vault paths may contain spaces, so prefer file tools or
carefully quoted shell commands.
If the vault path is unknown, use a shell command to resolve
OBSIDIAN_VAULT_PATH or check whether the fallback path exists. Once the path
is known, switch back to the harness's preferred file tools.
| Task | Workflow |
|---|---|
| Read a note | Read the resolved absolute path to the note. |
| List notes | Search file names under the resolved vault path. Use *.md for all Markdown notes. |
| Search note contents | Search content under the resolved vault path and restrict to *.md when needed. |
| Create a note | Write the full Markdown content to the resolved absolute path. |
| Append to a note | Read the note, then use an anchored edit when stable context exists. Rewrite the whole note only when that is clearer. |
| Targeted edits | Use focused exact edits based on current content and stable context. |
For a simple append with no stable context, a carefully quoted shell append is acceptable if it is the clearest safe option.
Obsidian links notes with [[Note Name]] syntax. When creating or updating
notes, use wikilinks to connect related content.
npx claudepluginhub alex-kopylov/zweihander --plugin researchGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.