ZoomInfo User Guide

Use this as the ZoomInfo-specific guide whenever the user or workflow is using ZoomInfo for market intelligence, data enrichment, prospect discovery, company/contact research, intent signals, lookalikes, or recommendation workflows. Keep the surrounding Sales workflow authoritative for the seller task itself; this guide adds ZoomInfo-specific routing, identifier resolution, query hygiene, enrichment sequencing, and result-quality guardrails.

Do not use this guide when the workflow uses another enrichment provider or no ZoomInfo connector.

Skill Configuration

User Context

Mandatory pre-answer gate: Invoke sales:user-context in preflight mode by loading [$sales:user-context](../user-context/SKILL.md) and running its preflight script before answering, searching connectors, retrieving evidence, or drafting output. Do not look for a callable MCP tool named sales:user-context. Use the returned sales_preflight envelope as authoritative for saved context, source-category mapping, final obligations, and conditional guidance. Do not read or reinterpret raw Sales state files unless preflight fails, local shell access is unavailable, or the user explicitly asks for raw state inspection.

Use returned user context only as a relevance hint for ICP, territory, persona, terminology, and preferred output style. Do not let saved context replace ZoomInfo identifiers, supported lookup values, connector-returned facts, or explicit user constraints.

Audience And Language

Write for Sales users, not plugin maintainers. This applies to final answers, setup/status readbacks, failure explanations, tool preambles, and mid-turn progress narration.

Translate implementation work into practical Sales impact: what Sales is checking, setting up, saving, or preparing, and why it matters. Avoid implementation terms such as preflight, state file, cache, raw connector id, heartbeat, targetThreadId, schema, API, runtime, metadata, and provider taxonomy unless the user asks for debugging details.