claude/skills/obsidian/SKILL.md
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
npx skillsauth add kendreaditya/.config obsidianInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Obsidian vault = a normal folder on disk.
Vault structure (typical)
*.md (plain text Markdown; edit with any editor).obsidian/ (workspace + plugin settings; usually don’t touch from scripts)*.canvas (JSON)Obsidian desktop tracks vaults here (source of truth):
~/Library/Application Support/obsidian/obsidian.jsonobsidian-cli resolves vaults from that file; vault name is typically the folder name (path suffix).
Fast “what vault is active / where are the notes?”
obsidian-cli print-default --path-only~/Library/Application Support/obsidian/obsidian.json and use the vault entry with "open": true.Notes
~/Documents, work/personal, etc.). Don’t guess; read config.print-default.Pick a default vault (once):
obsidian-cli set-default "<vault-folder-name>"obsidian-cli print-default / obsidian-cli print-default --path-onlySearch
obsidian-cli search "query" (note names)obsidian-cli search-content "query" (inside notes; shows snippets + lines)Create
obsidian-cli create "Folder/New note" --content "..." --openobsidian://…) working (Obsidian installed)..something/...) via URI; Obsidian may refuse.Move/rename (safe refactor)
obsidian-cli move "old/path/note" "new/path/note"[[wikilinks]] and common Markdown links across the vault (this is the main win vs mv).Delete
obsidian-cli delete "path/note"Prefer direct edits when appropriate: open the .md file and change it; Obsidian will pick it up.
testing
Reviews test coverage and suggests missing test cases for error paths, edge cases, and business logic. Activates when users write tests or implement new features.
development
Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.
tools
Comprehensive security scanning and vulnerability detection. Includes input validation, path traversal prevention, CVE detection, and secure coding pattern enforcement. Use when: authentication implementation, authorization logic, payment processing, user data handling, API endpoint creation, file upload handling, database queries, external API integration. Skip when: read-only operations on public data, internal development tooling, static documentation, styling changes.
development
Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.