Claude Skill

obsidian-cli

Drive a running Obsidian instance via the `obsidian` CLI — search vault, open/create/move notes, toggle tasks, edit properties, reload plugins, run JS, capture errors/screenshots. Trigger when the user says "search my vault", "open this note in Obsidian", "list notes tagged X", "

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download allemaar-open-skills-skills_obsidian-cli-acf5f79.zip · 2 KB

Install

skills CLI npx skills add https://github.com/allemaar/open-skills/tree/main/skills/obsidian-cli
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install allemaar-open-skills@llmmart
Git git clone https://github.com/allemaar/open-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole allemaar/open-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Obsidian CLI

Use the obsidian CLI to interact with a running Obsidian instance. Requires Obsidian to be open.

Command reference

Run obsidian help to see all available commands. This is always up to date. Full docs: https://help.obsidian.md/cli

Syntax

Parameters take a value with =. Quote values with spaces:

obsidian create name="My Note" content="Hello world"

Flags are boolean switches with no value:

obsidian create name="My Note" silent overwrite

For multiline content use \n for newline and \t for tab.

File targeting

Many commands accept file or path to target a file. Without either, the active file is used.

  • file=<name> — resolves like a wikilink (name only, no path or extension needed)
  • path=<path> — exact path from vault root, e.g. folder/note.md

Vault targeting

Commands target the most recently focused vault by default. Use vault=<name> as the first parameter to target a specific vault:

obsidian vault="My Vault" search query="test"

For mutations, resolve and bind the intended vault identity and exact vault-relative path before acting; inspect current content and recheck that target immediately before the command. Pass explicit vault/path parameters supported by live help, rather than relying on changing focus or an ambiguous basename. An explicit active-note request may use the resolved active note after identity verification. Read back the affected artifact and report the actual delta. Read-only browsing may retain focus defaults; reuse existing action authorization without another blanket confirmation.

Common patterns

obsidian read file="My Note"
obsidian create name="New Note" content="# Hello" template="Template" silent
obsidian append file="My Note" content="New line"
obsidian search query="search term" limit=10
obsidian daily:read
obsidian daily:append content="- [ ] New task"
obsidian property:set name="status" value="done" file="My Note"
obsidian tasks daily todo
obsidian tags sort=count counts
obsidian backlinks file="My Note"

Use --copy on any command to copy output to clipboard. Use silent to prevent files from opening. Use total on list commands to get a count.

Plugin development

Develop/test cycle

After making code changes to a plugin or theme, follow this workflow:

  1. Reload the plugin to pick up changes:
    obsidian plugin:reload id=my-plugin
    
  2. Check for errors — if errors appear, fix and repeat from step 1:
    obsidian dev:errors
    
  3. Verify visually with a screenshot or DOM inspection:
    obsidian dev:screenshot path=screenshot.png
    obsidian dev:dom selector=".workspace-leaf" text
    
  4. Check console output for warnings or unexpected logs:
    obsidian dev:console level=error
    

Additional developer commands

Run JavaScript in the app context:

obsidian eval code="app.vault.getFiles().length"

Inspect CSS values:

obsidian dev:css selector=".workspace-leaf" prop=background-color

Toggle mobile emulation:

obsidian dev:mobile on

Run obsidian help to see additional developer commands including CDP and debugger controls.

Files (open-skills)
  • SKILL.md 4.4 KB
    ---
    name: obsidian-cli
    description: Drive a running Obsidian instance via the `obsidian` CLI — search vault, open/create/move notes, toggle tasks, edit properties, reload plugins, run JS, capture errors/screenshots. Trigger when the user says "search my vault", "open this note in Obsidian", "list notes tagged X", "reload my plugin", "run this in Obsidian", "screenshot the active note", or any command-line vault operation. Use this (not obsidian-markdown) whenever the action requires a live Obsidian session; use obsidian-markdown for raw .md file edits on disk.
    visibility: public
    triggers:
      - "search my vault"
      - "open this note in Obsidian"
      - "list notes tagged X"
      - "reload my plugin"
      - "run this in Obsidian"
      - "screenshot the active note"
    next-skills:
      - skill: obsidian-markdown
        phrase: "/obsidian-markdown"
        why: "After opening/creating a note via the live session, write its body in valid Obsidian-flavored markdown"
      - skill: obsidian-bases
        phrase: "/obsidian-bases"
        why: "Build a .base database view over the notes you just searched or tagged in the vault"
      - skill: json-canvas
        phrase: "/json-canvas"
        why: "Lay the opened notes onto a .canvas as connected nodes"
    ---
    
    # Obsidian CLI
    
    Use the `obsidian` CLI to interact with a running Obsidian instance. Requires Obsidian to be open.
    
    ## Command reference
    
    Run `obsidian help` to see all available commands. This is always up to date. Full docs: https://help.obsidian.md/cli
    
    ## Syntax
    
    **Parameters** take a value with `=`. Quote values with spaces:
    
    ```bash
    obsidian create name="My Note" content="Hello world"
    ```
    
    **Flags** are boolean switches with no value:
    
    ```bash
    obsidian create name="My Note" silent overwrite
    ```
    
    For multiline content use `\n` for newline and `\t` for tab.
    
    ## File targeting
    
    Many commands accept `file` or `path` to target a file. Without either, the active file is used.
    
    - `file=<name>` — resolves like a wikilink (name only, no path or extension needed)
    - `path=<path>` — exact path from vault root, e.g. `folder/note.md`
    
    ## Vault targeting
    
    Commands target the most recently focused vault by default. Use `vault=<name>` as the first parameter to target a specific vault:
    
    ```bash
    obsidian vault="My Vault" search query="test"
    ```
    
    For mutations, resolve and bind the intended vault identity and exact vault-relative path before acting; inspect current content and recheck that target immediately before the command. Pass explicit vault/path parameters supported by live help, rather than relying on changing focus or an ambiguous basename. An explicit active-note request may use the resolved active note after identity verification. Read back the affected artifact and report the actual delta. Read-only browsing may retain focus defaults; reuse existing action authorization without another blanket confirmation.
    
    ## Common patterns
    
    ```bash
    obsidian read file="My Note"
    obsidian create name="New Note" content="# Hello" template="Template" silent
    obsidian append file="My Note" content="New line"
    obsidian search query="search term" limit=10
    obsidian daily:read
    obsidian daily:append content="- [ ] New task"
    obsidian property:set name="status" value="done" file="My Note"
    obsidian tasks daily todo
    obsidian tags sort=count counts
    obsidian backlinks file="My Note"
    ```
    
    Use `--copy` on any command to copy output to clipboard. Use `silent` to prevent files from opening. Use `total` on list commands to get a count.
    
    ## Plugin development
    
    ### Develop/test cycle
    
    After making code changes to a plugin or theme, follow this workflow:
    
    1. **Reload** the plugin to pick up changes:
       ```bash
       obsidian plugin:reload id=my-plugin
       ```
    2. **Check for errors** — if errors appear, fix and repeat from step 1:
       ```bash
       obsidian dev:errors
       ```
    3. **Verify visually** with a screenshot or DOM inspection:
       ```bash
       obsidian dev:screenshot path=screenshot.png
       obsidian dev:dom selector=".workspace-leaf" text
       ```
    4. **Check console output** for warnings or unexpected logs:
       ```bash
       obsidian dev:console level=error
       ```
    
    ### Additional developer commands
    
    Run JavaScript in the app context:
    
    ```bash
    obsidian eval code="app.vault.getFiles().length"
    ```
    
    Inspect CSS values:
    
    ```bash
    obsidian dev:css selector=".workspace-leaf" prop=background-color
    ```
    
    Toggle mobile emulation:
    
    ```bash
    obsidian dev:mobile on
    ```
    
    Run `obsidian help` to see additional developer commands including CDP and debugger controls.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.