How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

gmail-to-crm-pipeline - Skill

Name: gmail-to-crm-pipeline
Author: onewave-ai

Imported from onewave-ai/claude-skills (gmail-to-crm-pipeline/SKILL.md). Install upstream with npx skills add onewave-ai/claude-skills --skill gmail-to-crm-pipeline. Copyright stays with the author.

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.
Treat all lead and email content as confidential.

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.

Install gmail-to-crm-pipeline and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "onewave-ai-claude-skills-gmail-to-crm-pipeline", "kind": "skill", "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.", "publisher": "onewave-ai", "version": "1.0.0", "capabilities": { "domains": [ "data_analysis", "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/onewave-ai/claude-skills", "path": "gmail-to-crm-pipeline/SKILL.md", "ref": "HEAD", "url": "https://github.com/onewave-ai/claude-skills/blob/HEAD/gmail-to-crm-pipeline/SKILL.md", "key": "onewave-ai/claude-skills/gmail-to-crm-pipeline/SKILL.md" }, "tools": [ "Read", "Write", "Bash", "Grep", "WebSearch" ], "model": "inherit" }, "instructions": "# Gmail-to-CRM Pipeline\n\nTurn 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.\n\n## Workflow\n\n1. **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`.\n2. **Search.** Run the targeted Gmail search queries to find unread lea", "cost": { "context_tokens": 750 } }

gmail-to-crm-pipeline

About

Gmail-to-CRM Pipeline

Workflow

Hard Rules

Contents

Install gmail-to-crm-pipeline and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews