/new-person
Create a relationship tracking file for a person with contact info, history, and communication preferences. Use when user says "new person", "add [name]", "create a file for [name]", "track this person", or mentions someone important who doesn't have a file yet. See also:
$ npx -y skills add kbanc85/claudia --skill new-person --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/new-person
Context preview
The summary Claude sees to decide when to auto-load this skill.
Create a relationship tracking file for a person with contact info, history, and communication preferences. Use when user says "new person", "add [name]", "create a file for [name]", "track this person", or mentions someone important who doesn't have a file yet. See also:
SKILL.md
new-person.SKILL.mdname: new-person
description: Create a relationship tracking file for a person with contact info, history, and communication preferences. Use when user says "new person", "add [name]", "create a file for [name]", "track this person", or mentions someone important who doesn't have a file yet. See also: `relationship-tracker` for ongoing health; `meeting-prep` when you have a call coming up.
argument-hint: "[name]"
effort-level: medium
New Person
Create a new relationship file for tracking someone.
Usage
`/new-person [name]`
Quick Flow
1. Basic Information
"Tell me about [Name]. A few quick things:"
- What's their role?
- How do you know them?
- What's the relationship type? (Client, Colleague, Friend, Prospect, etc.)
2. Optional Details
"Anything else I should capture?"
- Contact info
- What matters to them
- Communication preferences
- Current context
3. Create File
Save to `people/[name-slug].md`
Template
# [Person Name]
**Role:** [Their title/position]
**Organization:** [Company/org]
**How we met:** [Context]
**Relationship type:** [Client, Colleague, Friend, Prospect, etc.]
## Quick Stats
| Field | Value |
|-------|-------|
| Last Contact | [Today's date] |
| Relationship Health | Active |
| Sentiment | Positive / Neutral / Unknown |
## Contact
| Channel | Details |
|---------|---------|
| Email | [If provided] |
| Phone | [If provided] |
| LinkedIn | [If provided] |
| Preferred | [If known] |
## Communication Style
[How they prefer to communicate, if known]
## What Matters to Them
[Their priorities, if known]
## Current Context
*Last updated: [Today]*
[What they're working on, if known]
## Our History
| Date | Event | Notes |
|------|-------|-------|
| [Today] | [Initial context] | Created file |
## Commitments
### I owe them
- [None yet]
### They owe me
- [None yet]
## Notes
[Any other context worth remembering]
---
*Created: [Today's date]*
After Creation
"Created file for [Name] at `people/[name-slug].md`
Want me to:
- Add more details?
- Note any commitments?
- Set a reminder to follow up?"
Name Handling
- Create slug from name: "Sarah Chen" -> "sarah-chen.md"
- Handle duplicates: Add identifier if needed ("sarah-chen-acme.md")
- Non-Latin names: Preserve original, add romanization if provided
Minimal vs. Full
**Minimal** (quick capture):
- Name, role, how you met
- Creates basic file
- Fills in more over time
**Full** (when user has time):
- All template fields
- Contact information
- Communication preferences
- Current context
- History
Ask: "Quick capture or full profile?"
Read more
name: new-person description: Create a relationship tracking file for a person with contact info, history, and communication preferences. Use when user says "new person", "add [name]", "create a file for [name]", "track this person", or mentions someone important who doesn't have a file yet. See also: `relationship-tracker` for ongoing health; `meeting-prep` when you have a call coming up. argument-hint: "[name]" effort-level: medium
New Person
Create a new relationship file for tracking someone.
Usage
`/new-person [name]`
Quick Flow
1. Basic Information
"Tell me about [Name]. A few quick things:"
- What's their role?
- How do you know them?
- What's the relationship type? (Client, Colleague, Friend, Prospect, etc.)
2. Optional Details
"Anything else I should capture?"
- Contact info
- What matters to them
- Communication preferences
- Current context
3. Create File
Save to `people/[name-slug].md`
Template
# [Person Name] **Role:** [Their title/position] **Organization:** [Company/org] **How we met:** [Context] **Relationship type:** [Client, Colleague, Friend, Prospect, etc.] ## Quick Stats | Field | Value | |-------|-------| | Last Contact | [Today's date] | | Relationship Health | Active | | Sentiment | Positive / Neutral / Unknown | ## Contact | Channel | Details | |---------|---------| | Email | [If provided] | | Phone | [If provided] | | LinkedIn | [If provided] | | Preferred | [If known] | ## Communication Style [How they prefer to communicate, if known] ## What Matters to Them [Their priorities, if known] ## Current Context *Last updated: [Today]* [What they're working on, if known] ## Our History | Date | Event | Notes | |------|-------|-------| | [Today] | [Initial context] | Created file | ## Commitments ### I owe them - [None yet] ### They owe me - [None yet] ## Notes [Any other context worth remembering] --- *Created: [Today's date]*
After Creation
"Created file for [Name] at `people/[name-slug].md`
Want me to:
- Add more details?
- Note any commitments?
- Set a reminder to follow up?"
Name Handling
- Create slug from name: "Sarah Chen" -> "sarah-chen.md"
- Handle duplicates: Add identifier if needed ("sarah-chen-acme.md")
- Non-Latin names: Preserve original, add romanization if provided
Minimal vs. Full
**Minimal** (quick capture):
- Name, role, how you met
- Creates basic file
- Fills in more over time
**Full** (when user has time):
- All template fields
- Contact information
- Communication preferences
- Current context
- History
Ask: "Quick capture or full profile?"
Terminal-based AI chief of staff. Remembers relationships, tracks commitments, helps you think strategically. Runs on Claude Code.
Repo: kbanc85/claudia
Other skills on claudia.
- /auto-research
Iteratively improve a local artifact (draft, document, page) by running a hill-climbing loop. The user names the artifact, the evaluator, and the budget. Claudia edits the artifact, scores it, keeps it if better or reverts if worse, repeats. Use when user says "iterate on this",
Open skill - /brain-monitor
Launch the Brain Monitor TUI, a real-time terminal dashboard for watching Claudia's memory system. Triggers on "brain monitor", "show dashboard", "memory dashboard", "terminal brain". See also: `brain` for a 3D graph view in the browser.
Open skill - /brain
Launch the Brain Visualizer, a real-time 3D view of memory and relationships. Triggers on "show your brain", "visualize memory", "open the brain", "memory graph". See also: `brain-monitor` for a terminal dashboard alternative.
Open skill - /build-team
Propose a personalized team of specialized agents based on the user's profile, goals, and how they actually work. Runs the proposal through an independent Checker, gates on the user's approval, and applies with rollback. Use when the user says "build my team", "set up my
Open skill - /capture-meeting
Process meeting notes or transcript to extract decisions, commitments, and insights. Use when user shares transcript or says "capture this meeting", "here are my notes from the call". See also: `meeting-prep` for pre-call briefings; `follow-up-draft` for post-meeting emails.
Open skill - /client-health
Health check across active client engagements showing status, deliverables, and concerns. Triggers on "how are my clients?", "client status", "client health check".
Open skill

