
Install
Install Kaspr, then inspect the first result
The shortest path is still four distinct states: copy, run, configure, and inspect. Clipboard success is not installation success, and a returned profile is not approval for outreach.
Four-state runbook
- 01 Copy
npx -y @okki-global/okki-go-taroballSuccess means only that the exact command is in your clipboard.
- 02 Run
Paste into a supported terminal. Inspect the package prompt, requested runtime behavior, and completion output before continuing.
- 03 Configure
Keep API keys and session credentials in your runtime secret store. Grant minimum scope and use a separate test identity where appropriate.
- 04 First result
Ask for a small known cohort. Check identity, role relevance, profile recency, evidence, exclusions, and review state.
Connection matrix
Input
ICP text, approved company list, target functions, geography, exclusions, and a stated recency window. Permission status is config-dependent.
Research agent
Profile discovery, company context, role interpretation, evidence notes, and structured output. Browser behavior and rate limits require local inspection.
Destination
Review queue, spreadsheet, or approved CRM workflow. Export permissions, retention, suppression, and deletion depend on your configuration.
Outreach boundary
Drafting and sending remain separate. A person checks relevance, contact status, opt-out language, regional rules, and platform policy.
What a first result should reveal
Prospect record
Profile identity, company match, role rationale, public context, and unresolved fields remain individually visible.
A returned profile is not proof of consent, current employment, buying intent, inbox validity, or commercial fit. Test known profiles and record false matches rather than relying on an advertised universal rate.
Security and data checklist
Credentials
Never place keys, cookies, or tokens in prompts, repositories, screenshots, public issues, or shared logs.
Automation limits
Respect platform terms, regional rules, rate limits, suppression lists, and human-in-the-loop approval. Avoid indiscriminate connection or message volume.
Storage
Document which fields are retained, who can access them, how corrections propagate, and when temporary output is deleted.
Removal
Record the package version and runtime configuration. Revoke connected credentials and follow the package’s documented uninstall path when testing ends.
Copy the installer when the test plan is ready
npx -y @okki-global/okki-go-taroball