Inspect package
Review what the npx command executes and where the runtime places skill files.
Agent integrations
Agent-native prospecting works best when runtime compatibility, secret ownership, task inputs, and output destinations are explicit from the start.

Compatibility route
Review what the npx command executes and where the runtime places skill files.
Use a supported agent environment with a local terminal and visible package output.
Grant only the read or write permissions required by the declared task.
Test sample output and human approval behavior before production records move.
Architecture
ICP rules, exclusions, desired fields, and jurisdictional constraints arrive as an intelligible task definition.
Structured by operatorAPI keys remain in runtime secret storage and should never be interpolated into prompts or result files.
Least privilegeAccount fit, contact confidence, personalization, and any external action remain separately approvable.
Human in the loopApproved records map to a declared schema so exports and CRM updates do not invent unsupported fields.
Config-dependentIntegration classes
Local environments capable of invoking npx and exposing package execution output to the operator.
Operator-approved providers used according to their contracts, permitted fields, and regional restrictions.
Runtime or operating-system facilities that keep connector credentials outside prompts and repositories.
CRMs, tables, or files reached only through a configured adapter and an explicit human-approved handoff.
Copy the command without a shell prompt, run it in your chosen agent environment, and review each requested permission.