ravi-contacts_skill

Overview

This skill manages contacts tied to your identity so you can list, search, create, update, and delete people you interact with. It resolves names to email addresses or phone numbers before sending messages and keeps interaction metadata like counts and last interaction timestamps. Contacts are stored in plaintext and are intended for communication routing, not credential storage.

How this skill works

Use commands to list, fuzzy-search, retrieve, create, update, or delete contacts. The skill returns JSON shapes for all operations and tracks interaction_count and last_interaction_dt automatically for contacts created from email or SMS exchanges. When sending email or SMS, the skill is queried first to resolve a name to an email or phone; if multiple matches appear the user is prompted to confirm.

When to use it

• Before sending email or SMS to resolve a person’s name to an email address or phone number.
• To maintain a simple address book of people you interact with (email, phone, display name, nickname).
• To mark frequently contacted or verified people as trusted for routing trusted messages.
• To import or clean up contacts auto-created from message interactions.
• When automation needs JSON contact data for integration with email or SMS workflows.

Best practices

• Always run searches before sending messages (search by name or email) to avoid misaddressing.
• Use E.164 format for phone numbers (include the leading + and country code).
• Do not store passwords, API keys, or other secrets in contact fields—contacts are plaintext.
• Mark contacts as trusted only for known, verified people to enable trusted routing.
• Use --json for all commands to ensure predictable, machine-readable output.

Example use cases

• User says "email Alice" → skill searches contacts, finds one match, and supplies Alice’s email to the email-sending flow.
• Automated workflow lists contacts and exports JSON for CRM sync or backup.
• Create a manual contact for a new vendor with display name, nickname, email, and phone before first outreach.
• Update a contact’s email when someone changes addresses so future sends resolve correctly.
• Clean up duplicate auto-contacts created from interactions by merging or deleting entries.