obsidian-recaplisted

# Obsidian Recap Produce a synthesized, narrative **daily recap** for the current project and persist it to the vault. The Stop hook already writes one session note per session and a link-only daily note; those are raw artifacts. This skill reads those artifacts and turns them into prose a human can skim weeks later. **This is synthesis, not transcription.** The recap explains what was accomplished and why, collapsing many sessions into a coherent story. It is the LLM's job precisely because a hook cannot summarize. Recaps land in `<projects_folder>/<repo>/recaps/<YYYY-MM-DD>.md` (or `Claude/Projects/<repo>/recaps/` if no projects folder is configured) and are linked into that day's daily note automatically. ## Step 1 — Check configuration Read `OBSIDIAN_VAULT_PATH` from the environment: - Bash: `bash -c 'echo $OBSIDIAN_VAULT_PATH'` - PowerShell: `$env:OBSIDIAN_VAULT_PATH` If empty, stop and tell the user: > "OBSIDIAN_VAULT_PATH is not set. Re-run `install.sh` and provide your vault > path when prompted, or add it manually to `~/.claude/settings.json` under > the `env` key." Also read: - `OBSIDIAN_PROJECTS_FOLDER` (empty string if unset) - `CLAUDE_PROJECT_DIR` (or fall back to current working directory) You do not need the REST API variables — `obsidian-writer` owns the transport chain (CLI → REST API → filesystem) and reads them from the environment itself. Never pass the API key to an agent; it would land in the dispatch payload and the transcript. ## Step 2 — Det