Back to skill
Skillv1.0.0

ClawScan security

baidu-search · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

ReviewMar 16, 2026, 8:14 AM
Verdict
Review
Confidence
medium
Model
gpt-5-mini
Summary
The skill appears to implement Baidu Qianfan search as described, but the package/registry metadata does not declare the required BAIDU_QIANFAN_API_KEY credential (and thus is internally inconsistent), so proceed only after addressing this mismatch and verifying the origin.
Guidance
This skill's code and docs implement the Baidu Qianfan search API and only need one secret: BAIDU_QIANFAN_API_KEY. However the registry metadata omitted that required env var — an oversight that should be corrected before trusting the skill. Before installing: (1) confirm the skill's source and owner (no homepage provided); (2) require the maintainer to add BAIDU_QIANFAN_API_KEY to the skill's declared required env/primary credential in the registry; (3) verify the endpoint (qianfan.baidubce.com) is legitimate for your account; (4) store the API key in your platform's secrets manager rather than a plain .env when possible and avoid committing .env to version control; (5) run npm install in an isolated environment and review package.json before executing; and (6) consider rotating the API key after testing. The current issue is metadata inconsistency (not obvious malicious code), but confirm provenance before adding this skill to production agents.

Review Dimensions

Purpose & Capability
okThe name, description, SKILL.md, scripts/search.mjs and references/api-reference.md all consistently implement a Baidu Qianfan (千帆) enterprise search integration. The code calls the documented endpoint (qianfan.baidubce.com) and uses expected parameters. Declared dependencies (commander, dotenv) are appropriate for a CLI Node tool.
Instruction Scope
okSKILL.md instructions stay on-topic: they explain how to provide the API key (env var or .env), how to run the script, and what parameters the search supports. The runtime instructions do not ask for unrelated files or credentials and only reference the skill-local .env file and the search API.
Install Mechanism
okThere is no install spec (instruction-only skill) and the code is small and readable. package.json lists normal runtime deps; however, because there's no install step in metadata the user or host will need to install Node deps (npm install) before running. No external or obscure download URLs are used.
Credentials
concernThe runtime code and SKILL.md require BAIDU_QIANFAN_API_KEY (via environment or .env), but the registry metadata lists no required env vars or primary credential. This is an inconsistency: the skill legitimately needs a single API key, and that key should be declared in the skill metadata (primaryEnv / requires.env). The missing declaration could lead to runtime failure or mask the fact that a secret will be used by the skill.
Persistence & Privilege
okThe skill does not request elevated/persistent privileges. always is false, it does not modify other skills or system-wide agent settings, and it only reads a skill-local .env (dotfile) for the API key. It performs outbound HTTPS requests only to the documented Baidu endpoint.