How do I install the Obsidian CLI Bases And Bookmarks skill?

Run npx skillmds@latest add concertonotes/obsidian-cli-bases-and-bookmarks in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Obsidian CLI Bases And Bookmarks safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Obsidian CLI Bases And Bookmarks?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Obsidian CLI Bases And Bookmarks free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Obsidian CLI Bases And Bookmarks?

ConcertoNotes (@concertonotes) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Obsidian CLI Bases And Bookmarks by concertonotes

Name: Obsidian CLI Bases And Bookmarks
Rating: 4.2 (5 reviews)
Author: ConcertoNotes

Obsidian CLI Bases And Bookmarks

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.

ConcertoNotes Updated Sep 8, 2026 0 repo stars

File contents

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 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 /usr/local/bin/zsh -ilc 'unset __CFBundleIdentifier LaunchInstanceID XPC_SERVICE_NAME CODEX_CI CODEX_SANDBOX CODEX_SHELL; export TERM=xterm-256color; obsidian ...'

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.
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:

bookmarks
bookmark

References

references/obsidian-cli-bases-bookmarks-playbook.md
references/limitations-and-boundaries.md
references/validation.md
references/source-links.md

---name: obsidian-cli-bases-and-bookmarksdescription: 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.---# Obsidian CLI Bases and BookmarksUse this skill for Obsidian Bases and Bookmarks operations through official desktop `obsidian` CLI commands.## Routing contractUse 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 bookmarksDo not use this skill when:- 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## PreconditionsAssume 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 launcherIn Codex Desktop on macOS, prefer this wrapper:```bashscript -q /dev/null /usr/local/bin/zsh -ilc 'unset __CFBundleIdentifier LaunchInstanceID XPC_SERVICE_NAME CODEX_CI CODEX_SANDBOX CODEX_SHELL; export TERM=xterm-256color; obsidian ...'```Escalate the wrapped command only when required by sandbox boundaries.## Core operating policy1. Use only documented official Bases and Bookmarks CLI commands.2. Prefer read-only discovery first for mixed flows: `bases`, `base:views`, `base:query`, `bookmarks`.3. Use structured output (`json`, `csv`, `tsv`, `md`, `paths`) whenever supported and useful.4. Treat `base:create` as a mutating operation and summarize created-file side effects before executing.5. For `bookmark`, require explicit target type (`file`, `folder`, `search`, or `url`) and avoid silent assumptions.6. If base file/path, view name, or bookmark target is ambiguous, stop and ask for disambiguation.7. Keep scope narrow to requested base/bookmark workflow; do not drift into unrelated note-wide edits.8. 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 contractAlways 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 familiesBases:- `bases`- `base:views`- `base:query`- `base:create`Bookmarks:- `bookmarks`- `bookmark`## References- `references/obsidian-cli-bases-bookmarks-playbook.md`- `references/limitations-and-boundaries.md`- `references/validation.md`- `references/source-links.md`

Frequently asked questions