agentleFS
sonichisonichi/sutando/skills/obsidian-vault/SKILL.md

obsidian-vault

Skill396 starsChanged 6 months agoMITView on GitHub

Voice-inline capture into a Sutando-owned Obsidian vault. The voice agent calls add_to_vault(kind, body, title?) directly — no core round-trip, no Obsidian plugin required. Filesystem-direct: Obsidian's watcher picks up the change instantly when the vault is open. Lives at <workspace>/obsidian-vault/ (<workspace> resolved via bash scripts/sutando-config.sh workspace — per sutando.config.local.json, defaulting to <repo>/workspace/; $SUTANDO_WORKSPACE no longer honored as of v0.8 / #1440). Auto-created on first capture, with a .obsidian/ marker dir so Obsidian recognizes the folder as a vault. Everything Sutando writes…

  • Reads credentials

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ubiquitous-language, batch-grill-me and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • kennethkeimSkill

    ubiquitous-language

    Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

    Also in 32 projects that use this

  • boyingliu01Skill

    batch-grill-me

    A relentless interview that asks every frontier question at once, round by round. Thin alias of `grilling` (#540) — upstream mattpocock/skills absorbed this protocol into grilling; XP-Gate keeps this name as the sprint-flow Phase 2 entry point so orchestration docs stay stable.

    Also in 6 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 26 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 25 projects that use this

  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 4 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 16 projects that use this

  • +1 more from Lesani

The file

Files
SKILL.md

obsidian-vault

Voice-inline capture into a Sutando-owned Obsidian vault. The voice agent calls add_to_vault(kind, body, title?) directly — no core round-trip, no Obsidian plugin required. Filesystem-direct: Obsidian's watcher picks up the change instantly when the vault is open.

Vault

Lives at <workspace>/obsidian-vault/ (<workspace> resolved via bash scripts/sutando-config.sh workspace — per sutando.config.local.json, defaulting to <repo>/workspace/; $SUTANDO_WORKSPACE no longer honored as of v0.8 / #1440). Auto-created on first capture, with a .obsidian/ marker dir so Obsidian recognizes the folder as a vault.

Layout

Everything Sutando writes lives under the Sutando/ subfolder, by kind:

<workspace>/obsidian-vault/
  .obsidian/                                 ← marker; Obsidian populates on first open
  Sutando/
    Notes/<slug>-<YYYY-MM-DDTHHMMSS>.md      kind="note"   → standalone file w/ frontmatter
    Tasks.md                                 kind="task"   → appended checkbox
    Thoughts/<YYYY-MM-DD>.md                 kind="thought" → appended timestamped block

This subfolder convention keeps Sutando's writes out of the way of anything else you put in the vault later.

Triggers (what the voice agent listens for)

  • "save this as a note" / "note that X" → kind="note"
  • "add to my tasks" / "todo: X" / "remind me to X" → kind="task"
  • "remember this thought" / "log this idea" → kind="thought"
  • Ambiguous capture intents → the tool description picks thought for stream-of-consciousness, task for action-shaped, note otherwise.

One-time setup in Obsidian

Open Obsidian → File → Open vault → Open folder as vault → pick <workspace>/obsidian-vault. Obsidian will remember it. The vault appears empty until you trigger your first capture.

Opt-in: agent-state mirror + nightly dream

add_to_vault (the voice-inline capture tool) is always available — it only writes when you explicitly say "save this as a note" / "todo: ..." / "thought: ...".

Two automatic features are opt-in via env var and OFF by default:

  • src/obsidian-mirror.py — one-shot CLI that sweeps tasks/ + results/ + notes/ + pending-questions.md into Sutando/Agent/. No background process; runs once and exits. Schedule it yourself via crons.json at whatever cadence you want.
  • Nightly dream.py cron — Opus-4.7-judged cross-linking (inline (cf. [[X]]) citations + tiered ## Strongly Related / ## Related / ## See also footer block). Sweeps the mirror first, then judges.

Both are gated by SUTANDO_OBSIDIAN_MIRROR. To enable, add to .env:

SUTANDO_OBSIDIAN_MIRROR=1

Then either:

  • One-shot now: python3 src/obsidian-mirror.py (single sweep + exit).
  • Or add an obsidian-dream entry to your per-host crons.json to run on a cadence (it is not included in the default template). The nightly job sweeps + judges in one go.

CLI flags worth knowing:

  • python3 src/obsidian-mirror.py --force — bypass the env gate (used by run_dream voice tool).
  • python3 src/obsidian-mirror.py --since 1h — only sync sources modified in the last hour (faster sweep for frequent crons).

The on-demand voice tool run_dream bypasses the gate — explicit user invocation always wins.

What's not in this skill (yet)

  • Search / weekly roundup / multi-file edits — those are the "core" half of this integration. Plan: add scripts/search.py, scripts/daily-roundup.py driven via work() so heavier ops don't block the voice turn.
  • Obsidian Local REST API — community plugin that exposes HTTP endpoints. We don't use it. Filesystem-direct is simpler and has no plugin dependency. Could be a future opt-in for read-side flows.

Loader

Loaded by src/inline-tools.ts:loadSkillManifestTools() at voice-agent startup. To pick up changes: restart voice-agent and reconnect the web client (Gemini caches the tool list at session start).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.