url/Obsidian-CLI-skill
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Broaden skill description to trigger on vault intent, not just CLI mentions

Browse Source 
The skill should activate whenever the user wants Claude to interact with
their Obsidian vault — not only when they explicitly mention the CLI or
terminal. Casual phrases like "add to my daily note" or "search my vault"
are now explicit triggers.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
pablo-mano
2026-03-04 00:18:28 +01:00
parent c7b35b314d
commit de356e8396
1 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/obsidian-cli/SKILL.md
+11 -11
View File
@@ -1,17 +1,17 @@
--- ---
name: obsidian-cli name: obsidian-cli
description: > description: >
Use this skill for any workflow where the user controls Obsidian from a terminal Use this skill whenever the user wants Claude to interact with their Obsidian vault
or script — not the GUI. Concrete triggers: running the `obsidian` binary and its — reading notes, creating or appending content, searching, managing tasks, tags,
subcommands (daily:append, eval, tasks, orphans, search, property:set, etc.); properties, daily notes, bookmarks, templates, sync, plugins, or links. The
writing bash or Python scripts that automate vault operations; scheduling Obsidian underlying mechanism is the official Obsidian CLI (v1.12+), but trigger even when
tasks via cron or systemd timers; debugging IPC socket errors or headless Linux the user doesn't mention the CLI — phrases like "add this to my daily note", "search
setups; evaluating JavaScript against the Obsidian API from a shell; or building my vault", "create a note from template", or "what tasks do I have open?" all apply.
programmatic wrappers around the CLI. The single clearest signal: the user is Also trigger for explicit CLI usage: running `obsidian` subcommands from a shell,
invoking or wants to invoke the `obsidian` command from a terminal rather than scripting or automating vault operations, scheduling via cron, debugging IPC/headless
clicking through the app. Skip for GUI-only questions, installing plugins or themes Linux setups, or building programmatic wrappers. Skip only for pure GUI questions
through the Obsidian interface, iCloud/sync configuration, or processing markdown (Obsidian settings navigation, theme/plugin installation via UI) or iCloud sync
files with tools that have no connection to the `obsidian` binary. configuration that has nothing to do with vault content.
--- ---
# Obsidian CLI # Obsidian CLI