Tomba Contact Intelligence

Use Tomba MCP tools for contact discovery, verification, enrichment, and company research.

Security Scan

The skill's requirements and instructions align with its stated purpose (Tomba contact discovery/enrichment) and it is an instruction-only skill that asks only for the expected Tomba credentials.

Purpose & Capability

Name/description request Tomba MCP functionality and the skill only requires TOMBA_API_KEY and TOMBA_SECRET_KEY and references Tomba MCP tools — these are coherent and expected for a Tomba integration.

Instruction Scope

SKILL.md confines behavior to selecting and sequencing named Tomba MCP tools, asks for only the minimal user inputs needed, and does not instruct reading unrelated files, environment variables, or exfiltrating data to third‑party endpoints.

Install Mechanism

No install spec or code is included (instruction-only), so nothing is downloaded or written to disk by the skill itself — lowest-risk install profile.

Credentials

The skill requires two Tomba credentials (API and secret). That is proportionate and expected for using the Tomba MCP server; SKILL.md does not reference any other env vars or unrelated secrets.

Persistence & Privilege

The skill is not always-enabled and is user-invocable; it does not request elevated persistence or modification of other skills or system-wide settings.

Assessment

This skill is internally consistent with a Tomba integration, but it will need your TOMBA_API_KEY and TOMBA_SECRET_KEY to operate. Only install it if you trust the source (the registry metadata lists the homepage tomba.io but the skill's repository/source is marked 'unknown'); verify the skill origin or compare SKILL.md/README to the official Tomba docs if unsure. Limit the API key permissions if possible, monitor API usage after enabling the skill, and rotate/revoke keys if you stop using it.

Use this skill when the user needs contact discovery, email verification, lead enrichment, phone lookup, domain research, company research, or technology/competitor analysis.

This skill assumes the Tomba MCP server is already connected and the following tools are available in the session:

• domain_search
• email_finder
• email_verifier
• email_enrichment
• author_finder
• linkedin_finder
• phone_finder
• phone_validator
• email_count
• similar_finder
• technology_finder
• companies_search

When To Use

Use this skill for requests like:

• find the best person to contact at a company
• guess and verify an email address
• enrich a lead with company and contact data
• find phone numbers tied to an email, domain, or LinkedIn profile
• research a domain's scale, technology, or similar competitors
• build target company lists with industry, size, location, or revenue filters

Do not use this skill for general web research that does not need Tomba data, or when the user is asking for unsupported actions such as sending emails.

Tool Selection

Choose tools based on the user's objective:

• Use email_finder when you have a person name plus company or domain.
• Use email_verifier after email_finder when the user needs a validated result.
• Use email_enrichment when the user already has an email and wants more profile data.
• Use domain_search when the user wants contacts for a company or domain without a specific person.
• Use phone_finder when the user wants phone numbers from an email, domain, or LinkedIn profile.
• Use phone_validator when the user provides a phone number and wants validation or carrier details.
• Use linkedin_finder when the user has a LinkedIn URL and wants an email.
• Use author_finder when the user provides an article URL and wants the author's contact.
• Use email_count to estimate the reachable contact surface for a domain.
• Use technology_finder to inspect a company's website stack.
• Use similar_finder to find comparable or competing domains.
• Use companies_search when the user wants a company list filtered by market, geography, size, revenue, type, or industry.

Workflow Guidance

Prefer short multi-step workflows that improve confidence:

1. If the user names a person, start with email_finder.
2. Verify the result with email_verifier before presenting it as high-confidence.
3. If the user wants broader prospecting, use companies_search or domain_search first.
4. Add email_enrichment, phone_finder, technology_finder, or similar_finder only when they answer the user's actual goal.

When several plausible contacts exist, rank them by relevance to the requested department or role and say why the top result was selected.

If the user does not provide enough information, ask only for the missing fields that materially improve the result, such as company domain, full name, article URL, LinkedIn URL, or target department.

Output Expectations

When returning results:

• distinguish clearly between confirmed data and inferred data
• mention whether an email was verified
• include the source input used for each lookup
• keep summaries concise and decision-oriented
• if no high-confidence result is found, say that directly and suggest the next best lookup path

Common Playbooks

Find A Person's Best Email

1. Use email_finder with the person's name and company.
2. Use email_verifier on the strongest candidate.
3. If requested, use email_enrichment and phone_finder.

Research A Company For Outreach

1. Use domain_search to identify existing contacts.
2. Use email_count to estimate contact coverage.
3. Use technology_finder and similar_finder for company context.

Build A Target Account List

1. Use companies_search with the user's market filters.
2. For top matches, use domain_search or email_finder for contact discovery.
3. Verify candidate emails before presenting them as final.