obsidian-cli-uri-fallback
Use when Obsidian note automation runs in cron/headless environments and obsidian-cli emits URI failure signatures (for example, `Failed to execute Obsidian URI`) that may not set a non-zero exit code. Detect false-success cases, fallback to deterministic markdown file writes, and record traceable fallback paths in run artifacts.
How do I install this agent skill?
npx skills add https://github.com/akillness/jeo-skills --skill obsidian-cli-uri-fallbackIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill implements a robust fallback mechanism for Obsidian CLI automation, ensuring note persistence even when the primary desktop URI execution fails. It identifies specific error signatures and uses standard file writing to save data directly to the vault.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
obsidian-cli-uri-fallback
Use this skill when Obsidian CLI calls are part of unattended runs and you need reliable note persistence even if URI execution fails silently.
When to use this skill
- Cron jobs or CI-like runs that attempt
obsidian-cli create/open/.... - Desktop app availability is uncertain (headless, remote, or locked session).
- CLI output includes explicit failure signatures while exit code is still zero.
- You need a deterministic fallback path to preserve audit notes.
Instructions
- Run the intended
obsidian-clicommand first. - Treat either non-zero exit or known failure-signature text as failure.
- Minimum signature list:
Failed to execute Obsidian URICannot find note in vault
- Minimum signature list:
- On failure, write the note directly to markdown path (
<vault>/.../*.md) using deterministic naming. - Record fallback status in run artifacts:
- attempted command
- observed signature
- fallback file path
- Continue the workflow without retry loops unless user explicitly requested retries.
Examples
obsidian-cli create "queries/hourly-2026-04-27.md" -c "..."printsFailed to execute Obsidian URIwith exit code 0.- classify as failure
- fallback: write
queries/hourly-2026-04-27.mddirectly - record fallback path in survey/PR artifacts
Best practices
- Prefer ASCII-only automation payloads in unattended shells.
- Keep fallback filenames stable and timestamped.
- Never claim Obsidian CLI success when failure-signature text is present.
- Keep fallback evidence alongside run artifacts for reviewer traceability.
References
.agent-skills/obsidian-cli/SKILL.md.agent-skills/survey/references/keyword-sweep-and-relevance-rescue.md
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/akillness/jeo-skills/obsidian-cli-uri-fallback">View obsidian-cli-uri-fallback on skillZs</a>