Frame the market question
Record buyer role, company profile, territory, exclusions, and the business event that would count as a meaningful signal.
Agent-native prospecting · evidence first
Give your AI agent an ICP, a territory, and the evidence standard. The skill returns structured research with source context and review states, without forcing another seat-based workspace into your stack.
Copying is step one; you still run and configure the skill in your agent.
npx -y @okki-global/okki-go-taroball
Grouped specification ledger
The values below are evaluation requirements, not performance promises. Runtime behavior, provider coverage, and downstream retention must be checked in the environment where the skill runs.
Vertical verification timeline
Record buyer role, company profile, territory, exclusions, and the business event that would count as a meaningful signal.
Attach public evidence, retrieval timing, and provider-specific caveats so an analyst can distinguish an observed fact from an inferred match.
Use waterfall enrichment only where additional sources add value; preserve disagreement instead of silently treating a single source as ground truth.
Check suppression, sender reputation, message relevance, and applicable regional obligations before export, drafting, or any human-authorized send.
Six evidence controls
Separate required attributes, preferred signals, exclusions, and unknown fields.
Carry URLs and retrieval context beside each structured prospect record.
Label inference and provider disagreement for deliberate human resolution.
Query another source only when the expected evidence justifies cost and latency.
Keep audience choice, message approval, and send authority with a person.
Apply retention, suppression, and access policies before records leave the agent.
Four-state runbook
npx -y @okki-global/okki-go-taroballSuccess signal: the exact command is in your clipboard.
Paste the command into the terminal used by your supported AI-agent environment. Read the package prompt before allowing execution.
Success signal: the installer completes without a package or permission error.
Add only the provider credentials your chosen workflow requires. Keep keys in the runtime secret store; never paste them into prospecting prompts.
Success signal: the agent can enumerate the installed skill without exposing secrets.
Begin with a narrow ICP and request evidence fields. Review sources, uncertain matches, and exclusions before exporting or drafting outreach.
Success signal: a structured sample appears with reviewable provenance.
Install FAQ
It invokes the published installer through npx. Review terminal output, requested permissions, package provenance, and runtime policy before continuing.
No. Copy only places the exact text on your clipboard. You decide when and where to run it.
The recommended workflow keeps targeting, message approval, suppression, and send decisions under human control. Follow CAN-SPAM, CASL, GDPR, and other rules applicable to recipients and regions.
Use the agent runtime’s secret management mechanism, scope permissions narrowly, rotate credentials, and confirm deletion behavior for stored results.