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 context lives in a thread nobody re-reads, and by the time someone asks 'where did that lead go?', the answer is nowhere. This skill turns inbound email into structured CRM-ready records automatically.
How It Works
The agent scans a defined mail window for messages that look like new external relationships — first-contact intros, referrals, inbound inquiries — and skips internal chatter and existing threads. For each match it extracts the person, company, role, stated need, and source, then emits a normalized record with a suggested pipeline stage. Output is a flat table you can paste, import, or hand to a CRM API call.
How to Deploy It
Drop the SKILL.md into your agent's skills directory (`~/.claude/skills/inbox-to-crm-logger/SKILL.md` or your platform's equivalent) and confirm it has read access to a mail tool. Run it on a daily or weekly cron and route the output to whichever CRM sink you use — clipboard, CSV, or a direct API write.
SKILL.md — Ready to Deploy
## Description
Scans a mailbox window for inbound messages that represent new external relationships and converts them into structured, CRM-ready contact records. Filters out internal traffic, automated mail, and continuations of existing threads so only genuinely new relationships surface. Produces a normalized table plus a short confidence note on any ambiguous record.
## Trigger
Invoke when the user says: log new contacts, inbox to CRM, who's new in my inbox, capture leads from email, update the CRM from mail. Also fires on a scheduled run (daily or weekly) when configured as a recurring job.
## Input
- Mail window (default: last 7 days; accepts explicit date ranges)
- Optional domain exclusion list (your own domains, vendors, newsletters)
- Optional existing-contact list to deduplicate against
## Steps
1. Retrieve messages in the requested window. Read headers and first 500 words of body only — do not load full threads.
2. Discard any message where the sender domain is on the exclusion list, the message is automated (no-reply, notification, receipt), or the thread has more than two prior messages.
3. For each surviving message, extract: full name, email, company, role orCopy the full SKILL.md and drop it into your agent's skills directory to activate this skill.