Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
DataHub for Any Data
v0.1.1Call any data interface through natural language with DataHub API. Supports async querying, result polling, API supply addition, and data bounties. Use when:...
⭐ 0· 56·0 current·0 all-time
by@xplore3
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
medium confidencePurpose & Capability
SKILL.md and the included scripts clearly implement a DataHub client that needs a DATAHUB_API_KEY and reads user/project config files (e.g., ~/.datahub/config.json, .datahub.json, datahub.config.json). The registry metadata declares no required env vars or config paths — this mismatch is an incoherence that should be resolved before trusting the skill.
Instruction Scope
Runtime instructions are limited to submitting queries and polling results (node scripts). The scripts do read config files from the user's home and current working directory to obtain the API key; they otherwise only perform network calls to the DataHub host. There is no instruction to read arbitrary user files or exfiltrate unrelated secrets, but the skill will access local config files that may contain credentials.
Install Mechanism
No install spec — this is instruction-only with included Node scripts. Nothing is downloaded at install time. This has lower install risk; the included scripts are static and their behavior can be reviewed locally.
Credentials
Although the functionality legitimately requires a DataHub API key, the registry did not declare any required environment variables or primary credential. The scripts accept the key via DATAHUB_API_KEY or config files. The implementation also places the key in request body, header, and (for polling) in URL query parameters — increasing risk of accidental leakage via logs, referers, or intermediary proxies. The number and placement of secrets handling should be disclosed in metadata.
Persistence & Privilege
The skill does not request persistent, always-on privileges (always: false). It does not modify other skills or system-wide settings. It only reads its own expected config files for the API key.
What to consider before installing
What to consider before installing:
- The skill DOES require a DataHub API key, even though the registry metadata omitted it. Expect to provide DATAHUB_API_KEY or create ~/.datahub/config.json or a project config file.
- The included scripts will read config files in your home directory and current working directory. Inspect those files and the scripts locally before running to ensure no unexpected file accesses.
- The scripts send your API key in the request body, in an X-API-Key header, and (for GET polling) as a query parameter. This can increase the chance the key is recorded in logs, referer headers, or proxies. Avoid using high-privilege credentials and consider creating a scoped API key with minimal permissions.
- Confirm the network endpoint (baseUrl defaults to https://datahub.seekin.chat). Verify the service owner, privacy policy, and reputation before sending sensitive data.
- The overall behavior aligns with the skill's stated purpose, but the metadata omission and how the key is transmitted are meaningful concerns. If you need to use it, (1) review the two included scripts, (2) prefer environment variables over files, (3) use a least-privilege API key, and (4) avoid putting highly sensitive secrets or data through this skill until you trust the endpoint and its operator.Like a lobster shell, security has layers — review code before you run it.
latestvk973d24djeeqexzkg90zgbzcf184pbe6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.