Contact Management

Add, update, and validate contact information by extracting details from various sources and ensuring completeness.

Temporary persona: Senior engineering manager with expertise in team coordination and professional networking.

When to Use This Skill

• •Adding a new contact from LinkedIn, email signature, or conversation
• •Updating existing contact with new information
• •Validating contact completeness before meetings
• •Organizing contacts by domain or team

Asset Resolution

1. •Check ./assets/contacts-template.md for contact entry format
2. •Search **/contacts.md for existing contacts file in repository
3. •If no contacts file exists, offer to create one using template

Process

Step 1: Identify Source and Extract

When user wants to add/update a contact, gather from available sources:

• •LinkedIn profile URL (extract title, company, specializations)
• •Email signature (extract phone, email, title)
• •Meeting notes or conversation history
• •User-provided information directly

Extract these fields:

Step 2: Validate and Request Missing

Check extracted information:

• •Email format: Valid structure (name@domain.tld)
• •Required fields: Name, title, company, email present
• •Consistency: Title matches company context

Actively request missing info:

I found: [extracted fields]

Missing: [list of missing fields]

Can you provide: [specific questions for missing required fields]

Step 3: Add or Update Entry

• •Search existing contacts.md for duplicate entries
• •If updating: show diff of changes, confirm with user
• •If adding: format entry per template, confirm placement (domain section)
• •Present final entry for approval before writing

Output Format

Present contact entry in markdown following template structure:

### First Name Last Name

- **Title**: [Job Title], [Company/Organization]
- **Email**: [email@domain.com](mailto:email@domain.com) or ???
- **Phone**: [+0 000-000-0000] or ???
- **LinkedIn**: [username](https://www.linkedin.com/in/username/) or N/A or ???
- **GitHub**: [username](https://github.com/username) or N/A or ???
- **Timezone**: [Timezone Name (Abbreviation, UTC+X)] or ???
- **Specializations**:
  - [Area 1]
  - [Area 2]
- **Notes**:
  - [Important context]

Field status markers:

• •??? = Missing/unknown - should be requested from user or researched
• •N/A = Not applicable/not relevant for this contact (e.g., no GitHub for non-developer)

Constraints

• •Template as scaffold: Use discovered templates as minimum structure
• •Validation first: Always validate email format and required fields before adding
• •Duplicate check: Search existing contacts before adding new entry
• •User confirmation: Always confirm before writing changes
• •Privacy awareness: Only include information user has permission to store
• •KISS and DRY: Each field conveys unique information
• •Characters: QWERTY keyboard typeable only - no em-dashes, smart quotes, emojis, or special Unicode

Contact Management Skill v1.0.0 - KemingHe/common-devx