Companies & Contacts enrichment - Explorium AgentSource
PassAudited by ClawScan on May 10, 2026.
Overview
This skill is a disclosed Explorium AgentSource integration that uses a local CLI and API key to search/export B2B data, with privacy and credential-handling points users should understand.
This skill appears coherent and purpose-aligned for B2B company/contact enrichment. Before installing, be comfortable giving it an Explorium API key, sending selected search and matching data to Explorium, and storing result files locally under /tmp. Use explicit record limits, confirm credit-consuming enrichments/exports, and clean up temp files when done.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone with access to the key could use the Explorium account/API quota.
The skill requires a provider API key and can store it locally, which grants access to the user's Explorium account and possible API credits.
"required_credentials": [{ "name": "EXPLORIUM_API_KEY", ... "storage": "~/.agentsource/config.json (mode 600) or EXPLORIUM_API_KEY environment variable" }]Use an environment variable or the documented mode-600 config, do not paste the key into chat, and rotate the key if it is exposed.
Search criteria and any selected company/contact records used for matching may leave the local environment and be processed by Explorium.
The skill sends search filters, entity IDs, matching records, and optionally natural-language query text to the Explorium provider API.
All API calls go to `https://api.explorium.ai/v1/`... `Company/contact records for matching` ... `call_reasoning` ... `Only when --call-reasoning is passed (opt-in)`
Only use this skill with data you are allowed to send to Explorium, and only allow call_reasoning/query logging when you are comfortable sharing the query text.
Local temp files may contain prospect/contact data and may remain until the operating system removes them.
API responses are stored in local temporary JSON files, and enrichment can include contact details such as emails and phone numbers.
`/tmp/agentsource_*.json` | API result data | Cleaned up automatically by OS
Delete /tmp/agentsource_*.json files when no longer needed, especially on shared machines or when results contain contact information.
The agent may run API searches/enrichments and create exported files as part of the workflow, which may consume credits depending on the operation.
The agent is instructed to execute a local CLI that can fetch, enrich, and export data; this is central to the skill's function and is disclosed.
All API operations go through the `agentsource` CLI tool (`agentsource.py`). The CLI calls the AgentSource REST API at `https://api.explorium.ai/v1/`.
Review previews and confirmation prompts before enrichment or large exports, and set explicit limits for record counts and output paths.
Installation changes the local home directory by adding a persistent CLI file, though no downloads or hidden dependencies are shown.
The manual setup script installs the included CLI into the user's home directory, while the registry install spec says this is an instruction-only skill.
cp "$PLUGIN_DIR/bin/agentsource.py" "$BIN_DIR/agentsource.py" ... chmod +x "$BIN_DIR/agentsource.py"
Run setup only from the reviewed package directory and remove ~/.agentsource if you no longer want the CLI or saved configuration.
