tyler-dot-earth/obsidian-safe-cli SkillScore 57 Maintained Enforce least-privilege Obsidian note operations through obsidian-safe-cli.sh with per-note cli-allowed property gating and a minimal command API for weaker models. Use when working in an Obsidian vault that contains private notes and the user wants agent access only to explicitly authorized notes.
by tyler-dot-earth
Use this skill Links this skill to your agents and keeps it current with the author’s updates.
Automatic
◆ Knowledge Management pack
$ decimalai skills pull tyler-dot-earth-obsidian-safe-cliCopy
Copy link Copy README badge Copy SKILL.md Get this skill — curl · raw file $ curl -fsSL https://app.decimal.ai/s/tyler-dot-earth-obsidian-safe-cli/SKILL.mdCopy
how this skill behaves on real traffic · last 30 days
No production data for this skill yet — usage numbers appear here once agents start running it.
Anonymized aggregate across every org using this skill — proof from real production use, not a demo. Sign in and install to see your own agents here →
· Benchmark: with vs. without sign in to run this on your agents 23 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 6d ago
— +1% tokens 0% turns 57% of whole cases pass with skill (13/23)
Showing 5 of 23 cases See all cases & grading →
SkillSafety ✓ 3 of 3 passed ✓ Code scan 15 of 15 checks clean
0 critical · 0 warning · 0 info — scanner v4 — 8/1/2026
live_secret remote_code_execution reverse_shell data_exfiltration ssrf_metadata agent_snooping anti_refusal destructive_commands obfuscated_unicode unicode_homoglyph opaque_blob suspicious_url tool_overreach trigger_abuse prompt_injection_phrasing
✓ Intent Safe
LLM judge · does the skill do what it claims
✓ Content Clean
LLM judge · policy & harmful-content review
Source Imported tyler-dot-earth / obsidian-safe-cli
skills/obsidian-safe-cli/SKILL.md
View on GitHub ↗ Imported 8/1/2026Version v1Bundled 1 file · scripts
Contents Benchmark Live Traces Versions (1) Ratings (0)
Obsidian safe cli Use this skill to operate on Obsidian notes only through obsidian-safe-cli.sh on PATH.
required rules Never use raw obsidian commands when obsidian-safe-cli.sh can do the operation. Never read a note unless obsidian-safe-cli.sh read <path> allows it. Never use direct filesystem writes; always use obsidian-safe-cli.sh create or obsidian-safe-cli.sh append. Never use delete, move, rename, plugin install, or restore operations. Treat cli-allowed as the source of truth for read authorization. Keep an auditable trail by preserving obsidian-safe-cli-audit.log. Keep command usage simple; this API is intentionally small for weaker models. command map Discover allowed notes: obsidian-safe-cli.sh search "<query>" Retrieve context snippets from allowed notes: obsidian-safe-cli.sh search-context "<query>" List all 'agent inbox' notes: obsidian-safe-cli.sh agent-inbox-list Read one allowed note: obsidian-safe-cli.sh read [--json] "<path>" Create a new inbox note: obsidian-safe-cli.sh create "<note-name>" "<content>" Append to an existing inbox note: obsidian-safe-cli.sh append "<note-name>" "<content>" execution flow Start with obsidian-safe-cli.sh agent-inbox-list, obsidian-safe-cli.sh search, or obsidian-safe-cli.sh search-context. Read only files returned by allowed search using obsidian-safe-cli.sh read. Command output is wrapped with op:start and op:ok lines; use --json when structured output is easier.
Use obsidian-safe-cli.sh create for first-write and obsidian-safe-cli.sh append for follow-up writes. Let the script route note writes into the configured inbox automatically. If read is denied, stop and ask the user for explicit human authorization. failure handling If obsidian-safe-cli.sh read returns access denied, do not attempt alternate read paths. If obsidian-safe-cli.sh command is missing, ask the user to ensure obsidian-safe-cli.sh is available on PATH and continue with the same guardrails. If Obsidian CLI is unavailable, report the blocker and do not fall back to direct filesystem reads for protected notes. If create fails because note exists, choose a new note name and retry create. If append fails because note is missing, switch to create. examples User asks: "Find notes about project alpha I have approved." Action: obsidian-safe-cli.sh search "project alpha" User asks: "Summarize this note I approved." Action: obsidian-safe-cli.sh read "<approved-path>", then summarize, then optionally create "summary". Want to see if tyler-dot-earth/obsidian-safe-cli would activate on your phrasing? Try it before you install — no LLM call, no signup. Try this skill →