obsidian
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- obsidian
- version
- 1.0.0
- homepage
- https://help.obsidian.md
- metadata
- { "clawdbot": { "emoji": "💎", "install": [ { "id": "brew", "bins": [ "obsidian-cli" ], "kind": "brew", "label": "Install obsidian-cli (brew)", "formula": "yakitrak/yakitrak/obsidian-cli" } ], "requires": { "bins": [ "obsidian-cli" ] } } }
- description
- Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
- description_en
- Manage and automate Obsidian vaults
- description_zh
- Obsidian 知识库管理与自动化
03 SKILL.md 正文
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.jsonand 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.
obsidian-cli quick start
Pick a default vault (once):
obsidian-cli set-default "<vault-folder-name>"obsidian-cli print-default/obsidian-cli print-default --path-only
Search
obsidian-cli search "query"(note names)obsidian-cli search-content "query"(inside notes; shows snippets + lines)
Create
obsidian-cli create "Folder/New note" --content "..." --open- Requires Obsidian URI handler (
obsidian://…) working (Obsidian installed). - Avoid creating notes under “hidden” dot-folders (e.g.
.something/...) via URI; Obsidian may refuse.
Move/rename (safe refactor)
obsidian-cli move "old/path/note" "new/path/note"- Updates
[[wikilinks]]and common Markdown links across the vault (this is the main win vsmv).
Delete
obsidian-cli delete "path/note"
Prefer direct edits when appropriate: open the .md file and change it; Obsidian will pick it up.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.