AGENT SKILL

obsidian-cli

Interact with a running Obsidian vault through the obsidian CLI to read, create, append, search, and manage notes, daily notes, tasks, properties, tags, and backlinks. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, or perform vault operations from the command line.

License 许可
MIT
最近更新
2026-09-25
Stars
★ 0
Forks
0

01 前言 Front Matter

name
obsidian-cli
description
Interact with a running Obsidian vault through the obsidian CLI to read, create, append, search, and manage notes, daily notes, tasks, properties, tags, and backlinks. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, or perform vault operations from the command line.
allowed-tools
[ "Bash(obsidian:*)", "Read" ]

03 SKILL.md 正文

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"

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.

Developer surface

The developer surface of the CLI (eval, dev:*, and the CDP and debugger controls) is intentionally omitted from this skill.

04 同仓库更多 Skills

coltonbearden
coltonbearden/awakened

good-skill

Fixture - a skill whose name equals its directory and whose description clears the forty-character floor (N-2).

★ 0
coltonbearden
coltonbearden/awakened

wrong-name

Too short.

★ 0
coltonbearden
coltonbearden/awakened

<skill-name>

<What the skill does, then the situations that should trigger it. Concrete and situational, third person, never marketing. Minimum 40 characters — this text is the auto-invocation surface (N-2).>

★ 0
coltonbearden
coltonbearden/awakened

writing-plans

Turns an agreed design or spec into a step-by-step implementation plan that an engineer with no context could execute. Use when a multi-step change is understood well enough to sequence but no plan exists yet, before touching code. Produces a plan file with exact paths, test-first steps, interfaces between tasks, and no placeholders.

★ 0
coltonbearden
coltonbearden/awakened

verification-before-completion

Gate that runs before any claim that work is done, fixed, passing, or shipped. Identifies the command that would prove the claim, runs it fresh, reads the whole output, and only then reports — with the evidence attached and any gap stated. Use before committing, opening a pull request, marking a task complete, or telling the user something works.

★ 0
coltonbearden
coltonbearden/awakened

using-skills

Session discipline that fires before the first action of any task. Checks whether an installed skill or command already covers the job, keeps every action inside the requested scope, and reports verification as evidence rather than confidence. Use at the start of a conversation, before answering a question, before exploring a codebase, and whenever a task changes shape mid-session.

★ 0