Terminal
Terminal/Skill
Finds a person's work phone number, ideally a validated mobile, and labels each number as mobile, direct-dial or HQ before any call.
By Clay
Works with
npx skills add clay-run/clay-skill-creator --skill find-work-phoneThe insight: phone is the most expensive and most regulated field in contact data — found is not the same as dialable. A mobile lookup costs ~5–10x an email lookup, and even a good waterfall validates a mobile for only about half of senior US contacts, less elsewhere — misses are normal. An HQ switchboard is not a direct line, and an unconsented call or text to a mobile carries legal risk (DNC registries, US TCPA, GDPR) that a cold email doesn't. So the find includes line-type validation, honest typing, and a compliance flag — never just "here's a number."
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 |
|---|---|---|
| A profile URL per contact | the professional profile, not just a name | this is a hard requirement, not a preference — the phone surface is keyed on the profile. A name-only row resolves the URL first and confirms it is the right person |
| A known email | if they have one | optional; raises the hit rate where accepted |
| The gate | which contacts they would actually call | ask before a batch. Phone credits are worth spending only on the right persona at a qualified company |
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 (or follow
https://raw.githubusercontent.com/clay-run/agent-plugins/main/GETTING_STARTED.md), restart
the agent if setup says to, and re-run this skill. Tell the user which workspace you're in.
Phone waterfalls are keyed on the professional profile, not the name: the managed phone functions require a LinkedIn URL (email waterfalls don't).
A known email raises the hit rate — pass it through if accepted. On a batch, gate first: phone credits only on contacts the user would actually call (right persona, qualified company).
Find the workspace's managed phone function (names vary — "Mobile Phone Number", or a
combined function returning email + phone) and confirm it's runnable: clay routines list
paginates and omits functions; clay functions list shows the catalog, but a listed
function can still be not enabled for API & CLI (clay routines get → not_found);
fall back to a table/workflow, or admin registration (clay routines create).
Check estimatedCreditCost before running — always. At ~10 credits per lookup, state
the total and get explicit approval. CLI envelope:
{"items":[{"id":"<key>","inputs":{...}}]} via --input -. Timing: hits return in
seconds; a real-person miss takes minutes (every provider tries, some bill anyway); an
unresolvable LinkedIn URL fails fast, before the waterfall starts. A batch finishes at the
speed and cost of its misses; hits resolve early, under the flat estimate.
Large or multi-region batches belong in a Clay table's native phone waterfall (provenance,
regional tuning), not a CLI loop.
status: complete while the item inside failed (unresolvable profile URL), or the item
completes empty (waterfall miss). Both are not-founds: gate on an actual number, never
on run status.HQ).Per person: name · company · phone (E.164) · type (mobile / direct-dial / HQ; flag VoIP) · status (valid / not found) plus what identified them. Batch runs add a summary: found %
by type, not found %, credits spent. Close with the compliance one-liner.
Ask: "Get me a mobile number for Priya Raman at brightloop.example."
URL on file → state ~10-credit cost, get approval → waterfall hits early →
+1-XXX-XXX-4821 · mobile · valid; offer the 0.2-credit status + litigator screen before
the call block.
Counter-example: an unresolvable profile URL fails fast (run still says complete) →
report not found; don't substitute the main line unless asked, then only labeled HQ.