Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

sales-enrich销售丰富

Agent Skill

sales-enrich 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,680

周安装

70

GitHub Stars

13

下载量

560
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:sales-enrich(销售丰富)
来源仓库:https://github.com/sales-skills/sales
仓库路径:skills/sales-enrich
安装命令:
npx skills add https://github.com/sales-skills/sales --skill sales-enrich
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sales-skills/sales --skill sales-enrich

简介

sales-enrich 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 当前顶部介绍:sales-enrich 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。
  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。

SKILL.md

Enrich Contacts & Clean CRM Data

Help the user enrich contacts and companies with verified data, clean stale CRM records, and optimize their enrichment workflow. This skill is platform-agnostic but references Apollo.io as the primary tool. The same strategies apply to ZoomInfo, Clay, Lusha, Cognism, or any enrichment provider.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

  1. What do you need to do?

- A) Enrich a list of contacts with emails/phones - B) Enrich company/account records with firmographic data - C) Clean up stale or incomplete CRM data - D) Set up ongoing auto-enrichment - E) Deduplicate contacts or accounts - F) Verify existing email addresses before a campaign - G) Other — describe it

  1. How many records are involved?

- A) Under 100 (manual/one-time) - B) 100-1,000 (batch job) - C) 1,000-10,000 (bulk operation) - D) 10,000+ (large-scale cleanup) - E) Ongoing (continuous enrichment of new records)

  1. What enrichment tool(s) do you have?

- A) Apollo.io - B) ZoomInfo - C) Clay - D) Lusha / Cognism - E) Clearbit / Breeze - F) Multiple providers (waterfall) - G) None yet — recommend one

  1. What data do you need?

- A) Email addresses (verified/deliverable) - B) Phone numbers (direct/mobile) - C) Both email and phone - D) Firmographic data (company size, revenue, industry, tech stack) - E) All of the above

Step 2 — Enrichment strategy

Choose the right approach based on volume and frequency:

Single-record enrichment

  • When: Researching a specific prospect, manual prospecting
  • How: Look up individual records in your enrichment tool or via API
  • Credit cost: 1 credit per person (email), more for phone numbers
  • Best for: High-value ABM targets, executive-level contacts

Batch enrichment

  • When: Enriching a list before launching a campaign
  • How: Upload CSV or select records in-platform for bulk enrichment
  • Credit cost: 1 credit per record enriched (plan carefully)
  • Best for: Campaign prep, list cleaning before outreach

Auto-enrichment

  • When: Keeping CRM data fresh continuously
  • How: Set up rules to enrich new records on creation or on a schedule
  • Credit cost: Ongoing — budget credits monthly
  • Best for: Teams with steady lead flow who need data quality without manual effort

Waterfall enrichment

  • When: Single provider doesn't have enough coverage
  • How: Try Provider A first → if no result, try Provider B → then Provider C
  • Credit cost: Only pay for successful enrichments at each level
  • Best for: Maximizing coverage when targeting niche personas or international contacts
  • Key waterfall providers:
ProviderStrengthCoverage
ClayPurpose-built waterfall across 150+ providersBroadest — aggregates multiple sources
ApolloEmail + phone enrichment (waterfall in beta)275M+ contacts
ZoomInfoEnterprise-grade firmographic + contact321M+ contacts
Seamless.AIReal-time verified emails + mobiles1.8B+ emails, 414M+ mobiles
CognismEMEA/international mobile numbersStrong EU coverage
LushaQuick email + direct dial lookup100M+ contacts
Hunter.ioDomain search + email finder + verifierEmail-focused, bulk operations
TombaDomain search + email finder + bulk enrichment430M+ indexed emails
Prospeo5-step email verification + company enrichment280M+ leads
Snov.ioEmail finder + verifier + campaigns600M+ contacts

For detailed per-provider workflows, API endpoints, and credit economics, see references/platforms.md

Step 3 — Execute the enrichment

Pre-enrichment checklist

  • Deduplicate first: Remove duplicate records before enriching — don't pay to enrich the same person twice
  • Filter to qualified records only: Don't enrich contacts you'll never reach out to
  • Check existing data: Skip records that already have verified emails/phones
  • Estimate credit cost: Records × credit cost per record. Stay within budget.
  • Set enrichment scope: Choose which fields to enrich (email only is cheaper than email + phone + firmographic)

For platform-specific enrichment workflows, API endpoints, credit economics, and bulk operation instructions, see references/platforms.md.

Compliance checklist

Before enriching and contacting, verify compliance with data privacy regulations in your target regions:

EU contacts (GDPR):

  • You have a lawful basis for processing (legitimate interest for B2B outreach is common, but document it)
  • Your enrichment provider has a GDPR-compliant data sourcing policy (check their DPA)
  • You can honor right to erasure requests — if someone asks to be deleted, you can remove them from all systems
  • Your outreach includes a clear way to opt out
  • You're not enriching personal data beyond what's necessary (data minimization principle)

US contacts (CAN-SPAM):

  • Every email includes a physical mailing address
  • Every email includes a working unsubscribe link
  • Unsubscribe requests are honored within 10 business days
  • Subject lines are not deceptive
  • The email is identified as an advertisement (if applicable)

California contacts (CCPA/CPRA):

  • You provide a "Do Not Sell My Personal Information" option if applicable
  • You can disclose what personal data you've collected if a consumer requests it
  • Your enrichment vendor's data collection practices comply with CCPA

General rules:

  • If someone unsubscribes, suppress them globally — don't re-enrich and re-add them next month
  • If you're enriching contacts in bulk, check regional distribution first and apply the strictest relevant regulation
  • Keep a log of where enriched data came from (which provider, when) for audit purposes

Data quality scoring

After enrichment, score your data quality:

FieldQuality levelAction
Email verified + deliverableHighReady for outreach
Email found but unverifiedMediumRun through verification tool (NeverBounce, ZeroBounce) before sending
Email not foundLowTry alternate enrichment provider or find via LinkedIn/company website
Phone — direct/mobileHighReady for calling
Phone — HQ/switchboardLowNot useful for cold calling — try to find direct line

Step 4 — CRM data hygiene

For stale data identification, deduplication strategy, enrichment schedules, and ongoing data quality automation, use /sales-data-hygiene. That skill covers record matching, merge rules, audit trails, and refresh cadences in detail.

Key rule: Always deduplicate before enriching — don't pay to enrich the same person twice.

Step 5 — Credit optimization

Credit-saving strategies

  • Enrich only qualified records: Apply ICP filters before enriching — don't waste credits on bad-fit contacts
  • Check existing data first: Skip records that already have the data you need
  • Prioritize email over phone: Email credits are typically cheaper. Only reveal phone numbers for contacts you'll actually call.
  • Use waterfall strategically: Start with the cheapest provider, escalate to premium for high-value targets
  • Batch over real-time: Bulk enrichment is often more credit-efficient than one-at-a-time
  • Monitor usage weekly: Set up alerts when you hit 80% of monthly credit budget

For platform-specific credit economics, see the relevant platform skill (/sales-apollo, /sales-zoominfo, /sales-clay, etc.) or references/platforms.md.

Gotchas

  • Don't enrich before deduplicating. Claude often recommends "enrich everything, then clean up." This wastes credits on duplicate records. Always dedup first, then enrich the clean list.
  • Don't assume enriched emails are deliverable. Enrichment tools find email addresses — they don't guarantee deliverability. Always run enriched emails through a verification tool (NeverBounce, ZeroBounce, MillionVerifier) before high-volume campaigns. Apollo-reported "verified" emails still bounce at 5-10% rates.
  • Don't enrich an entire CRM database at once. Claude tends to suggest bulk-enriching everything. This burns through credits fast and enriches records you may never contact. Start with your highest-priority segments and expand.
  • Don't ignore phone number credit costs. Mobile number reveals are 5-10x more expensive than email reveals in most tools. Only reveal phone numbers for contacts your team will actually call — not the entire list.
  • Don't set up auto-enrichment without a credit budget cap. Auto-enrichment can burn through an entire month's credits in days if configured too broadly. Set a monthly cap and limit auto-enrichment to new records matching your ICP.
  • Don't enrich contacts without checking regional compliance. Enriching EU contacts without a lawful basis for processing (GDPR), or emailing US contacts without an unsubscribe link (CAN-SPAM), exposes you to legal risk. See the compliance checklist in Step 3 before enriching in bulk.
  • Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Before recommending a specific platform skill

This skill covers a strategy domain across many platforms. Before pointing the user to any specific platform skill (any /sales-{platform} listed in ## Related skills, e.g., /sales-mailshake, /sales-klaviyo, /sales-apollo), read that platform skill's actual SKILL.md first. The 1-line description in ## Related skills is enough to *identify* a candidate — it's not enough to *commit* to it or to write a prompt that invokes it well.

How to read it:

  • If ~/.claude/skills/{skill-name}/SKILL.md exists locally, Read it.
  • For sales-* skills, WebFetch directly from this repo: https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md — e.g., for sales-mailshake: https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md.
  • For non-sales-* skills (third-party), look up {org}/{repo} in ~/.claude/skills/sales-do/references/skill-sources.md if installed and fetch the same skills/{skill-name}/SKILL.md path under that repo.

After reading, ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its argument-hint shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's argument-hint. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.

Related skills

  • /sales-prospect-list — Build the prospect list that you'll then enrich
  • /sales-intent — Layer buying signals on enriched contacts to prioritize outreach
  • /sales-cadence — Design the outbound sequence for enriched contacts
  • /sales-data-hygiene — CRM data quality, deduplication, enrichment automation
  • /sales-apollo — Apollo.io platform help (enrichment settings, credit management)
  • /sales-clay — Clay platform help (waterfall enrichment across 150+ providers)
  • /sales-zoominfo — ZoomInfo platform help (enrichment, intent, OperationsOS)
  • /sales-clearbit — Clearbit / Breeze Intelligence platform help
  • /sales-hunter — Hunter.io (Domain Search, Email Finder, Email Verifier)
  • /sales-seamless — Seamless.AI (1.8B+ contacts, CRM Enrich, Autopilot)
  • /sales-snov — Snov.io (email finder, verifier, multichannel campaigns)
  • /sales-brandjet — BrandJet AI platform help — multi-channel outreach, brand intelligence, AI monitoring
  • /sales-sendr — Sendr platform help (Data Studio enrichment, Lead Finder 479M+ contacts, personality analysis)
  • /sales-leadiq — LeadIQ platform help (Chrome extension prospecting, champion tracking, CRM enrichment, GraphQL API)
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill

Examples

Example 1: Pre-campaign enrichment

User says: "I have 500 contacts for a campaign but only 60% have emails. Enrich the rest." Skill does:

  1. Recommends deduping the list first
  2. Filters to records missing emails
  3. Sets up batch enrichment in Apollo with email-only scope (save phone credits)
  4. Recommends email verification before launching the sequence Result: List enriched to 85%+ email coverage, verified and ready for outreach

Example 2: CRM data cleanup

User says: "Our Salesforce has 50,000 contacts but half the data is stale. Help me clean it up." Skill does:

  1. Identifies stale data patterns (bounced emails, outdated titles, missing fields)
  2. Recommends a phased approach: dedup → prioritize top segments → enrich in batches
  3. Sets up an ongoing enrichment schedule to prevent future staleness
  4. Calculates credit budget for the cleanup Result: Phased CRM hygiene plan with credit-conscious enrichment strategy

Troubleshooting

Low enrichment match rate

Cause: Prospects are in niche industries, use uncommon email domains, or are very senior (C-suite data is harder to find) Solution: Try waterfall enrichment across multiple providers. For C-suite, try LinkedIn manual lookup or ask for referral introductions instead of cold outreach.

Enriched emails bouncing

Cause: Data provider has stale records, or person recently changed jobs Solution: Run enriched emails through a dedicated verification service before sending. Set up a feedback loop — when emails bounce, re-enrich or remove the contact.

Credits running out mid-month

Cause: Over-enrichment (enriching too many records or enriching phone numbers unnecessarily) Solution: Review usage in Settings > Usage. Restrict enrichment to ICP-qualified records only. Limit phone reveals to contacts tagged for calling. Consider upgrading plan if consistently hitting limits.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

39.15%
按下载量换算219

Claude

31.41%
按下载量换算176

Cursor

16.91%
按下载量换算95

Gemini CLI

10.17%
按下载量换算57

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills