Enrich an account list

The 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.

Declared inputs

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.