recommend-contacts
Get AI-powered contact recommendations at a target company based on your ZoomInfo interaction history. Provide a company name or domain and optionally a use case.
What this skill does
# Recommended Contacts Get ML-ranked contact recommendations at a target company, personalized to your ZoomInfo usage and CRM data. ## Input The user will provide via `$ARGUMENTS`: - A company name, domain, or ZoomInfo company ID (required) - Optionally: a use case — "prospecting", "deal acceleration", or "renewal" (defaults to PROSPECTING) - Optionally: how many results they want (defaults to 25, max 100) ## Workflow 1. **Lookup metadata first** — before calling any other MCP tool, use `lookup` to load reference data for any fields relevant to the request. Use the returned `id` values (not display names) in all subsequent API calls. This ensures accurate parameter resolution and result interpretation. 2. **Resolve the company** if the user provided a name or domain: - Use `search_companies` with `companyName` or `companyWebsite` to find the company — use lookup `id` values for any filters. - Extract the ZoomInfo company ID from the result. 3. **Enrich the company** using `enrich_companies` with the resolved `companyId` to get firmographic context (industry, size, revenue, business model). This context is used to interpret the recommendations. 4. **Map the use case** to the correct enum value: - "prospecting" or default → `PROSPECTING` (based on contacts you've viewed, copied, or exported on the ZoomInfo platform; has cold-start support) - "deal acceleration" or "new business" → `DEAL_ACCELERATION` (based on contacts in closed-won CRM opportunities for new business) - "renewal", "growth", or "expansion" → `RENEWAL_AND_GROWTH` (based on contacts in closed-won CRM opportunities for renewals) 5. **Get recommendations** using `get_recommended_contacts` with: - `ziCompanyId`: the resolved ZoomInfo company ID - `useCaseType`: the mapped enum value - `pageSize`: user-specified count or 25 6. **Enrich the top contacts** using `enrich_contacts` on the top 10 results (batch of 10) to get full contact details including email, direct phone, and accuracy scores. ## Output Format ### Target Company One-line summary: [Company Name] — [Industry], [Employee Count] employees, [Revenue], [HQ Location] ### Use Case State which use case was used and what it means: - **PROSPECTING**: "Recommendations based on contacts similar to those you've recently viewed, copied, or exported in ZoomInfo." - **DEAL_ACCELERATION**: "Recommendations based on contact patterns from your CRM's closed-won new business deals." - **RENEWAL_AND_GROWTH**: "Recommendations based on contact patterns from your CRM's closed-won renewal deals." ### Recommended Contacts | Rank | Name | Title | Department | Management Level | Email | Direct Phone | Accuracy | Score | |------|------|-------|------------|-----------------|-------|-------------|----------|-------| | 1 | | | | | | | | | | 2 | | | | | | | | | For each contact, use the `meta` field from the recommendation response to explain WHY they were recommended. The meta describes the reference person the recommendation was based on. Present this as a "Why Recommended" note below the table or as an additional column. ### Recommendation Analysis Group the recommended contacts by pattern: - **By Department**: Which departments are most represented? (e.g., "8 of 25 are in Sales, 6 in Marketing") - **By Seniority**: What management levels dominate? (e.g., "Heavily weighted toward Director and VP") - **By Function**: What job functions appear most? (e.g., "Strong signal toward revenue-facing roles") Use the resolved lookup values to categorize accurately — do not guess department or management level labels. ### Engagement Priority Rank the top 5 contacts to engage first, with reasoning: - Who has the highest combined relevance (recommendation score) and reachability (accuracy score)? - Who is the likely entry point vs. the likely decision-maker? - Suggested outreach sequence ### Next Steps - Use `/zoominfo:enrich-contact` to deep-dive on any specific person - Use `/zoominfo:find-buyers` if you need to filter by specific persona criteria beyond what recommendations provide - If recommendations are sparse, note that PROSPECTING recommendations improve as you use ZoomInfo more (view, copy, export contacts). DEAL_ACCELERATION and RENEWAL_AND_GROWTH require CRM integration. ### Important Notes on Scores - The `score` (general similarity) and `reRankingScore` (propensity-adjusted) are not directly comparable to each other - Higher scores indicate stronger fit but do not guarantee response rates - Recommendations refresh daily based on your latest platform and CRM activity
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.