Quick read on the state of a relationship — who they are, last contact, open commitments, unresolved threads, and a specific next action. Reads SENSORY-CORTEX/people/ and cross-references any mentions in HIPPOCAMPUS/decisions/, CEREBELLUM/corrections.md, and MOTOR-CORTEX/. Use before sending an email or message to someone you have not talked with in a while, before a meeting, when a name comes up and you need context, or when deciding whether a relationship needs attention.
Give a honest, compact read on one relationship. The goal is a usable snapshot — enough to write a real message or enter a real conversation without rereading everything. Not a CRM entry; a human picture.
The AI-OS root is at ~/Desktop/AI-OS/ by default. If the user has configured a different root (check the plugin config or a root-level CLAUDE.md marker), use that path instead. People entities live at SENSORY-CORTEX/people/{slug}.md.
Invoke this skill whenever any of the following apply:
Do not invoke for someone actively in the current session's context — that information is already in working memory. Also skip for truly new contacts with no file yet; offer to create one instead.
The caller should provide:
SENSORY-CORTEX/people/ basenames and name/aliases fields in frontmatter.If multiple people match a partial name, list the candidates (name + company + last contact) and ask. If no match, ask whether to create a new person file.
Resolve the file in this order:
SENSORY-CORTEX/people/name field in frontmatteraliases list in frontmatter (if present)If nothing matches, stop and ask. If multiple match, stop and ask.
Read the full file, parsing frontmatter and body. Expected frontmatter fields (flex — not all will be present):
name, aliases, role, company, locationstatus (active / dormant / archived / do-not-contact)relationship (one-line framing, e.g., "prospect", "former colleague", "investor intro")last_contact_at, next_touch_bytags, relatedSearch the rest of the brain for mentions of this person:
HIPPOCAMPUS/decisions/ — any decision whose frontmatter related lists this person's wiki-link, or whose body mentions the name. Note dates.CEREBELLUM/corrections.md — any correction that referenced this person (e.g., "sent too long an email to X" — context worth remembering).MOTOR-CORTEX/*/ — any project whose files mention the person. Projects they're embedded in.HIPPOCAMPUS/short-term/ — recent session files (last 30 days).SENSORY-CORTEX/companies/ — if the person has a company field, load that company's file too. Relationships often sit in the intersection.If no MCP is available, skip and note the gap. Do not fail on missing optional connectors.
From last_contact_at + any cross-reference evidence, compute:
on-rhythm, slipping (past cadence), dormant (past 2x cadence with no explicit reason), fresh (contacted recently), or never (file exists but no contact recorded)If the person's frontmatter status says do-not-contact, surface that immediately before anything else and skip the next-action section.
From the file and cross-references, extract:
Be specific. "Following up on the thing" is not useful. "Owes feedback on the hiring doc since 2026-03-24" is.
Use this structure. Keep it to one screen unless depth is explicitly requested.
# {name} — {status verdict}
## Who
<one-line: role at company, location, relationship framing>
## Freshness
<last contact date + days ago, cadence verdict, next-touch-by if set>
## Recent topics
<2-3 bullets on what was last discussed>
## Open — you owe
<bullets or "none tracked">
## Open — they owe
<bullets or "none tracked">
## Relevant context
<anything surfaced from decisions, projects, companies that colors how to approach this person right now>
## Suggested next action
<one concrete action. Example: "Reply to the 2026-04-02 thread with a short status + new date.">
## Risk flags
<anything that should give pause: "last contact ended on a correction", "status is dormant", "do-not-contact — stop here", or "none">
If purpose was supplied, expand the relevant section:
active, move to dormant, or archive.After the output, if anything surfaced that belongs in MEMORY.md (not in short-term, not in person file) — a permanent fact about the relationship, a durable preference — offer to add it. Do not write without user confirmation.
If the person file does not exist:
SENSORY-CORTEX/people/{slug}.md with the context extracted from mentionsNever fabricate details. If the only evidence is "Ludwig mentioned a Jane in a short-term file once", say that and nothing more.
do-not-contact status. Stop instead.last_contact_at, next_touch_by, or status go through the user.meeting-prep when the purpose is meeting preparation — meeting-prep handles the overall brief, relationship-check handles the person-by-person layer.decision-check when the relationship has open decisions — surface whether any pending decision involves this person.reflect or foresight should promote a re-engage action into next week's priorities.CEREBELLUM/patterns.md via consolidation — do not edit patterns.md here.