sales-tomba

name	sales-tomba
description	Tomba.io platform help — domain search, email finder, email verifier, enrichment, author finder, LinkedIn finder, phone finder, bulk operations, browser extensions, API, integrations. Use when you can't find a prospect's email address in Tomba, Tomba verification results look wrong, your enriched contacts are missing data, the Tomba API isn't returning expected results, a Tomba integration isn't syncing, or your Tomba lead lists are disorganized. Do NOT use for enrichment strategy across tools (use /sales-enrich), building prospect lists (use /sales-prospect-list), cross-platform deliverability (use /sales-deliverability), or connecting tools generically (use /sales-integration).
argument-hint	[describe what you need help with in Tomba]
license	MIT
version	1.0.0
tags	["sales","enrichment","email-finder","verification","platform"]
github	https://github.com/tomba-io

Tomba Platform Help

Help the user with Tomba.io platform questions — from domain search and email finding through verification, enrichment, bulk operations, API, and integrations.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

1. What area of Tomba do you need help with?

   • A) Domain Search — finding all emails at a company
   • B) Email Finder — finding a specific person's email
   • C) Email Verifier — validating email addresses
   • D) Email Enrichment — enriching contacts with company/social data
   • E) Author Finder — finding blog author emails
   • F) LinkedIn Finder — finding emails from LinkedIn profiles
   • G) Phone Finder — finding phone numbers
   • H) Bulk Operations — processing thousands of records at once
   • I) Leads & Lists — managing saved contacts and lists
   • J) Browser Extension — Chrome/Edge/Safari/Firefox extension
   • K) Google Sheets / Excel — add-on or add-in
   • L) API — programmatic access, automation, custom integration
   • M) Integrations — Zapier, HubSpot, Salesforce, Pipedrive, Make, n8n
   • N) Account & Billing — plans, credits, team members
   • O) Something else — describe it

2. What's your role?

   • A) Sales rep / AE / BDR
   • B) Sales manager / team lead
   • C) RevOps / Sales Ops
   • D) Recruiter
   • E) Marketing
   • F) Founder / solo seller
   • G) Developer / engineering
   • H) Other

3. What are you trying to accomplish? (describe your specific goal or question)

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit.

Step 2 — Route or answer directly

If the request maps to a specialized skill, route:

• Enrichment strategy across tools → /sales-enrich
• Building prospect lists / ICP definition → /sales-prospect-list
• Email deliverability / SPF/DKIM/DMARC →