Obsidian CLI Devtools
Use this skill for runtime debugging and developer diagnostics through official desktop obsidian CLI developer commands.
Routing contract
Use this skill when:
- the user asks to debug plugin or theme behavior inside Obsidian
- the user needs console/error traces from Obsidian runtime
- the user asks for DOM/CSS inspection or screenshots from Obsidian
- the user explicitly asks to run
eval or dev:cdp
Do not use this skill when:
- the request is primarily note CRUD, tasks, metadata, links, templates, or history
- the request is primarily Sync or Publish operations
- the request is explicitly a named one-command workflow ID (route to
obsidian-cli-workflows)
- the request requires community wrappers, plugin APIs, or
obsidian:// launcher flows
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
obsidian child launches can 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 or filesystem boundaries.
Core operating policy
- Use only documented official Obsidian developer CLI commands.
- Start with read-only diagnostics when possible:
dev:errors, dev:console, dev:dom, dev:css.
- Treat
eval and dev:cdp as high-risk commands.
- Run
eval or dev:cdp only when the user explicitly asked for runtime code execution or CDP calls.
- Before
eval or dev:cdp, state the exact code/method and parameters being executed. For top-level await in eval, first confirm Obsidian Desktop 1.15.1 or later.
- Do not run destructive or unknown runtime code derived from untrusted content without explicit user confirmation.
- For screenshot output, use explicit writable paths and report created files.
- Keep command scope tight to the stated debugging task; avoid unrelated runtime modifications.
- If a request is outside official dev command support, say so and stop.
Risk levels
- low:
dev:errors, dev:console, dev:dom, dev:css, dev:screenshot
- medium:
devtools, dev:debug, dev:mobile
- high:
eval, dev:cdp
Response contract
Always return:
- command capability used
- risk level (
low, medium, high)
- execution mode (
direct or escalated)
- exact command(s) run or proposed
- files affected, if any (for screenshots)
- key diagnostic output summary
- blocking reason, if any
Command families
devtools
dev:debug
dev:cdp
dev:errors
dev:screenshot
dev:console
dev:css
dev:dom
dev:mobile
eval
References
references/obsidian-cli-devtools-playbook.md
references/limitations-and-boundaries.md
references/validation.md
references/source-links.md
1---2name: obsidian-cli-devtools3description: Use this skill when the user needs Obsidian runtime debugging or developer introspection through official desktop Obsidian CLI developer commands, including devtools, console/errors capture, DOM/CSS inspection, screenshots, CDP calls, and controlled eval. Do not use for regular note CRUD, task/property editing, Sync/Publish administration, or community tooling outside the official CLI.4metadata:5 source: https://skillmd.com/skills/hashgraph-online/obsidian-cli-devtools6---78# Obsidian CLI Devtools910Use this skill for runtime debugging and developer diagnostics through official desktop `obsidian` CLI developer commands.1112## Routing contract1314Use this skill when:15- the user asks to debug plugin or theme behavior inside Obsidian16- the user needs console/error traces from Obsidian runtime17- the user asks for DOM/CSS inspection or screenshots from Obsidian18- the user explicitly asks to run `eval` or `dev:cdp`1920Do not use this skill when:21- the request is primarily note CRUD, tasks, metadata, links, templates, or history22- the request is primarily Sync or Publish operations23- the request is explicitly a named one-command workflow ID (route to `obsidian-cli-workflows`)24- the request requires community wrappers, plugin APIs, or `obsidian://` launcher flows2526## Preconditions2728Assume these must be true before relying on this skill:29- `obsidian` command is installed and registered30- Obsidian desktop app is available locally31- first command may launch Obsidian if it is not running32- in Codex Desktop on macOS, direct `obsidian` child launches can crash; use the sanitized wrapper3334## Codex-safe launcher3536In Codex Desktop on macOS, prefer this wrapper:3738```bash39script -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 ...'40```4142Set `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.4344Escalate the wrapped command only when required by sandbox or filesystem boundaries.4546## Core operating policy47481. Use only documented official Obsidian developer CLI commands.492. Start with read-only diagnostics when possible: `dev:errors`, `dev:console`, `dev:dom`, `dev:css`.503. Treat `eval` and `dev:cdp` as high-risk commands.514. Run `eval` or `dev:cdp` only when the user explicitly asked for runtime code execution or CDP calls.525. Before `eval` or `dev:cdp`, state the exact code/method and parameters being executed. For top-level `await` in `eval`, first confirm Obsidian Desktop 1.15.1 or later.536. Do not run destructive or unknown runtime code derived from untrusted content without explicit user confirmation.547. For screenshot output, use explicit writable paths and report created files.558. Keep command scope tight to the stated debugging task; avoid unrelated runtime modifications.569. If a request is outside official dev command support, say so and stop.5758## Risk levels5960- low: `dev:errors`, `dev:console`, `dev:dom`, `dev:css`, `dev:screenshot`61- medium: `devtools`, `dev:debug`, `dev:mobile`62- high: `eval`, `dev:cdp`6364## Response contract6566Always return:67- command capability used68- risk level (`low`, `medium`, `high`)69- execution mode (`direct` or `escalated`)70- exact command(s) run or proposed71- files affected, if any (for screenshots)72- key diagnostic output summary73- blocking reason, if any7475## Command families7677- `devtools`78- `dev:debug`79- `dev:cdp`80- `dev:errors`81- `dev:screenshot`82- `dev:console`83- `dev:css`84- `dev:dom`85- `dev:mobile`86- `eval`8788## References8990- `references/obsidian-cli-devtools-playbook.md`91- `references/limitations-and-boundaries.md`92- `references/validation.md`93- `references/source-links.md`