Capabilities
Use the skill as a deliberate sequence: define the prospecting question, inspect the business-email evidence available to your runtime, and pass only a reviewed record into the next sales operation.
Begin with an ICP, named account context, buyer role, geography, exclusion rules, and a clear reason for checking an address. This keeps a finder request from becoming an unbounded search for personal or irrelevant contact data. A RevOps owner can define acceptable evidence, freshness expectations, and the handoff destination before an agent starts.
Business email discovery should retain the company domain and role context that produced a candidate. Similar names, acquired domains, and outdated directories are common sources of error. ZeroBounce-style workflow output should therefore label proposed data as context-dependent and expose unknown fields instead of quietly filling them with assumptions.
Syntax, domain behavior, and validation signals can inform a decision, but they do not establish consent, relevance, or inbox placement. Keep the result beside the time of check, source conditions, and suppression requirements. That record helps an SDR manager distinguish a usable research lead from a record that needs a different channel or more review.
Human-in-the-loop review is the final capability, not a ceremonial afterthought. Confirm that the account belongs in the campaign, that a message has a legitimate purpose, and that unsubscribe and regional obligations are handled. The agent can prepare an auditable packet; a responsible operator decides whether to contact anyone.
Copy the command, run it in a controlled environment, and inspect a first result before extending the workflow.
npx -y @okki-global/okki-go-taroball