zoominfo

Use only when a focused Sales workflow has selected a present and connected ZoomInfo connector, or the user explicitly asks for ZoomInfo company search, contact search, enrichment, intent, similarity, recommendations, or research. Do not use when another enrichment source is selected.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/opencode/src/skill/builtin/.bundle/sales/workflows/zoominfo/SKILL.md

Quality

Content

62%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, well-structured operational guide with clear sequencing, explicit verification, and a concrete output template. Its main weaknesses are length/repetition and heavy inlining of reference-style content that progressive disclosure would move into separate files.

Suggestions

Consolidate the repeated 'do not present ZoomInfo as CRM ground truth' and similar guardrails into a single canonical statement to reduce duplication and token cost.

Extract the connector-lane catalog, lookup taxonomy, and output-format template into one-level-deep reference files (e.g., references/lanes.md, references/output-format.md) linked from SKILL.md to improve progressive disclosure.

Add a small number of literal tool-call argument examples (e.g., a sample search_companies filter object) to lift actionability from mostly-executable to copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining generic concepts Claude already knows, but it runs long (~220 lines) with repeated restatements of the same guardrails (e.g., not presenting ZoomInfo as CRM ground truth appears multiple times) that could be tightened. It earns efficiency in places but is padded by duplicated exhortations.	3 / 5
Actionability	It gives concrete, executable guidance such as specific action names (search_companies, enrich_contacts, lookup), ordered resolution patterns, and a copy-ready output format template, with only minor gaps (no literal tool-call argument examples). This is an instruction-only skill and the guidance is actionable.	4 / 5
Workflow Clarity	The Default Resolution Pattern is a clearly numbered sequence with an explicit verification checkpoint ('Verify that returned rows actually satisfy the user's hard constraints') and Failure Handling covers error recovery. It falls just short of 5 because validation/retry checkpoints are present for identifier shape but not uniformly across all batch/enrichment steps.	4 / 5
Progressive Disclosure	The content is well-sectioned but almost entirely inline in SKILL.md with no bundle files present; the only references are to an external parent skill (../index/SKILL.md) via anchors. Large reference-style content (lane lists, lookup taxonomies, output template) is inlined rather than split into one-level-deep files, so it sits at 'some structure, could be better organized'.	3 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that clearly states both what the skill does and when to use it, with explicit anti-trigger guidance. It is highly distinct from sibling enrichment skills and uses natural trigger terms.

Dimension	Reasoning	Score
Specificity	Names the ZoomInfo domain and lists several concrete action families (company search, contact search, enrichment, intent, similarity, recommendations, research), with minor gaps in coverage. It is comprehensive on operation types but stops slightly short of the fullest concrete-action enumeration seen at score 5.	4 / 5
Completeness	It explicitly answers 'when' via 'Use only when... selected a present and connected ZoomInfo connector, or the user explicitly asks for ZoomInfo company search...' and 'what' via the listed operation types, with concrete trigger phrases and an explicit anti-trigger ('Do not use when another enrichment source is selected').	5 / 5
Trigger Term Quality	Phrases like 'ZoomInfo company search', 'contact search', 'enrichment', 'intent', 'similarity', 'recommendations', and 'research' are natural terms a user would say, with good coverage but a few common variations omitted. It does not quite reach the exhaustive synonym/extension-level coverage of score 5.	4 / 5
Distinctiveness Conflict Risk	The skill is scoped to a named connector (ZoomInfo) with a present-and-connected condition and an explicit exclusion of other enrichment sources, giving it a clear niche and minimal conflict risk relative to sibling Sales skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: XiaomiMiMo/MiMo-Code
Path: packages/opencode/src/skill/builtin/.bundle/sales/workflows/zoominfo/SKILL.md
Commit: ec3f989

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.