Developer principles
The operating idea is simple: a prospecting agent should preserve the request, surface uncertainty, expose connection boundaries, and stop at a meaningful human decision point.
npx -y @okki-global/okki-go-taroballThen review the package output, requested permissions, and local configuration before using production data.
Method over marketing
This table is a framework for evaluation, not a scorecard. It avoids unverified vendor claims and shows what a technical or operations reviewer should investigate as of 2 September 2026.
| Evaluation dimension | Agent-native skill | Centralized seat SaaS | What to verify |
|---|---|---|---|
| Working context | Runs inside a chosen agent environment. | Runs in a vendor-controlled application. | Identity, logging, workspace isolation, and admin visibility. |
| Task model | Natural-language brief translated into tool actions. | Standardized UI objects and configured sequences. | Repeatability, field validation, and exception handling. |
| Data model | Depends on configured tools and providers. | May bundle proprietary and partner data. | Provenance, recency, coverage, rate limits, and export rights. |
| Human control | Can place review directly between research and export. | May use approval steps, permissions, or campaign controls. | Whether a user can inspect and stop each consequential action. |
| Cost visibility | Package, runtime, and provider costs may be separate. | Seats, usage, data, and add-ons may be bundled. | Current public terms or a written quote; do not infer pricing. |
| Security disclosure | Requires package and runtime review. | Requires vendor, tenant, and integration review. | Published documentation, contractual controls, and actual configuration. |
Unknown means unknown. If a public source does not confirm a capability, control, price, or certification, keep the field unresolved until evidence is available.
A result is an argument
OKKI Go output should help someone answer three questions: What was requested? What evidence supports this item? What remains unresolved? That structure is more durable than a long list with no visible selection logic.
The illustrative trace does not imply access to any specific database. Your configured provider and runtime determine which fields can be researched and how they may be used.
Named market, role, constraints, exclusions, and required evidence.
Source type, checked context, field conflicts, and missing information.
Accept, reject, or investigate further with a written reason.
Export only approved fields to a destination with an explicit owner.
Engineering posture
Connect only the sources and destinations required for a defined workflow. Prefer scoped keys, separate environments, and revocable credentials. Never place API keys in prompts, sample results, or repository files.
A matched company, professional role, or contact channel should retain enough context for a reviewer to understand its origin and recency. Waterfall enrichment can expand coverage, but it also increases the need for field-level attribution.
Company research and message preparation can be assisted while send, write-back, deletion, and bulk export remain controlled decisions. Human-in-the-loop should be a visible workflow state, not a vague policy statement.
Rate limits, missing fields, stale evidence, provider errors, and permission problems should not silently become fabricated certainty. Preserve the error, explain the impact, and give the operator a safe recovery path.
Review the package in your environment
Copy the command, run it in a controlled terminal, configure the minimum required credentials, and validate a deliberately small first result. Update or uninstall through the package/runtime process you have reviewed; do not assume a copied command changed your system.
npx -y @okki-global/okki-go-taroball