Current description: Interact with Obsidian vaults using the official Obsidian CLI (v1.12+). Read, create, append, search, and manage notes, daily notes, properties, tags, tasks, bookmarks, templates, themes, sync, plugins, and links — all from the terminal. Use this skill whenever the user mentions Obsidian CLI, wants to automate Obsidian vault operations, manage notes programmatically, script daily note workflows, query vault metadata, or integrate Obsidian with AI agents or automation pipelines. Also trigger when the user asks about controlling Obsidian from the command line, building scripts around their knowledge base, or running headless Obsidian setups. Even if the user just says "add something to my daily note" or "search my vault" in a CLI/scripting context, this skill applies.
+
+
+
+
+
+
+
+
+
+
Query
+
Should Trigger
+
Actions
+
+
+
+
+
+
+
+
+
+
diff --git a/eval/eval_set.json b/eval/eval_set.json
new file mode 100644
index 0000000..c99eb4d
--- /dev/null
+++ b/eval/eval_set.json
@@ -0,0 +1,82 @@
+[
+ {
+ "query": "hey i need to automatically append meeting notes to today's daily note in obsidian from a bash script that runs after each zoom call ends",
+ "should_trigger": true
+ },
+ {
+ "query": "obsidian daily:append keeps failing on my headless ubuntu server, keeps showing 'IPC socket not found' — i'm running it as a systemd service",
+ "should_trigger": true
+ },
+ {
+ "query": "how do i search my obsidian vault for all notes tagged #project/alpha using the cli and pipe the results into another script?",
+ "should_trigger": true
+ },
+ {
+ "query": "i want to write a shell script that creates a new note in obsidian from a template and then sets the status property to 'in-progress' — what's the syntax for property:set?",
+ "should_trigger": true
+ },
+ {
+ "query": "my obsidian eval command works fine but i need to run multiline javascript against app.vault — the single-line approach isn't enough for what i'm trying to do",
+ "should_trigger": true
+ },
+ {
+ "query": "setting up a cron job to run obsidian tasks every morning and email me the incomplete ones — not sure what flags I need or what the output format looks like",
+ "should_trigger": true
+ },
+ {
+ "query": "i'm building a python wrapper around the obsidian cli to batch-update frontmatter across ~200 notes in my vault. how does property:set handle list-type fields?",
+ "should_trigger": true
+ },
+ {
+ "query": "trying to use the obsidian cli on my mac but the obsidian binary isn't in my PATH even though i enabled CLI in settings and restarted",
+ "should_trigger": true
+ },
+ {
+ "query": "need to move about 50 notes from Projects/ to Archive/ in my obsidian vault without touching the GUI — is there a bulk-move option?",
+ "should_trigger": true
+ },
+ {
+ "query": "can the obsidian cli get me a list of all orphan notes (no incoming links) as JSON? i want to feed that list into a cleanup script",
+ "should_trigger": true
+ },
+ {
+ "query": "how do i install the Dataview community plugin in obsidian? i've never installed a plugin before and don't know where to find it in the settings panel",
+ "should_trigger": false
+ },
+ {
+ "query": "writing a python script to bulk-rename markdown files in ~/notes — they all need a YYYY-MM-DD date prefix added to the filename based on their creation date",
+ "should_trigger": false
+ },
+ {
+ "query": "i use Logseq for my daily notes and journaling, is there any CLI tool similar to what obsidian has that lets me append to today's journal from the terminal?",
+ "should_trigger": false
+ },
+ {
+ "query": "setting up a brand new obsidian vault for my zettelkasten — what folder structure and naming convention do you recommend for atomic notes?",
+ "should_trigger": false
+ },
+ {
+ "query": "i want to use the obsidian web clipper extension to save full articles to my vault from chrome. how do i configure the template it uses?",
+ "should_trigger": false
+ },
+ {
+ "query": "building an obsidian plugin in TypeScript that hooks into the editor and adds a custom right-click context menu for formatting commands",
+ "should_trigger": false
+ },
+ {
+ "query": "i need to read and update YAML frontmatter across a directory of markdown files using Python — something like python-frontmatter or ruamel.yaml",
+ "should_trigger": false
+ },
+ {
+ "query": "how do i sync my obsidian vault to iCloud on mac? should i put it inside Documents or in a dedicated iCloud Drive folder to avoid conflicts?",
+ "should_trigger": false
+ },
+ {
+ "query": "i want to export some obsidian notes to PDF to share with colleagues who don't use obsidian — what's the best way to do a batch export?",
+ "should_trigger": false
+ },
+ {
+ "query": "implementing full-text search over a folder of markdown files in a node.js app — what's a lightweight library or algorithm for this? something like lunr or flexsearch?",
+ "should_trigger": false
+ }
+]
\ No newline at end of file
diff --git a/skills/obsidian-cli/SKILL.md b/skills/obsidian-cli/SKILL.md
index 7de2f38..e527def 100644
--- a/skills/obsidian-cli/SKILL.md
+++ b/skills/obsidian-cli/SKILL.md
@@ -1,16 +1,17 @@
---
name: obsidian-cli
description: >
- Interact with Obsidian vaults using the official Obsidian CLI (v1.12+).
- Read, create, append, search, and manage notes, daily notes, properties, tags,
- tasks, bookmarks, templates, themes, sync, plugins, and links — all from the terminal.
- Use this skill whenever the user mentions Obsidian CLI, wants to automate Obsidian
- vault operations, manage notes programmatically, script daily note workflows,
- query vault metadata, or integrate Obsidian with AI agents or automation pipelines.
- Also trigger when the user asks about controlling Obsidian from the command line,
- building scripts around their knowledge base, or running headless Obsidian setups.
- Even if the user just says "add something to my daily note" or "search my vault"
- in a CLI/scripting context, this skill applies.
+ Use this skill for any workflow where the user controls Obsidian from a terminal
+ or script — not the GUI. Concrete triggers: running the `obsidian` binary and its
+ subcommands (daily:append, eval, tasks, orphans, search, property:set, etc.);
+ writing bash or Python scripts that automate vault operations; scheduling Obsidian
+ tasks via cron or systemd timers; debugging IPC socket errors or headless Linux
+ setups; evaluating JavaScript against the Obsidian API from a shell; or building
+ programmatic wrappers around the CLI. The single clearest signal: the user is
+ invoking or wants to invoke the `obsidian` command from a terminal rather than
+ clicking through the app. Skip for GUI-only questions, installing plugins or themes
+ through the Obsidian interface, iCloud/sync configuration, or processing markdown
+ files with tools that have no connection to the `obsidian` binary.
---
# Obsidian CLI