Obsidian CLI Bases and Bookmarks
Use this skill for Obsidian Bases and Bookmarks operations through official desktop obsidian CLI commands.
Routing contract
Use this skill when:
- the user asks to inspect or query
.base files
- the user asks to list base views or query base results in structured formats
- the user asks to create an item through a base view
- the user asks to list or add bookmarks
Do not use this skill when:
- the user wants to author or revise the
.base definition (use Bases Authoring)
- the request is primarily note CRUD, tasks, templates, link cleanup, or history/diff workflows
- the request is plugin/theme/snippet runtime administration
- the request is Sync/Publish operations
- the request is explicitly a named one-command workflow ID (route to
obsidian-cli-workflows)
- the request is runtime diagnostics/eval/CDP workflows
Preconditions
Assume these must be true before relying on this skill:
obsidian command is installed and registered
- Obsidian desktop app is available locally
- first command may launch Obsidian if it is not running
- in Codex Desktop on macOS, direct launches may crash; use the sanitized wrapper
Codex-safe launcher
In Codex Desktop on macOS, prefer this wrapper:
script -q /dev/null "${CODEX_OBSIDIAN_ZSH_PATH:-/usr/local/bin/zsh}" -ilc 'unset __CFBundleIdentifier LaunchInstanceID XPC_SERVICE_NAME CODEX_CI CODEX_SANDBOX CODEX_SHELL; export TERM=xterm-256color; obsidian ...'
Set CODEX_OBSIDIAN_ZSH_PATH to override the default /usr/local/bin/zsh path. The override must be an absolute path to a Zsh-compatible executable.
Escalate the wrapped command only when required by sandbox boundaries.
Core operating policy
- Use only documented official Bases and Bookmarks CLI commands.
- Prefer read-only discovery first for mixed flows:
bases, base:views, base:query, bookmarks.
- Use structured output (
json, csv, tsv, md, paths) whenever supported and useful.
- Treat
base:create as a mutating operation and summarize created-file side effects before executing.
- Use
base:views only after resolving the active base. Probe installed help before passing any target option. Use exact path= and view= with base:query for pinned result checks.
- For
bookmark, require explicit target type (file, folder, search, or url) and avoid silent assumptions.
- If base file/path, view name, or bookmark target is ambiguous, stop and ask for disambiguation.
- Keep scope narrow to requested base/bookmark workflow; do not drift into unrelated note-wide edits.
- If request is outside official Bases/Bookmarks surface, say so and stop.
Risk levels
- low:
bases, base:views, base:query, bookmarks
- medium:
bookmark
- high:
base:create
Response contract
Always return:
- capability used
- risk level (
low, medium, high)
- execution mode (
direct or escalated)
- exact command(s) run or proposed
- output format used (if structured)
- side-effect summary (for mutating actions)
- files/bookmarks affected, if any
- blocking reason, if any
Command families
Bases:
bases
base:views
base:query
base:create
Bookmarks:
References
references/obsidian-cli-bases-bookmarks-playbook.md
references/limitations-and-boundaries.md
references/validation.md
references/source-links.md
1---2name: obsidian-cli-bases-and-bookmarks3description: Use this skill when the user needs official desktop Obsidian CLI Bases or Bookmarks workflows, including base discovery, view/query operations, base item creation, and bookmark management. Keep this skill separate from general note CRUD, runtime admin, Sync/Publish, and devtools diagnostics.4metadata:5 source: https://skillmd.com/skills/hashgraph-online/obsidian-cli-bases-and-bookmarks6---78# Obsidian CLI Bases and Bookmarks910Use this skill for Obsidian Bases and Bookmarks operations through official desktop `obsidian` CLI commands.1112## Routing contract1314Use this skill when:15- the user asks to inspect or query `.base` files16- the user asks to list base views or query base results in structured formats17- the user asks to create an item through a base view18- the user asks to list or add bookmarks1920Do not use this skill when:21- the user wants to author or revise the `.base` definition (use [Bases Authoring](../obsidian-bases-authoring/SKILL.md))22- the request is primarily note CRUD, tasks, templates, link cleanup, or history/diff workflows23- the request is plugin/theme/snippet runtime administration24- the request is Sync/Publish operations25- the request is explicitly a named one-command workflow ID (route to `obsidian-cli-workflows`)26- the request is runtime diagnostics/eval/CDP workflows2728## Preconditions2930Assume these must be true before relying on this skill:31- `obsidian` command is installed and registered32- Obsidian desktop app is available locally33- first command may launch Obsidian if it is not running34- in Codex Desktop on macOS, direct launches may crash; use the sanitized wrapper3536## Codex-safe launcher3738In Codex Desktop on macOS, prefer this wrapper:3940```bash41script -q /dev/null "${CODEX_OBSIDIAN_ZSH_PATH:-/usr/local/bin/zsh}" -ilc 'unset __CFBundleIdentifier LaunchInstanceID XPC_SERVICE_NAME CODEX_CI CODEX_SANDBOX CODEX_SHELL; export TERM=xterm-256color; obsidian ...'42```4344Set `CODEX_OBSIDIAN_ZSH_PATH` to override the default `/usr/local/bin/zsh` path. The override must be an absolute path to a Zsh-compatible executable.4546Escalate the wrapped command only when required by sandbox boundaries.4748## Core operating policy49501. Use only documented official Bases and Bookmarks CLI commands.512. Prefer read-only discovery first for mixed flows: `bases`, `base:views`, `base:query`, `bookmarks`.523. Use structured output (`json`, `csv`, `tsv`, `md`, `paths`) whenever supported and useful.534. Treat `base:create` as a mutating operation and summarize created-file side effects before executing.545. Use `base:views` only after resolving the active base. Probe installed help before passing any target option. Use exact `path=` and `view=` with `base:query` for pinned result checks.556. For `bookmark`, require explicit target type (`file`, `folder`, `search`, or `url`) and avoid silent assumptions.567. If base file/path, view name, or bookmark target is ambiguous, stop and ask for disambiguation.578. Keep scope narrow to requested base/bookmark workflow; do not drift into unrelated note-wide edits.589. If request is outside official Bases/Bookmarks surface, say so and stop.5960## Risk levels6162- low: `bases`, `base:views`, `base:query`, `bookmarks`63- medium: `bookmark`64- high: `base:create`6566## Response contract6768Always return:69- capability used70- risk level (`low`, `medium`, `high`)71- execution mode (`direct` or `escalated`)72- exact command(s) run or proposed73- output format used (if structured)74- side-effect summary (for mutating actions)75- files/bookmarks affected, if any76- blocking reason, if any7778## Command families7980Bases:81- `bases`82- `base:views`83- `base:query`84- `base:create`8586Bookmarks:87- `bookmarks`88- `bookmark`8990## References9192- `references/obsidian-cli-bases-bookmarks-playbook.md`93- `references/limitations-and-boundaries.md`94- `references/validation.md`95- `references/source-links.md`