Labsco
firecrawl logo

obsidian

✓ Official★ 3

by firecrawl · part of firecrawl/openclaw

Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.

🔥🔥🔥✓ VerifiedFreeQuick setup
#automation#scraping#git
🧰 Not standalone. This skill ships with firecrawl/openclaw and only works together with that tool — install the tool first, then add this skill.

Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.

by firecrawl

Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli. npx skills add https://github.com/firecrawl/openclaw --skill obsidian Download ZIPGitHub3

Obsidian

Obsidian vault = a normal folder on disk.

Vault structure (typical)

  • Notes: *.md (plain text Markdown; edit with any editor)

  • Config: .obsidian/ (workspace + plugin settings; usually don’t touch from scripts)

  • Canvases: *.canvas (JSON)

  • Attachments: whatever folder you chose in Obsidian settings (images/PDFs/etc.)

Find the active vault(s)

Obsidian desktop tracks vaults here (source of truth):

  • ~/Library/Application Support/obsidian/obsidian.json

obsidian-cli resolves vaults from that file; vault name is typically the folder name (path suffix).

Fast “what vault is active / where are the notes?”

  • If you’ve already set a default: obsidian-cli print-default --path-only

  • Otherwise, read ~/Library/Application Support/obsidian/obsidian.json and use the vault entry with "open": true.

Notes

  • Multiple vaults common (iCloud vs ~/Documents, work/personal, etc.). Don’t guess; read config.

  • Avoid writing hardcoded vault paths into scripts; prefer reading the config or using print-default.