Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问许可证需确认审计提醒

prospect-enrich前景丰富

Agent Skill

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

总安装

285

周安装

12

GitHub Stars

12

下载量

1
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

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

简介

prospect-enrich 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于需要根据关键词或任务场景进行信息搜索与筛选的研究检索场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前建议确认权限范围、维护状态及是否涉及联网或文件操作。
  • 具体用法可参考原始 README 和 SKILL.md 文档进一步核验。

SKILL.md

Prospect Enrich Skill

<quick_start> Trigger: Mon-Fri 6:00 AM ET Manual Trigger: "Run prospect enrich" or "Enrich phoneless contacts" Dependencies: Requires HubSpot portal 21530819 access, Apollo credits, Clay credits Output: Branded HTML report + enriched contacts synced to HubSpot with tier tags </quick_start>

<success_criteria>

  • Query HubSpot for all contacts with phone = null (geo: USA/Canada only)
  • Filter out Golden Rule exclusions (customers, channel, device owners, AE-owned, product-page engagers)
  • Identify DEMO REQUEST contacts (first_conversion contains demo/pricing keywords) — enrich FIRST
  • Classify remaining by ATL/BTL tier (see CLAUDE.md ATL/BTL Decision-Maker rules)
  • Batch enrich via Apollo (apollo_people_bulk_match or apollo:enrich-lead)
  • For Apollo misses: send to Clay waterfall (find-and-enrich-contacts-at-company)
  • Sync enriched phone numbers back to HubSpot with tier tags
  • Include company enrichment (domain, revenue, headcount) for ATL-tier contacts
  • Generate branded HTML report with tier sections and Epiphan colors
  • Report: total contacts processed, phone match rate %, ATL/BTL breakdown, credits used </success_criteria>

Stage 1: Pull Phoneless Contacts from HubSpot

MCP Tool: search_crm_objects (HubSpot)

objectType: "contacts"
filterGroups: [{
  filters: [
    { propertyName: "phone", operator: "NOT_HAS_PROPERTY" },
    { propertyName: "hs_lead_status", operator: "IN", values: ["Subscriber", "Qualified Lead", "Inbound Lead", "Marketing Qualified Lead", "Sales Qualified Lead"] }
  ]
}]
properties: [
  "firstname", "lastname", "email", "company", "jobtitle", "phone",
  "first_conversion", "lifecyclestage", "hubspot_owner_id",
  "device_count", "engagement_overview", "is_channel"
]
limit: 100

Output: List of contacts with name, email, company, title, first_conversion; no phone.


Stage 2: Apply Golden Rules Filter

Golden Rules (Hard Exclusions — apply BEFORE enrichment to save credits):

  • EXCLUDE: lifecyclestage = 'customer' (existing customer)
  • EXCLUDE: device_count >= 1 (device owner)
  • EXCLUDE: engagement_overview contains product usage (product-only engager)
  • EXCLUDE: is_channel = true (channel partner)
  • AE-OWNED (90-Day Stale Exception): hubspot_owner_id IN (82625923, 423155215, 190030668)

- If hs_lastmodifieddate > 90 days ago → KEEP but tag as STALE AE LEAD with ATL/BTL tier + deal value. Tim reviews. - Ron Epstein (423155215): 90-day rule applies to ALL leads - Lex Evans (82625923) & Phillip Sandler (190030668): 90-day rule applies to NA contacts only (USA/Canada). Non-NA → still exclude. - If last activity < 90 days → EXCLUDE (AE actively working)

  • EXCLUDE: first_conversion ILIKE '%setup%' — product setup forms only (not sales interest)
  • Keep: Geo filter to USA/Canada only

⚠️ CRITICAL — DO NOT EXCLUDE these first_conversion values:

  • 'Pearl family demo', 'Demo signup', 'demo request'
  • 'General contact us', 'pricing'
  • 'Pearl', 'Connect', 'signup'

These are HIGH-INTENT demo requests — active hand-raisers. Tag them as DEMO REQUEST tier and enrich BEFORE all other tiers.

Output: Filtered list (typically 60-70% of input after Golden Rules)


Stage 3: ATL/BTL Classification Gate (MANDATORY)

Apply BEFORE enrichment to set processing priority order.

Reference: CLAUDE.md § ATL/BTL Decision-Maker Classification v1.0

Tier 1: DEMO REQUEST (Enrich FIRST — Highest Priority)

Any contact whose first_conversion contains:

  • 'Demo signup', 'Pearl family demo', 'demo request'
  • 'General contact us', 'pricing'

These are active hand-raisers — enrich immediately regardless of job title.

Tier 2: ATL (Enrich Second — Budget Authority)

Chief (CIO, CTO, CFO, COO) • Vice President (VP, AVP, SVP, EVP) • President • Provost • Vice Provost • Superintendent • Director (of IT, Technology, Facilities, Academic Technology, Procurement, Materials Mgmt, Medical Education, Court Administration) • Dean • Court Administrator • Clerk of Court (Federal) • City Manager • County Manager • Senior Pastor • Executive Pastor

Tier 3: GRAY (Enrich Third — Flag for Tim's Review)

  • Manager (AV/Facilities/IT) — ATL only if reports to Director+ AND has delegated budget authority >$25K
  • Department Chair — ATL at small institutions; BTL at large universities
  • Director of Educational Technology — depends on reporting line (Provost = ATL; IT VP = maybe BTL)
  • Program Director — ATL only if department-level budget holder; BTL if coordination role

Tier 4: BTL (Enrich Last — Deprioritize)

Technician • Specialist • Coordinator • Support • Administrator (Systems/Network/Database) • Engineer (AV/Network/Systems) • Operator • Instructor/Professor/Faculty • Designer (Learning/Instructional/Graphic) • Assistant • Clerk (non-Court Admin) • Volunteer • Intern • Student • Resident • Help Desk

NEVER ENRICH (Hard Skip — Do NOT Spend Apollo/Clay Credits)

Warehouse Manager • Network Manager • Systems Administrator • AV Technician • Graphic Design Instructor • Program Administrator • Web Designer • Classroom Support • Lab Coordinator • Maintenance • Building Engineer • Multimedia Services Manager • Video Production Specialist • Streaming Crew

Classification Logic:

if first_conversion matches DEMO_KEYWORDS:
  tier = "DEMO REQUEST"  # Enrich first, regardless of title
elif title in NEVER_ENRICH:
  tier = "NEVER"  # Hard skip — do not spend credits
elif title in ATL:
  tier = "ATL"
elif title in GRAY:
  tier = "GRAY"  # Flag for Tim's manual review
else:
  tier = "BTL"

# Processing order: DEMO REQUEST → ATL → GRAY → BTL (skip NEVER)

Stage 4: Batch Enrich via Apollo

Process contacts in tier priority order: DEMO REQUEST → ATL → GRAY → BTL

MCP Tool: apollo_people_bulk_match (or apollo:enrich-lead skill)

details: [
  {
    id: contact.id,
    first_name: contact.firstname,
    last_name: contact.lastname,
    email: contact.email,
    organization_name: contact.company,
    domain: extract domain from email or company website
  }
  ... (up to 10 per batch)
]
reveal_personal_emails: false

Expected Enrichment:

  • phone (direct, mobile, corporate)
  • current_role_min_months_since_start_date (tenure for seniority signal)
  • person_seniorities (c_suite, vp, director, manager, etc.)

Match Rate Target: 65-75% of batch should get phone.


Stage 5: Waterfall Misses to Clay

For Apollo non-matches: Send to Clay find-and-enrich-contacts-at-company

MCP Tool: find-and-enrich-contacts-at-company

companyIdentifier: contact.company (domain preferred)
contactFilters: {
  job_title_keywords: [extract broad role from contact.jobtitle],
  locations: ["United States", "Canada"]
}
dataPoints: {
  contactDataPoints: [{ type: "Email" }],
  companyDataPoints: [{ type: "Latest Funding" }, { type: "Tech Stack" }]
}

Clay Enrichment: Return matching contacts at company with email + company data.


Stage 6: Sync Back to HubSpot

For each enriched contact:

  1. Update HubSpot contact via manage_crm_objects (updateRequest):

- phone (direct or mobile from Apollo/Clay) - hs_analytics_num_page_views (engagement signal) - Tag in notes: [DEMO REQUEST], [ATL], [GRAY], or [BTL]

  1. Enrich company data if not already set:

- MCP Tool: apollo_organizations_enrich - Update HubSpot company: revenue, headcount, founded_date


Stage 7: Generate Branded HTML Report

Output: HTML file saved to workspace as bdr-v3-prospect-enrich-YYYY-MM-DD.html

Styling:

  • Epiphan brand colors: #1a1a2e (dark), #e94560 (accent), #0f3460 (primary)
  • Clean, professional layout
  • Mobile-responsive design

Report Sections:

Summary Metrics Table:

MetricValue
Total phoneless poolX
After Golden Rules filterY (Z% removed)
DEMO REQUEST tierD
ATL tierA
GRAY tierG
BTL tierB
NEVER tier (skipped)N
Phones found (Apollo)PA (PA% of processed)
Phones found (Clay)PC (PC% of non-Apollo)
Total enrichedPA + PC (success %)
Apollo credits usedC

Section 1: DEMO REQUEST Contacts (Green highlight) Sorted first — these are hand-raisers with highest conversion potential.

ContactEmailTitleCompanyPhoneFirst ConversionRevenueAction
...............Demo signup...Priority dial

Section 2: ATL Contacts (Blue highlight) Budget decision-makers — second priority.

Section 3: GRAY Contacts (Yellow highlight) Flagged for Tim's manual review — budget authority uncertain.

Section 4: BTL Contacts (Gray) No budget authority — lowest enrichment priority.

Section 5: NEVER ENRICH Skipped List Contacts that matched NEVER ENRICH titles — credits NOT spent.

Section 6: Key Insights + Recommended Actions

  • Top companies by ATL density
  • Highest-value DEMO REQUESTs
  • Recommended next steps

Stage 8: Emit Outcome Sidecar As the final step, write the following JSON to ~/.claude/skill-analytics/last-outcome-prospect-enrich.json:

{"ts":"[current UTC ISO8601]","skill":"prospect-enrich","version":"1.1.0","variant":"default",
 "status":"[success|partial|error]","runtime_ms":[estimated ms from start],
 "metrics":{"contacts_processed":[Stage 1 total],"phones_found":[Apollo+Clay hits],
 "phone_match_rate_pct":[phones/contacts*100],"atl_count":[ATL tier],"demo_request_count":[DEMO tier],
 "credits_used":[Apollo batch count]},"error":null,"session_id":"[date YYYY-MM-DD]"}

Use status "partial" if some stages failed but results were produced. Use "error" only if no output was generated. Do not include contact names or emails in any field.

Next Steps: Results feed into phone-verification-waterfall-skill for phoneless re-check and prospect-refresh-skill for net-new ICP search.


Skill Metadata

Version: 1.1 Last Updated: 2026-03-19 Author: Tim Kipper Status: Production Integration: HubSpot (portal 21530819) + Apollo + Clay Tier: P1 (Core BDR Automation) Triggers: Scheduled (Mon-Fri 6:00 AM) + Manual ("Run prospect enrich") Changelog:

  • v1.1 (2026-03-19): Added DEMO REQUEST tier (highest priority), AE owner exclusion (IDs 82625923, 423155215), first_conversion filter logic, HTML report output with Epiphan brand colors. Schedule expanded Mon-Fri (was Mon only).
  • v1.0 (2026-03-19): Initial release with ATL/BTL classification, Apollo + Clay waterfall.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

35.75%
按下载量换算0

Claude

32.37%
按下载量换算0

Cursor

17.14%
按下载量换算0

Gemini CLI

8.51%
按下载量换算0

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

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

来源信息

继续浏览同类 Skills