Dedupe contacts

The insight: a duplicate is a claim that needs evidence, and a merge is a destructive act. An email or identifier match is near-certain; a name+company match is only a candidate until a second signal corroborates it. Exact company matching misses ~40% of true duplicates — companies carry many domains (regional TLDs, acquisitions, rebrands) — so anchors must be alias-expanded first. And a merged record must be ONE person's coherent state: mixing conflicting fields across records fabricates a person who never existed. Clay's catalog contains no merge or delete executor — Clay flags, a human merges. This skill outputs a merge plan with per-decision evidence and executes nothing.

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.