obsidian-cli
Manage Obsidian Vaults with CLI Commands
Obsidian users need fast note operations without manual navigation. This skill uses the Obsidian CLI to read, update, search, and debug vaults.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "obsidian-cli" from https://skillstore.io/skills/kepano-obsidian-cli.md and its manifest at https://skillstore.io/api/skills/kepano-obsidian-cli/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "obsidian-cli". Read my note named Project Plan.
Expected outcome:
The skill returns a concise summary of sections, tasks, and open questions from that note.
Using "obsidian-cli". Add 'Schedule launch review' to today's daily note.
Expected outcome:
The skill appends an unchecked task and reports the vault and note it changed.
Using "obsidian-cli". Check my plugin for errors after a rebuild.
Expected outcome:
The skill reloads the plugin, checks Obsidian errors, and summarizes console or visual issues.
Security Audit
High RiskMost Ruby backtick alerts are Markdown formatting, but several examples intentionally invoke the Obsidian CLI. Main concerns are vault mutation, sensitive developer output, and app-context JavaScript evaluation; no prompt injection text was found.
Confirmed security concerns (3)
Capability review items (13)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (31)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/kepano-obsidian-cli/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/kepano-obsidian-cli?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/kepano-obsidian-cli?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/kepano-obsidian-cli/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/kepano-obsidian-cli.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
kepano. (2026). obsidian-cli security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/kepano-obsidian-cli/audits/4BibTeX citation
@techreport{kepano-kepano-obsidian-cli-2026,
author = {kepano},
title = {obsidian-cli security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/kepano-obsidian-cli/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "obsidian-cli security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "kepano"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/kepano-obsidian-cli/audits/4"
identifiers:
- type: other
value: "skillstore:kepano-obsidian-cli:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review research notes
Summarize active notes, find related notes, and add backlinks while preserving the vault structure.
Maintain daily work logs
Append tasks, update daily notes, search open items, and keep note properties current.
Debug Obsidian plugins
Reload plugins, inspect errors, capture screenshots, and review DOM or console output.
Try These Prompts
Read the active Obsidian note and summarize the main sections, tasks, and open questions.
Append this task to today's daily note: [task]. Confirm the target vault and note before changing anything.
Search my vault for [topic], list the strongest matches, and suggest where a backlink should be added.
Reload plugin [id], check errors and console output, inspect [selector], and report findings before editing code.
Best Practices
- Confirm the target vault and file before running read or write commands.
- Use explicit file or path parameters when the active note is unclear.
- Ask before using eval, screenshots, DOM inspection, clipboard output, or write commands.
Avoid
- Do not run commands against an unspecified vault when multiple vaults are open.
- Do not expose sensitive note content through broad searches, screenshots, or clipboard output.
- Do not use JavaScript evaluation for routine note edits.