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.

76

Quality

96%

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

92%

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 workflow skill with clear sequencing and verification gates and no basic-concept padding. The main gap is progressive disclosure: most detail lives inline in one file rather than being split into referenced materials.

Suggestions

Move the three per-mode output templates into a bundled reference file (e.g. references/output-templates.md) and link to it from each mode, keeping SKILL.md as a tighter overview.

Dedupe the source-ownership rules that recur across Key Dependency Categories, Overall Rules, and the Output Contract to tighten conciseness.

If a references/ bundle is added, list it so the progressive-disclosure structure is verifiable against actual files.

DimensionReasoningScore

Conciseness

The body is dense and domain-specific without explaining concepts Claude already knows (no primer on what a CRM or ICP is); it assumes competence throughout, though source-ownership rules recur mildly across sections.

3 / 3

Actionability

Provides concrete executable guidance: a 6-step ranking priority, provider-specific load rules (load `zoominfo`/`apollo` based on selected provider), explicit hard-filter verification, and copy-ready output table templates per mode.

3 / 3

Workflow Clarity

Workflow stages are numbered (Clarify/Gather, First Draft) with checkpoints ("make at most two narrow source calls...then ask the user to choose") and verification gates ("Verify hard filters before calling a row qualified"); the skill is read/discovery-only so the destructive-write cap does not apply.

3 / 3

Progressive Disclosure

References to the shared index skill are one level deep and well-signaled, but the body is a single >50-line file holding all detailed material (ranking, dependency categories, three mode templates) inline rather than split into reference files.

2 / 3

Total

11

/

12

Passed

Description

100%

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 description: concrete actions, natural trigger terms, and an explicit use/when clause with a negative carve-out that sharpens distinctiveness. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists 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" — rather than vague language.

3 / 3

Completeness

Opens with an explicit "Use for" trigger clause stating when to invoke it, plus an "Exclude" clause, so both what it does and when to use it are clearly answered.

3 / 3

Trigger Term Quality

Covers natural sales-domain terms a user would say (company/contact/lead/prospect discovery, enrichment, ICP matching, segmentation, market and territory scans) rather than only technical jargon.

3 / 3

Distinctiveness Conflict Risk

The explicit "Exclude meeting preparation, outreach-led company research, and prioritization of an already established account book" carve-out gives it a clear niche and reduces conflict with adjacent sales skills.

3 / 3

Total

12

/

12

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.