gmail-to-crm-pipeline — Claude Code skill: Gmail leads to CRM
gmail-to-crm-pipeline reads unread Gmail inquiries, scores each lead against your ICP, and writes qualified ones into Supabase. Replies stay as drafts.
MIT 260 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill gmail-to-crm-pipeline -a claude-codeWhat gmail-to-crm-pipeline does
Two MCP connectors carry the work: Gmail for reading and drafting, Supabase for the CRM rows. The skill needs no separate scripts and no API keys of its own.
Each run searches unread mail inside a time window, 24 hours by default, then strips signatures and extracts a lead profile. Fields it cannot find stay null rather than being guessed. Scoring splits into ICP fit (0 to 40), intent (0 to 35) and urgency (0 to 25). At 25 or above the lead gets a draft reply matched to its tier and a row in Supabase. Nothing is sent automatically.
A run finishes with lead-pipeline-report.md in the working directory and a summary on screen. Neither connector is optional: step one checks both are reachable, and the first run also creates the CRM tables and reads ICP settings from pipeline_config. Raw email bodies and credentials stay out of Supabase and out of the report.
What it helps with
- turn unread Gmail inquiries into structured lead records
- score an inbound request by ICP fit, intent and urgency
- draft a tier-matched reply without sending it
- upsert a qualified lead into Supabase while skipping duplicates
- produce a pipeline report as
lead-pipeline-report.md
Example prompts for the agent
- Run the pipeline over unread mail from the last 24 hours and score the leads.
- Mark this lead as contacted and schedule a follow-up for tomorrow.
- Rebuild
lead-pipeline-report.mdand show me the pipeline summary.
How to install gmail-to-crm-pipeline
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill gmail-to-crm-pipeline -a claude-code2Manually: put the files in place
~/.claude/skills/gmail-to-crm-pipeline/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gmail-to-crm-pipeline/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill gmail-to-crm-pipeline -a codex2Manually: put the files in place
.agents/skills/gmail-to-crm-pipeline/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill gmail-to-crm-pipeline -a cursor2Manually: put the files in place
.cursor/skills/gmail-to-crm-pipeline/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills gmail-to-crm-pipeline2Manually: put the files in place
.github/skills/gmail-to-crm-pipeline/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill gmail-to-crm-pipeline -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path gmail-to-crm-pipelineManually: put the files in place
.devin/skills/gmail-to-crm-pipeline/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill gmail-to-crm-pipeline -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about gmail-to-crm-pipeline
How do I install gmail-to-crm-pipeline in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill gmail-to-crm-pipeline -a claude-code. The skill file lands at ~/.claude/skills/gmail-to-crm-pipeline/SKILL.md.
What does gmail-to-crm-pipeline do?
It searches unread Gmail, builds a lead profile from each message, scores ICP fit, intent and urgency, writes a draft reply, and logs the qualified lead in Supabase.
Do I need API keys for it?
No. It runs on the Gmail and Supabase MCP connectors, with no outside scripts or API keys involved. Both connectors still have to be connected before the first run.
Source text
SKILL.md · MIT
--- name: gmail-to-crm-pipeline description: 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. tools: Read, Write, Bash, Grep, WebSearch model: inherit --- # 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 1. **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`. 2. **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`. 3. **Parse.** Read each unique message, strip signatures and disclaimers, and extract the structured field set. See `references/gmail-retrieval.md`. 4. **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`. 5. **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`. 6. **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`. 7. **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`. 8. **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. - Treat all lead and email content as confidential. ## Contents - `references/gmail-retrieval.md` -- Gmail MCP tools, search queries, parsing rules, extracted field set. - `references/lead-extraction.md` -- Lead profile JSON schema and extraction guidelines. - `references/scoring-model.md` -- ICP, intent, urgency scoring tables; tier mapping; adjustment rules. - `references/response-templates.md` -- Per-tier response templates, personalization rules, anti-patterns, draft creation. - `references/crm-schema.md` -- Supabase MCP tools, table DDL, logging procedure and SQL. - `references/pipeline-report.md` -- Report Markdown structure and reporting SQL queries. - `references/configuration.md` -- First-run setup, customization, manual commands, error handling, privacy, invocation triggers.
© OneWave-AI · MIT · OneWave-AI/claude-skills