← UnifyCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Unify
Snapshot Sep 30, 2026 · 23:07 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "enrichment",
"description": "Enrichment with Unify; find work emails, phone numbers, firmographics, funding, technographics, job postings, and fresh employment data for known companies or people. Use when the user has specific entities (names, domains, LinkedIn URLs, a DataTable, CRM records) and needs more data on them, including email verification before outreach.",
"included_files": [],
"skill_md_contents": "---\nname: enrichment\ndescription: Enrichment with Unify; find work emails, phone numbers, firmographics, funding, technographics, job postings, and fresh employment data for known companies or people. Use when the user has specific entities (names, domains, LinkedIn URLs, a DataTable, CRM records) and needs more data on them, including email verification before outreach.\n---\n\n# Enrichment: adding data to known entities\n\nEnrichment briefs go through `run_agent` (see `agent-runs`). Unify runs managed\nprovider waterfalls internally. Never ask it to use a specific email vendor;\ndescribe the outcome.\n\n## Identifying entities in a brief\n\nGive the strongest identity keys you have, per entity:\n\n- Person: LinkedIn URL/slug, or first + last name + company domain, or email.\n- Company: domain (best), or LinkedIn URL, or exact name + disambiguator.\n- Bulk: reference an existing DataTable by ID (\"enrich every row of table <uuid>\n with work emails\") or paste a short list.\n\n## What to ask for\n\n- **Work emails**: found via a managed multi-provider waterfall and returned with\n validation status. Only `valid` (and cautiously `catch-all`) emails are safe to\n send to; ask for \"verified emails\" when outreach is the goal. Personal email\n coverage is not offered.\n- **Phone numbers**: mobile/direct dials via a phone waterfall; lower hit rates\n than email. Set expectations with the user.\n- **Company data**: firmographics come free from Universal Data first; funding\n rounds, job postings/hiring intent, technographics (web-detectable and\n backend/inferred), news, ad activity, web traffic come from paid vendors.\n- **Employment validation**: \"confirm these contacts still work at these\n companies\" (checks current employer and can refresh stale LinkedIn data).\n\n## Cost control\n\nContact-data and vendor enrichment cost credits per record. In bulk briefs, state\na cap: \"cap credit spend at N\", \"email only, skip phones\", or \"free sources only,\nmark the gaps\". Expect the agent to pause with a clarification question when a\nbrief implies large spend; answer or relay it (see `agent-runs`).\n\n## Patterns\n\n- **Enrich-then-engage**: enrich and verify emails *before* any outreach brief;\n the Unify agent itself refuses to write outreach on thin prospect context.\n- **Scout before scale**: for 100+ rows, enrich 5 first, review the hit rate with\n the user, then run the remainder.\n- Results append columns to a DataTable; page with `load_datatable`.\n"
}SHA-256: b8dfe8d3fb1394a1d1a567bd84b20ae680562322e38e6096ad5054c76a9b39fd