obsidian-person
The `/obsidian-person` command creates or updates a person note in an Obsidian vault by extracting information from the current conversation. It searches for existing matching notes (handling typos and partial names), then either updates the found note or creates a new structured note in the People folder with full metadata including role, company, relationship strength, and interaction date. The command also logs the interaction in the daily note and updates any People index file present in the vault.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/eugeniughelbur/obsidian-second-brain/HEAD/commands/obsidian-person.md -o ~/.claude/commands/obsidian-person.mdobsidian-person.md
Use the obsidian-second-brain skill. Execute `/obsidian-person $ARGUMENTS`: The argument is a person's name - handle typos and partial matches. 1. Read `_CLAUDE.md` first if it exists in the vault root 2. Search the vault for an existing note matching the name (fuzzy - handle typos and partial names) 3. If found: confirm with user, then update with new info from conversation 4. If not found: create `Full Name.md` in the entities folder (resolved per `references/folder-map.md` - wiki-style `wiki/entities/`, Obsidian-style `People/`) with full frontmatter schema 5. Fill in everything inferable from the conversation: role, company, context, relationship strength, last interaction date 6. Log the interaction in today's daily note 7. If a People index file exists, add or update the entry there If the name has a typo or is approximate, search the vault, show what was found, and confirm before proceeding. Never silently create a note with a misspelled name. --- **AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future agent` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. The vault is for future agent retrieval - not human reading. **Anti-fabrication:** Search exhaustively before claiming any note, person, or file is absent - false absence is the most common failure mode - and never invent facts, entities, or dates (mark unknowns as `TBD`). See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.
>
Create a new obsidian-second-brain command via interview - zero markdown editing required
Surface 3-5 next-direction candidates by reading ungraduated ideas, open project questions, and orphan research notes - what is worth working on next
Vault-first source-grounded research via Gemini File Search. One command, no browser. The grounded parallel to /research-deep (which is open-web via Perplexity).
Generate a decision record when the vault structure changes - the vault knows why it knows what it does
Read Google Calendar and write an AI-first snapshot to the vault - today, week, next week, or a custom range
Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions. Re-run to refresh without clobbering your edits
Show or update a kanban board - flags overdue items, updates from conversation