Skill v1.0.0
currentAutomated scan100/100version: "1.0.0" name: obsidian-save description: Write into the user's Obsidian vault — create a note or append to one. Use when the user asks to save, note down, or remember something in Obsidian or "the vault", and at the end of research, a decision, or a handoff worth keeping. Requires Execution on Local Computer.
Writing to the Obsidian vault
The vault is a folder of Markdown files on the user's own computer, not in your box. Reach it with a command on the local computer.
The one rule
Never create, edit, or move vault files yourself — no cat >, no editor, no mv, no rm. Every write goes through vault.py. It owns filenames, frontmatter, collisions, and access scope, so notes from every bot stay consistent and the user can trust what lands in the vault.
VAULT="${GROK_OBSIDIAN_HOME:-$HOME/.grok-obsidian}/scripts/vault.py"
If that file is missing, or a command reports that no vault is configured, stop and use the obsidian-setup skill first.
Before you create — look
A vault fills up with near-duplicates fast. Search first (see the obsidian-lookup skill); if a note on this subject exists, append to it instead of creating a second one.
Create a note
python3 "$VAULT" save \--bot "Research Bot" \--title "Telegram channel research" \--tags "research,telegram" \--source "https://example.com/article" \--content "Conclusion first, then the evidence."
Long or multi-line bodies are easier to pipe:
printf '%s' "$BODY" | python3 "$VAULT" save --bot "..." --title "..."
Append to a note
python3 "$VAULT" append \--bot "Research Bot" \--path "Grok Bot/research-bot/2026-08-30-telegram-channel-research.md" \--heading "Second pass" \--content "New finding and its source."
Every command prints JSON with the path it wrote. Report that path to the user — they navigate by it.
Arguments
| Flag | Command | Notes | |
|---|---|---|---|
--bot | all | Your own name. It scopes what you may touch — pass your real name | |
--title | save | Short and descriptive; it becomes the filename | |
--content | save, append | Or pipe the body on stdin | |
--path | append | Vault-relative path, as returned by save or search | |
--tags | save | Comma-separated | |
--source | save | URL, file, or chat the content came from | |
--heading | append | Section heading; defaults to a timestamp | |
--force | save | Overwrite a same-day note with the same title | |
--dry-run | save, append | Show the path without writing |
What to write
- Lead with the conclusion, then the evidence. Notes are read months later.
- One note, one subject. Two subjects means two calls.
- Keep the source. An unsourced claim is worth much less in a vault.
- Numbers need evidence next to them. Never write a metric you did not measure
or read from a named source.
- Write in the language the user used with you.
What not to write
- Secrets, tokens, API keys, passwords — never, even when asked to "save this
config". Say you skipped them and why.
- Raw chat logs, unless the user asked for a transcript.
- Anything unverified, unless it is labelled as unverified.
Where notes land
<vault>/Grok Bot/<your-name>/YYYY-MM-DD-<title>.md
Each bot writes into its own folder and, by default, can read only that folder. The user widens this deliberately.
When it fails
generic bot name— you passed a placeholder name like "New Bot". Ask the
user which folder to write into and pass it as --folder.
no vault configured/vault not found— use theobsidian-setupskill.
Do not guess a path and do not write elsewhere.
outside the allowed folders— you are reaching beyond your scope. Ask the
user to add the folder to GROK_OBSIDIAN_FOLDERS rather than working around it.
- Command refused or no local computer — local execution is off. Tell the user
to enable Settings → General → Agent → Execution on Local Computer. Do not save in your box and call it saved.