prospect-enrich
Mon-Fri 6:00 AM — Daily batch enrichment of phoneless contacts using Apollo + Clay. DEMO REQUEST first, then ATL-first priority. Golden Rules + ATL/BTL Classification Gate. Feeds into phone-waterfall and prospect-refresh.
What this skill does
# Prospect Enrich Skill
<objective>
Enrich HubSpot contacts missing phone numbers using Apollo and Clay APIs. Apply DEMO REQUEST priority (hand-raisers first), then ATL-first prioritization and Golden Rules (exclude customers, channel, device owners, AE-owned contacts). Output branded HTML report sorted by tier and ready for phone-waterfall and prospect-refresh tasks.
</objective>
<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>
<workflow>
## 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]`
2. **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 Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.