# Manage Obsidian Vaults with CLI Commands

Obsidian users need fast note operations without manual navigation. This skill uses the Obsidian CLI to read, update, search, and debug vaults.

## Install

```bash
npx skillstore add kepano/obsidian-cli
```

## Metadata

- Status: approved
- Slug: kepano-obsidian-cli
- Skillstore revision: r1
- Version status: missing
- Tree hash: 81ed417fe9e6105633cb95d338c64d539da352a99130cb65bc0ee83cdb2d5a22
- Author: kepano
- GitHub username: kepano
- License: MIT
- Repository: https://github.com/kepano/obsidian-skills/tree/main/skills/obsidian-cli
- Ref: a25199bc7d6b82598536822d1738eb5d5f54025b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/kepano-obsidian-cli
- Manifest: https://skillstore.pages.dev/api/skills/kepano-obsidian-cli/manifest

## Capabilities

- Read active notes or named files through the Obsidian CLI.
- Create notes, append content, update daily notes, and set note properties.
- Search vault content, list tasks, sort tags, and review backlinks.
- Target specific vaults and files with vault, file, or path parameters.
- Reload plugins and inspect errors, console output, screenshots, DOM, and CSS.
- Run Obsidian developer commands, including app-context JavaScript evaluation.

## Use Cases

- Review research notes: Summarize active notes, find related notes, and add backlinks while preserving the vault structure.
- Maintain daily work logs: Append tasks, update daily notes, search open items, and keep note properties current.
- Debug Obsidian plugins: Reload plugins, inspect errors, capture screenshots, and review DOM or console output.

## Prompt Templates

### Read Current Note

```
Read the active Obsidian note and summarize the main sections, tasks, and open questions.
```

### Add Daily Task

```
Append this task to today's daily note: [task]. Confirm the target vault and note before changing anything.
```

### Search Related Notes

```
Search my vault for [topic], list the strongest matches, and suggest where a backlink should be added.
```

### Debug Plugin State

```
Reload plugin [id], check errors and console output, inspect [selector], and report findings before editing code.
```

## Limitations

- Obsidian must be open, and the Obsidian CLI must be installed.
- Commands act on the focused vault unless a vault name is supplied.
- Write commands can change local notes and should be reviewed first.
- Developer commands depend on Obsidian version, plugins, and enabled debugging support.

## Best Practices

- Confirm the target vault and file before running read or write commands.
- Use explicit file or path parameters when the active note is unclear.
- Ask before using eval, screenshots, DOM inspection, clipboard output, or write commands.

## Anti Patterns

- Do not run commands against an unspecified vault when multiple vaults are open.
- Do not expose sensitive note content through broad searches, screenshots, or clipboard output.
- Do not use JavaScript evaluation for routine note edits.

## Security Audit

- Audited at: 2026-07-05T18:00:53.665\+00:00
- Summary: Most Ruby backtick alerts are Markdown formatting, but several examples intentionally invoke the Obsidian CLI. Main concerns are vault mutation, sensitive developer output, and app-context JavaScript evaluation; no prompt injection text was found.

## Stats

- Views: 162
- Downloads: 11
- Favorites: 0
- Popularity score: 0