notelisted

# Save a session note to Obsidian Resolve the vault, then write to `<vault>/Sessions/<YYYY-MM-DD>-<slug>.md`. ```bash VAULT="$(<skill-dir>/vault.sh)" || exit 1 # honors $OBSIDIAN_VAULT, else reads obsidian.json DATE="$(date +%F)" mkdir -p "$VAULT/Sessions" ``` `<skill-dir>` is the base directory printed when this skill loads — by default `~/.claude/skills/note`. If `vault.sh` fails it tells the user how to fix it; don't guess a path, and don't fall back to writing somewhere else. - Take the date from `date +%F`. Never guess it. - `<slug>`: 3–6 lowercase hyphenated words naming the *topic* (`obsidian-agent-notes`, not `session-summary`). If an argument was passed to the skill, it is the topic to focus on — narrow the note to that thread rather than covering the whole session. - If the target file already exists, append a `## <HH:MM> — <sub-topic>` section instead of overwriting. - Everything else in the vault is the user's own writing. Don't edit those files. ## What the note is for Two readers: the user six months from now, and an agent that has to pick the thread up cold. So record **what was concluded and why**, not a transcript of what happened. Decisions, the reasoning behind them, dead ends and why they were dead, the exact commands / paths / version pins that mattered. Cut the narration. Write in the language of the conversation, and keep the user's own terminology. Suggested shape. Drop any section that would be empty; don't pad to fill it out. ```ma