Enrich Company And Contact Data
Use for data-first company, contact, lead, and prospect discovery or enrichment...
Install
npx skills add XiaomiMiMo/MiMo-Code --skill enrich-company-and-contact-data -g -a claude-code -y- Repository
- XiaomiMiMo/MiMo-Code13.7k
- Category
- Writing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,621 tokens
- Runs scripts
- No, instructions only
What it does
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.
Enrich Company And Contact Data
Context-Gathering Intake
Whenever this skill asks for context, strongly prefer using the answers-ask-user-input skill and the ask_user_input tool over other tools such as request_user_input; otherwise ask directly in the conversation.
Prepare a sales person with a trusted, decision-ready view of companies or contacts: what is known, what is a strong match, what is still uncertain, and what action the data supports. This skill owns evidence resolution, ICP-fit and coverage comparisons, and source-grounded signal analysis; it does not own rep-work priority, outreach execution, or CRM writes.
Common Skill Instructions
MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.
Enrichment Ranking
Use this priority order when the request is broad or the working set is ambiguous.
- Explicit user-provided rows, domains, contacts, companies, ICP criteria, requested fields, or stated ranking rule
- The named CRM account set, territory, target list, or documented ICP that the user points to
- Entities that satisfy every hard filter, such as geography, industry, company size, technology, role, or seniority
- Entities with high-confidence identity resolution and enough comparable evidence to support the requested output
- Entities with a clear fit implication, reachable buying-team path, or source-grounded external signal
- Near matches and unresolved entities, clearly separated from qualified results
Do not silently broaden a supplied list into discovery, merge ambiguous entities, or rank by a criterion the user cannot inspect.
If the user asks to score or tier a list, keep the judgment limited to ICP fit, enrichment completeness, identity confidence, or defined signal strength. If the user asks which accounts to work now, where to focus, or what rep action deserves priority, route to prioritize-accounts.
