read-up-onlisted

Jog the agent's memory on a topic, person, or project that lives somewhere in the user's Obsidian vault (second brain). Works from any directory on the machine. Use when the user says "read up on X", "catch me up on X", "what do I know about X", "remind yourself about X", or otherwise asks for a briefing on a subject they expect to be in their vault but won't say where.
magnusrodseth/dotfiles · ★ 2 · AI & Automation · score 65

Install: claude install-skill magnusrodseth/dotfiles

# Read Up On Build a briefing on a topic by discovering and synthesizing everything the vault already knows about it. The user invokes this when they want full context loaded before continuing; they don't know (or care) which files hold the answer. Can be invoked from ANY project on the machine. ## Configuration Resolve the vault location first, then use `$VAULT` everywhere below: ```bash if [ -d "$HOME/dev/personal/vault" ]; then VAULT="$HOME/dev/personal/vault" # local machine (any cwd) else VAULT="${CLAUDE_PROJECT_DIR:-$PWD}" # cloud session: the repo IS the vault fi ``` The fallback matters in Claude Code cloud/web sessions, where the vault is cloned to a sandbox path and `$HOME/dev/personal/vault` does not exist. On a local machine the first branch always wins, so behaviour there is unchanged. All searches below run against `$VAULT`, regardless of the current working directory. The vault's auto-memory lives at `$HOME/.claude/projects/*-dev-personal-vault/memory/MEMORY.md` (glob it; the project dir name encodes the username, which differs between machines). **This path does not exist in cloud sessions** — if the glob matches nothing, skip the auto-memory step and rely on the notes and git history instead. Do not treat its absence as an error. ## When to use Trigger phrases: "read up on ...", "catch me up on ...", "what do I have on ...", "refresh on ...", "load context on ...". Topics can be: - A **project** (e.g. "REMA 1000 tech lead rol