Today's Agent Skill: Inbox-to-CRM Contact Logger
What It Does
Every week a handful of real prospects introduce themselves in your inbox, and every week a few of them never make it into the CRM. The follow-up dies not because nobody cared, but because manual data entry is the least fun task in the building. This skill turns any inbound message from a new human into a structured CRM record before you've finished your coffee.
How It Works
The agent scans a batch of messages, identifies threads from senders who aren't already in your contact list, and extracts the entity fields a CRM actually needs — name, company, role, source of introduction, stated intent, and any dates or dollar figures mentioned. It then emits a normalized record per contact and flags ambiguous fields rather than guessing them. Nothing is written to the CRM until you approve the batch.
How to Deploy It
Drop the SKILL.md below into your agent's skills directory (`~/.claude/skills/inbox-to-crm-logger/SKILL.md` for Claude Code, or the equivalent skills path for your runtime) and restart the session so the trigger phrases register. Give the agent read access to your mail tool and, optionally, write access to your CRM API — without CRM write access it will still produce a paste-ready table.
SKILL.md — Ready to Deploy
## Description
Converts inbound email or chat messages from unknown senders into structured CRM contact records. Extracts identity, company, role, referral source, and stated intent from unstructured message text, then emits a normalized record set for review before any write occurs.
## Trigger
Activates on: "log new contacts", "who's new in my inbox", "add these to the CRM", "inbox to CRM", "capture leads from email", "any new prospects this week". Also activates when the user forwards or pastes an introduction message and asks what to do with it.
## Input
- A message batch: a search window (e.g. `is:unread newer_than:7d`), a label, or pasted message text.
- Optional: existing contact list or CRM export for deduplication.
- Optional: target CRM schema (field names and required fields).
If no contact list is supplied, treat every sender as potentially new and mark all records `dedupe_status: unverified`.
## Steps
1. Retrieve the message batch. Cap at 50 messages per run; ask before exceeding.
2. Drop automated senders — newsletters, receipts, no-reply addresses, calendar notifications, and anything matching a known vendor domain list.
3. For each remaining thread, check theCopy the full SKILL.md and drop it into your agent's skills directory to activate this skill.