From research-vault
Canonical roster of people the user works with — full names, affiliations, role on which projects, and the short handles the user writes (e.g.
How this skill is triggered — by the user, by Claude, or both
Slash command
/research-vault:vault-peopleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Hot cache of the people the user works with most. The full per-person profiles
Hot cache of the people the user works with most. The full per-person profiles
live under memory/people/<name>.md — see the vault-memory skill for the
tiered lookup pattern.
| Handle | Full name | Affiliation | Role / context |
|---|---|---|---|
(empty — seed via /start) |
If the user writes a bare first name with no further context, prefer the most recently-active collaborator with that name — but always ask before guessing unless the surrounding context makes it unambiguous. Getting the wrong person assigned to a task is worse than a one-line clarification.
#firstname-lastname handle in lowercase-hyphen form.memory/people/<name>.md with role, affiliation, and the project
files they appear in.People also appear in project files under ## People. Those entries are the
project-specific context (what they do on that project); this roster is the
general identity.
npx claudepluginhub gillyspace27/research-vault-plugin --plugin research-vaultCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.