sales-tomba
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).
What this skill does
# 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 → `/sales-deliverability` - Buying signals and prioritization → `/sales-intent` - Connecting tools via Zapier/webhooks → `/sales-integration` Otherwise, answer directly from platform knowledge using the reference below. ## Step 3 — Tomba platform reference **Read `references/platform-guide.md`** for detailed module documentation, pricing, integrations, and data model. *You no longer need the platform guide details — focus on the user's specific situation.* ## Step 4 — Actionable guidance Based on the user's specific question, provide: 1. **Step-by-step instructions** with exact UI navigation or API calls 2. **Configuration recommendations** with specific values (e.g., "set limit to 50 for faster pagination") 3. **Common pitfalls** for the specific workflow 4. **Verification steps** — how to confirm it's working correctly ### Common workflows **Find all contacts at a target company**: 1. Domain Search with the company's domain → get all known emails 2. Filter by department (sales, engineering) and seniority (director+) 3. Verify the emails you plan to contact 4. Save to a lead list → export to CRM or campaign tool **Find a specific person's email**: 1. Email Finder with their name + company domain → get the email + confidence score 2. If confidence <80%, check Email Format for the domain to validate the pattern 3. Verify the email with Email Verifier before sending 4. Enrich the contact for additional context (title, social profiles) **Clean an existing list before a campaign**: 1. Bulk verify all emails → separate into valid, invalid, accept_all 2. Remove invalid emails immediately 3. For accept_all: include but monitor bounce rates closely 4. Enrich missing fields (names, titles) for personalization 5. Export clean, enriched list to your campaign tool **Monitor competitor tech stack**: 1. Technology endpoint → see what tools a company uses 2. Similar Domains → find competitor/adjacent companies 3. Combine with domain search to find the right contacts 4. Use for technographic-based outreach → see `/sales-intent` ## Gotchas *Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.* - **Don't skip email verification after finding.** The Email Finder returns probable emails based on pattern matching — they're not guaranteed deliverable. Always run found emails through the Email Verifier before adding them to campaigns. Sending to unverified emails destroys sender reputation. - **Don't ignore the Email Format endpoint.** Before searching for individual emails, check the domain's email format first (`/v1/email-format`). If you know the company uses `[email protected]` (85% match), you can validate results faster and skip low-confidence guesses. - **Don't waste credits on unfiltered domain searches.** A domain search on a large company can return thousands of results. Use department, seniority, and country filters to narrow to decision-makers you'll actually contact. Each search costs credits regardless of how many results you use. - **Don't forget about webhook callbacks for bulk jobs.** Bulk operations are asynchronous — the API returns immediately but processing continues in background. Use the `webhook_url` parameter to get notified when done instead of polling. Polling wastes API calls and may hit rate limits. - **Don't assume all plans include the same features.** Webhooks require Pro plan or above. Full domain search result downloads are plan-gated. Check your plan's limits before building workflows that depend on these features. - **Self-improving**: If you discover something not covered here, append it to `references/learnings.md` with today's date. ## Step 5 — Related skills - `/sales-enrich` — Enrichment strategy across tools (waterfall enrichment, CRM hygiene, credit optimization) - `/sales-prospect-list` — Build targeted prospect lists with ICP definition and segmentation - `/sales-deliverability` — Email deliverability setup (SPF/DKIM/DMARC, warmup, inbox placement) - `/sales-intent` — Interpret buying signals and prioritize accounts (use Tomba's tech detection as a signal) - `/sales-integration` — Connect Tomba to CRM and other tools via Zapier, Make, or API - `/sales-cadence` — Design outbound sequences for contacts found in Tomba - `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. Install: `npx skills add sales-skills/sales --skill sales-do` ## Examples ### Example 1: Finding emails at a target company **User says**: "I need to find all the sales leaders at Stripe using Tomba" **Skill does**: 1. Recommends Domain Search on `stripe.com` with department=sales and seniority=executive,senior 2. Shows how to filter results and interpret confidence scores 3. Recommends verifying emails before outreach 4. Suggests saving results to a lead list and exporting to campaign tool **Result**: Filtered, verified list of sales leaders at Stripe ready for outreach ### Example 2: Bulk email verification before a campaign **User says**: "I have a CSV of 3,000 contacts and need to verify all the emails before launching a Lemlist campaign" **Skill does**: 1. Walks through bulk verification setup — CSV format, upload process 2. Recommends using webhook callback for async completion notification 3. Explains how to interpret results (valid, invalid, accept_all, unknown) 4. Advises removing invalid emails and flagging accept_all for monitoring 5. Points to `/sales-lemlist` for importing the clean list into Lemlist **Result**: Verified contact list with clear action per status, ready for campaign import ### Example 3: Using the Tomba API for automated enrichment **User says**: "I want to auto-enrich new HubSpot contacts with Tomba
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.