القائمة
Interact with Obsidian vaults using the Obsidian CLI to search, read, write, and organize notes. Use this skill when you need to perform programmatic operations on any Obsidian vault, such as searching for context, managing notes, or updating metadata via the CLI.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
This skill should be used when the user asks to "devenv", "devenv.nix", "languages.*", "services.*", "git-hooks", "devenv shell", "devenv up", "devenv build", or works with devenv development environments. Provides comprehensive devenv configuration patterns.
Use jrnl as a persistent memory store to remember user information, preferences, project context, and facts across conversations. This skill should trigger whenever: the user shares personal information, preferences, or project details that would be useful to remember later; when you need to recall prior context about the user, their setup, or their work; when the user asks "do you remember..." or similar recall questions; when the user mentions storing, saving, or noting something for later; when discussing projects, tools, or workflows where knowing the user's history would improve your assistance. Always query relevant memories before answering questions about the user's projects, preferences, setup, or past conversations — even if you think you remember, the journal may have more current information.
Apply Rust-inspired safety patterns to TypeScript code. Use this skill whenever writing or reviewing TypeScript — especially when adding types, handling errors, validating external data (APIs, file input, user input), designing state machines, or refactoring legacy code with loose booleans or try/catch. It covers four patterns: discriminated unions (eliminate impossible states), Result types (explicit failures), schema-based parsing at boundaries (parse don't validate), and explicit mutability. If the user is working with TypeScript and mentions any of these concepts, or if their code shows patterns like boolean overloads, untyped throw, or unchecked external data, apply this skill.
Expert in Zustand state management for React. Covers store creation, TypeScript integration, middleware (persist, immer), selector patterns, and best practices for avoiding unnecessary re-renders.
Check domain name availability for any TLD using nix-shell whois. Use this whenever the user asks to check if a domain is available, find available domain names, brainstorm domain names for a project, or validate domain name ideas. Triggers on phrases like "is X taken", "check domain", "find available domains", "domain name ideas", "is .com available", etc.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
| name | obsidian-cli |
| description | Interact with Obsidian vaults using the Obsidian CLI to search, read, write, and organize notes. Use this skill when you need to perform programmatic operations on any Obsidian vault, such as searching for context, managing notes, or updating metadata via the CLI. |
This skill provides instructions for using the Obsidian CLI to interact with Obsidian vaults. The CLI requires the Obsidian app to be running.
Important: obsidian in PATH typically launches the GUI app. Use the CLI binary directly:
obsidian-cli
If the path is not found (e.g., after a NixOS rebuild), you can find the current path with:
readlink -f ~/.nix-profile/bin/obsidian | xargs dirname | xargs -I{} ls {}/obsidian-cli
If Obsidian is not running, the CLI will print an error — you may need to launch the app first.
# Search the vault
obsidian-cli vault=<vault-name> search query="query text"
obsidian-cli vault=<vault-name> search:context query="query text" format=json
# Read a note by name (resolves like wikilinks, no path needed)
obsidian-cli vault=<vault-name> read file=<filename>
# Read a note by exact path
obsidian-cli vault=<vault-name> read path="Folder/File.md"
# Read a specific property from a note
obsidian-cli vault=<vault-name> property:read name=<property-name> file=<filename>
# List all tags
obsidian-cli vault=<vault-name> tags counts format=json
# Get backlinks to a note
obsidian-cli vault=<vault-name> backlinks file=<filename> format=json
# Create a note with content (use \n for newlines)
obsidian-cli vault=<vault-name> create path="Folder/File.md" content="Content here..."
# Append to an existing note
obsidian-cli vault=<vault-name> append file=<filename> content="\nNew content"
# Prepend after frontmatter
obsidian-cli vault=<vault-name> prepend file=<filename> content="Prepended content"
# Set a property (updates frontmatter)
obsidian-cli vault=<vault-name> property:set name=<property-name> value="value" file=<filename>
# List incomplete tasks from a note
obsidian-cli vault=<vault-name> tasks file=<filename> todo
# Mark a task as done
obsidian-cli vault=<vault-name> task file=<filename> line=<line-number> done
# List all files in a folder
obsidian-cli vault=<vault-name> files folder="Folder/Subfolder"
# Get headings/outline of a note
obsidian-cli vault=<vault-name> outline file=<filename> format=json
# Check unresolved links (broken references)
obsidian-cli vault=<vault-name> unresolved
format=json when piping output to other commands or when you need structured data.file= parameter resolves like wikilinks — you can reference a note without the path or extension.path= to ensure it is placed in the correct directory.[[Note Name]]) to create connections that can be discovered via backlinks.