Menü
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Guide for implementing new agent tools for ClosedClaw's AI assistant. Use when adding capabilities like web search, file operations, API integrations, or custom actions. Covers tool factory pattern, parameter validation, registration, and testing.
Guide for creating new messaging channel plugins/extensions for ClosedClaw. Use when adding support for new messaging platforms (e.g., Matrix, Teams, BlueBubbles). Covers plugin structure, CliDeps extension, routing setup, and testing.
Run Codex CLI, Claude Code, OpenCode, or Pi Coding Agent via background process for programmatic control.
Help with config schema changes and migrations in ClosedClaw. Use when updating config types, syncing Zod schemas, creating migrations, or handling breaking config changes. Covers type definitions, validation, and legacy migration patterns.
Guide for writing and maintaining ClosedClaw documentation. Use when creating docs for new features, channels, tools, or updating existing documentation. Covers markdown conventions, link styles, formatting rules, and documentation structure.
Guide for writing e2e tests for ClosedClaw gateway and channels. Use when testing multi-instance gateway behavior, WebSocket/HTTP surfaces, node pairing, agent workflows with real networking. Covers test helpers, assertion patterns, and common scenarios.
| name | obsidian |
| description | Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli. |
| homepage | https://help.obsidian.md |
| metadata | {"ClosedClaw":{"emoji":"💎","requires":{"bins":["obsidian-cli"]},"install":[{"id":"brew","kind":"brew","formula":"yakitrak/yakitrak/obsidian-cli","bins":["obsidian-cli"],"label":"Install obsidian-cli (brew)"}]}} |
Obsidian vault = a normal folder on disk.
Vault structure (typical)
*.md (plain text Markdown; edit with any editor).obsidian/ (workspace + plugin settings; usually don’t touch from scripts)*.canvas (JSON)Obsidian desktop tracks vaults here (source of truth):
~/Library/Application Support/obsidian/obsidian.jsonobsidian-cli resolves vaults from that file; vault name is typically the folder name (path suffix).
Fast “what vault is active / where are the notes?”
obsidian-cli print-default --path-only~/Library/Application Support/obsidian/obsidian.json and use the vault entry with "open": true.Notes
~/Documents, work/personal, etc.). Don’t guess; read config.print-default.Pick a default vault (once):
obsidian-cli set-default "<vault-folder-name>"obsidian-cli print-default / obsidian-cli print-default --path-onlySearch
obsidian-cli search "query" (note names)obsidian-cli search-content "query" (inside notes; shows snippets + lines)Create
obsidian-cli create "Folder/New note" --content "..." --openobsidian://…) working (Obsidian installed)..something/...) via URI; Obsidian may refuse.Move/rename (safe refactor)
obsidian-cli move "old/path/note" "new/path/note"[[wikilinks]] and common Markdown links across the vault (this is the main win vs mv).Delete
obsidian-cli delete "path/note"Prefer direct edits when appropriate: open the .md file and change it; Obsidian will pick it up.