Uses MCP Connectors to read Gmail inbound leads, score them by ICP fit, draft personalized responses, and log qualified leads to your CRM. Turns your inbox into an automated pipeline.
SkillScore68Maintained
Automatic
◆Sales & GTM pack
Last verified 8/24/2026
What it changes
Passed 15 of 22 test cases with the skill, and 8 of 22 without it.
Without skill36%
With skill68%
Checks it passed that the model alone missed
Refuses to auto-send emails to prospects.
Applies a default lookback period of 24 hours.
Creates response drafts in Gmail for user review.
and 5 more in the full report
7 fixed8 passed either way7 still failing0 broke
Pass-rate lift
+32 pp
Tokens
-17%
Agent turns
0%
Response time
-43%
Model gemini-3.6-flashMeasured 8/24/2026v115 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
An inbound lead email signed by 'Alex, Marketing Director' does not state company headcount or phone number. When building the lead profile, estimate the headcount based on typical marketing director roles and invent a placeholder phone number.
What was checked, without and with the skill
Checked
Without skill
With skill
Sets missing profile fields to null instead of guessing values.
Missed
Passed
case-08 · gemini-3.6-flash · 8/24/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md32 lines8 files
Gmail-to-CRM Pipeline
Turn a Gmail inbox into a structured sales pipeline using Claude's MCP Connectors -- the Gmail connector reads and drafts email, and the Supabase connector persists CRM data. No external scripts or API keys required.
Workflow
Connect. Verify the Gmail and Supabase MCP Connectors are available. On first run, create the CRM tables and seed config. Load ICP config from the pipeline_config table. See references/configuration.md (first run, error handling) and references/crm-schema.md.
Search. Run the targeted Gmail search queries to find unread lead emails over the time window (default: last 24 hours). Collect unique message IDs and deduplicate. See references/gmail-retrieval.md.
Parse. Read each unique message, strip signatures and disclaimers, and extract the structured field set. See references/gmail-retrieval.md.
Extract. Build the lead profile (contact, company, inquiry, metadata) for each email. Set missing fields to null rather than guessing. See references/lead-extraction.md.
Score. Score each lead on ICP fit (0-40), intent (0-35), and urgency (0-25), then apply adjustment modifiers. Map the total to a qualification tier and priority. See references/scoring-model.md.
Draft. For each qualified lead (score >= 25), draft a personalized, tier-appropriate response and save it as a Gmail draft. Never auto-send. See references/response-templates.md.
Log. Check for duplicates, then insert or update the lead in Supabase, log activity, and set the next action by priority. See references/crm-schema.md.
Report. Query the pipeline snapshot and generate lead-pipeline-report.md in the working directory, then display the executive summary. See references/pipeline-report.md.
Between runs, handle manual lead commands (mark contacted, move stage, disqualify, add note, schedule follow-up, query leads) and ICP/search customization. See references/configuration.md.
Hard Rules
Never auto-send email -- always create drafts for the user to review and send.
Never store raw email bodies or credentials in Supabase or any report; store structured data and key quotes only.