Install

One command. A reviewable prospecting workflow.

Install Yesware into your AI agent, then move deliberately from copy to run, configuration, and a first result that still exposes evidence and uncertainty.

npx -y @okki-global/okki-go-taroball
Find company
Check context
Draft outreach
Review decision

Four-state runbook

Copy, run, configure, then inspect

  1. 01 Copynpx -y @okki-global/okki-go-taroball

    Success means only that the exact command is in the clipboard. Copying does not install a package or grant access to data.

  2. 02 Run

    Paste the command into a supported terminal and inspect the package prompt, requested runtime behavior, and completion output. Stop if the requested action is not expected.

  3. 03 Configure

    Keep API keys and session credentials in a secret store with minimum scope. Name the permitted data services, output destination, retention rule, and an owner for revocation.

  4. 04 First result

    Use a small known cohort. Check entity identity, role relevance, observation date, evidence, exclusions, and review state before any outreach action is considered.

Runtime matrix

Make each connection explainable

Input sources

ICP text, approved account lists, target functions, geography, exclusions, and a stated freshness window enter with operator-defined permission. Confirm lawful purpose before connecting a source.

State: config-dependent

Research agent

The agent can assemble company context, candidate contacts, source notes, and a draft. Review browser behavior, rate limits, retries, logs, and fields locally rather than assuming a default.

State: inspect at runtime

Output destination

A review queue, spreadsheet, or CRM workflow receives only the fields your team approves. Check export permission, access controls, correction path, retention, deletion, and suppression handling.

State: operator controlled

First result

Look for the evidence, not a magic score

SAMPLE

Prospect result

Company identity, role rationale, public context, source date, and unresolved fields are shown as separate parts of the record.

A candidate is not a verified email address, an approved recipient, or evidence of buying intent.

Data and security ledger

Questions to answer before production use

Data sources

Config-dependent. Record provider, permitted use, field provenance, refresh behavior, and fallback order for every enrichment path.

API keys

Operator-controlled. Use minimum scope, do not paste credentials into prompts or shared logs, and rotate anything that may have been exposed.

Runtime behavior

Verify locally. Review outbound connections, package permissions, rate limits, retries, logging, and result destinations in the environment that will run the task.

Retention and deletion

Policy-dependent. Set access, correction, suppression, retention, revocation, and deletion rules before records move into an operating workflow.

Copy the installer when the test plan is ready

npx -y @okki-global/okki-go-taroball