people

Resolve names, handles, and aliases against private local people indexes.

5|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/cbusillo/codex-skills --skill people-cbusillo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: people
Source: https://github.com/cbusillo/codex-skills/tree/main/skills/people
Command: npx skills add https://github.com/cbusillo/codex-skills --skill people-cbusillo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, and includes scripts (resource) and references (resource) components.

What problem does it solve? Agents often encounter names, GitHub handles, nicknames, or misspellings without knowing who they refer to, which leads to wrong-person routing, stale mentions, and leaked private contact data. This Skill resolves those references against private local identity indexes while keeping personal data out of public artifacts. ## Core Features & Use Cases - Identity Resolution: Match names, aliases, GitHub handles, emails, and known misspellings against a global user index plus a repo-local overlay, returning matched, ambiguous, not_found, or no_index statuses. - Scoped Index Writes: Create or update person entries with the writer helper, defaulting to global/user storage so durable identity context follows the agent across repositories. - Privacy Guardrails: Surface only task-relevant fields, omit notes from ambiguous results, and keep contact details, trust hints, and profile files out of public GitHub content. - Use Case: Before assigning a reviewer in a planning workflow, resolve "Burnett" to the correct person id and GitHub handle, then use only the verified handle for the mention. ## Quick Start Ask the agent to resolve a collaborator by name or handle, for example: resolve who "example-user" is using the people skill before assigning the review.

Frequently Asked Questions about people

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve a GitHub handle to a person locally?

Run the resolve_person.py script with the handle as the query, with or without the leading @. It checks the global user index and repo-local overlay, returning a matched status with the person's id, display name, and contact fields when exactly one entry matches.

How do I add a person to the local people index?

Use people_index.py with the upsert subcommand, providing --id and --display-name plus optional aliases, GitHub username, roles, and organization fields. Writes default to global/user storage under CODE_HOME; pass --scope repo only for project-specific entries.

What happens when no people index is configured?

The resolver returns a no_index status and the workflow continues normally without identity enrichment. Missing people data is explicitly not treated as a failure, so the skill stays optional for hosts and repositories without local config.

Can fuzzy matching be used for assigning reviewers?

No. Fuzzy matching is lookup-only and must be explicitly requested with --fuzzy. Write actions such as assigning, mentioning, or routing require a matched status with id, contact, name, or compact confidence; ambiguous or fuzzy results need manual clarification first.

Where is private people data stored and is it committed?

Durable entries live in $CODE_HOME/skills/.local/people.yaml with repo overlays in .local/people.yaml, both gitignored. Only the public-safe example schema is tracked; real names, handles, and contact details must never be committed or published.