Terminal
Terminal/Skill
Adds validated firmographics such as industry, headcount, revenue and HQ to a list of company domains or names, marking unknowns as unknown.
By Clay
Works with
npx skills add clay-run/clay-skill-creator --skill enrich-account-listThe insight: the enrichment call is the easy 10% — identity before it and
interpretation after it decide whether the output is intelligence or noise.
Enrichment matches an ENTITY, not a live business: a stale domain enriches fine on
last-known data, a wrong domain enriches a stranger, and the payload lies politely —
headcount arrives as a band string that parses to garbage in comparisons, and
missing fields read as empty rather than unknown. So this skill validates identity
first on every row (never trusting CRM fields that "look populated"), enriches once
per unique domain, and normalizes the output into values a formula can trust —
with unknown as a first-class state, never a silent zero.
Nothing here ships with a value. Each one is the installer's, not the author's: ask for it, never substitute a plausible default, and where an answer does not exist say which step becomes unavailable rather than guessing. Where a default IS defensible it is named below, and using it means saying so in the output.
| Input | What the installer supplies | If it is missing |
|---|---|---|
| The list | a CSV or CRM export with at least one domain or company-name column | no default. Existing industry and headcount columns are stale claims, kept as reference only |
| The fields they need | industry, headcount, revenue, HQ country, founded | ask. Tech stack, signals and scores belong to named sibling skills — say so rather than swelling scope |
| Cost ceiling | credits | dedupe to unique domains first, state lookups × declared cost plus resolution for name-only rows, then wait |
If an answer sheet is present beside this skill, load it and ask only for what it does not cover. A partial sheet is normal; a value it is missing gets asked for on its own rather than restarting the interview. Say which values came from the sheet before using them — a sheet applied silently is a wrong field nobody catches. If there is no sheet, say nothing about sheets — the check is a file lookup, not a question, so run the interview as though the feature did not exist rather than reporting an absence. At delivery, offer to save the answers back (identifiers only — never a token or a password), private and never published — and phrase the offer so it explains itself: "want me to save your answers to a file, so the next person on your team doesn't have to answer these again?"
Run clay whoami; echo "exit_code=$?". If it fails or Clay tools are missing, run
the Clay plugin's setup skill, restart if it says to, and re-run this skill. Tell
the user which workspace you're in. Confirm the managed Enrich Company function
exists (clay routines get) and read its declared cost.
resolved rows proceed; ambiguous/not_found/acquired rows land in the
output with that status — never enriched on a guess).status: dead-domain — and remember the
trap the hard way taught: a dead or acquired company still enriches fine on
last-known data; enrichment presence is never liveness evidence. Never skip
identity because CRM fields look populated — they are frequently stale, wrong,
or redirected.Managed Enrich Company (Company Identifier → record, ~1 credit/domain), CLI
envelope + gating rules in references/enrichment-mechanics.md. Gate on actual
payload values, never run status (complete + empty is the routine miss shape) — an
empty payload is an honest not_enriched row, not a retry loop.
unknown, visibly. Never let a band
string touch a numeric comparison (parseInt reads it as 1, silently).unknown, a first-class
value downstream formulas must handle; a row of unknowns is still an enriched
identity.website (never its
domain field, which can echo a link-shortener) should agree with the input
domain — a mismatch flags possible wrong-entity resolution, routed to review,
never silently kept.One row per unique company: input identity · resolved/validated domain · status (enriched / not_enriched / dead-domain / ambiguous / acquired) · industry · headcount band + ordinal · revenue · HQ country · founded · enriched-at · identity-mismatch flag, joined back to the input rows (contacts inherit their
account's enrichment). Summary: rows in, unique companies, enriched %, honest
not-founds, unknowns per field, credits measured vs declared. Every input row lands
somewhere — silent drops are the cardinal sin.
not_enriched.Ask: "Enrich our 120-row account export — industry, size, revenue."
Identity: 120 rows → 74 unique companies (46 duplicate-account rows join back
later); 61 have domains, 13 name-only → resolver handoff returns 9 resolved, 2
ambiguous, 1 not_found, 1 acquired (flagged, not enriched). Liveness screen kills 2
dead domains free. Cost stated: 68 enrichments × ~1 credit, approved. Enrichment:
64 return payloads; 4 come back empty → not_enriched. Normalization: 61 industries
fill; headcount bands parse on 58 (6 unknowns visible); one payload's website
disagrees with the input domain → identity-mismatch flag for review. Delivered: 74
company rows joined to 120 input rows · 64 enriched · honest states on the rest ·
68 credits measured vs 68 declared.