Obsidian Cli
Required companion skill for safe Obsidian vault operations: resolving vault paths, searching notes, creating notes, updating YAML properties, appending logs, validating backlinks, and using Obsidian URI/CLI helpers when available. Use whenever an agent needs to operate on an Obsidian vault.
Install
$ agentstack add skill-lionellau-capture-concept-obsidian-cli ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-lionellau-capture-concept-obsidian-cli) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Obsidian CLI
Use this skill for safe operations on a local Obsidian vault. The vault is a filesystem directory containing .obsidian/.
Operating Model
- Resolve the vault path from the user, environment, or calling skill config.
- Verify the path exists and contains
.obsidian/. - Prefer
rgfor search. - Use an available
obsidiancommand or Obsidian URI only when it exists and
the command shape is known.
- Fall back to direct file operations when CLI helpers are unavailable.
- Never edit outside the resolved vault.
Tool Detection
command -v obsidian >/dev/null && echo "OBSIDIAN_COMMAND=true" || echo "OBSIDIAN_COMMAND=false"
command -v rg >/dev/null && echo "RG=true" || echo "RG=false"Search
Preferred:
rg -n --glob '*.md' "query|alias|topic" "$VAULT"Fallback:
find "$VAULT" -name '*.md' -not -path '*/.trash/*'If an obsidian command supports search in the environment, it may be used, but do not assume a universal syntax without testing it first.
Create Notes
Create parent directories as needed and write Markdown files directly. Preserve existing files unless the user asked to update them.
mkdir -p "$VAULT/Concepts/software-engineering"Prefer readable kebab-case filenames:
cache-key-mismatch.mdUpdate Properties
When a deterministic helper exists, use it. Otherwise edit YAML carefully:
- preserve unrelated fields
- preserve user content
- update
updated: - keep
related:as a flat list of existing note slugs
Backlinks
Before adding a backlink, validate the target file exists. When adding a forward link, also add a reverse link if the related note has a clear structure and can be edited safely.
If the reverse edit is risky, skip it and report the reason.
Logs
Append capture operations to capture-log.md or wiki-log.md in the vault root. Use wikilinks for note references.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: lionellau
- Source: lionellau/capture-concept
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.