CtrlK
BlogDocsLog inGet started
Tessl Logo

enrich-company-and-contact-data

Use for data-first company, contact, lead, and prospect discovery or enrichment, including firmographic or technographic completion, named-company profiling, entity resolution, ICP matching, prospect-list building, segmentation, trigger or sales-signal analysis, market and territory scans, and enrichment-backed comparisons. Exclude meeting preparation, outreach-led company research, and prioritization of an already established account book.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable enrichment-workflow skill with concrete output contracts and clear routing rules. It would benefit from consolidating restated source-ownership rules and making validation/feedback checkpoints more explicit.

Suggestions

Consolidate the source-ownership rules that appear in both 'Key Dependency Categories' and 'Overall Rules' to remove redundancy and trim tokens.

Add an explicit validate-then-fix feedback loop (e.g., re-check hard filters and identity confidence after enrichment, with a retry step) rather than leaving verification implicit.

Replace the repeated '{Follow the instructions...}' references at the end of each mode template with a single shared pointer to avoid cluttering all three output formats.

DimensionReasoningScore

Conciseness

The body is instruction-dense and avoids explaining concepts Claude already knows, but source-ownership rules are restated across 'Key Dependency Categories' and 'Overall Rules', leaving minor redundancy that could be trimmed.

4 / 5

Actionability

Concrete output templates with exact table columns, provider-specific load rules ('When...ZoomInfo, load zoominfo'), and precise decision rules give mostly executable guidance, though a few conditional phrases like 'use your best judgment to potentially include other data sources' are less specific.

4 / 5

Workflow Clarity

A clear two-stage workflow plus a 6-step Enrichment Ranking and verification rules ('Verify hard filters before calling a row qualified') provide good sequencing; the destructive/batch cap does not apply since the skill forbids writes, but feedback loops remain mostly implicit rather than validate-fix-retry.

4 / 5

Progressive Disclosure

Sections are well organized and content is appropriately split into three Modes with one-level-deep references to the index skill; no bundle files exist, and the repeated '{Follow the instructions...}' index references in every mode template are minor clutter rather than cleanly signaled once.

4 / 5

Total

16

/

20

Passed

Description

92%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 concretely lists capabilities, opens with an explicit trigger clause, and draws clear boundaries against adjacent skills. Slightly jargon-heavy trigger terms keep it just short of perfect on keyword naturalness.

DimensionReasoningScore

Specificity

The description enumerates many concrete actions—'firmographic or technographic completion, named-company profiling, entity resolution, ICP matching, prospect-list building, segmentation, trigger or sales-signal analysis, market and territory scans, and enrichment-backed comparisons'—giving comprehensive coverage of the domain.

5 / 5

Completeness

It opens with an explicit 'Use for...' trigger clause (when) and follows with a concrete action list (what), plus an 'Exclude...' boundary, clearly and explicitly answering both what and when.

5 / 5

Trigger Term Quality

Natural sales/revenue-ops terms like 'company, contact, lead, and prospect discovery', 'ICP matching', and 'segmentation' are well covered with synonyms, but the language leans slightly jargon-heavy (firmographic, technographic) and lacks the plainest phrasings a casual user might say.

4 / 5

Distinctiveness Conflict Risk

The explicit 'Exclude meeting preparation, outreach-led company research, and prioritization of an already established account book' carves a clear niche and minimizes conflict with adjacent sales skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 suspicious

Warning

Total

15

/

16

Passed

Repository
XiaomiMiMo/MiMo-Code
Reviewed

Table of Contents

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.