Skillv1.0.0

ClawScan security

Turing Tavily Web Search · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

ReviewMar 13, 2026, 3:43 AM

Verdict: Review
Confidence: medium
Model: gpt-5-mini
Summary: The skill implements a Turing Tavily web search and legitimately needs Turing API credentials, but the package metadata does not declare those required credentials and the code expects them in a local config file — this mismatch and the undeclared dependency are inconsistent and worth verifying before install.
Guidance: Do not install blindly. Before using: (1) Confirm you trust the Turing Tavily proxy domain (default https://live-turing.cn.llm.tcljd.com) because your API key will be sent there. (2) Verify or update the registry metadata to declare TURING_API_KEY, TURING_CLIENT, and TURING_ENVIRONMENT so you know what secrets are required. (3) Check that the script's expected config location (~/.openclaw/openclaw.json) is acceptable to you — the script reads that file for credentials. (4) Ensure Python's 'requests' is available or install it in an isolated environment. (5) If you have doubts about the endpoint or owner, review the script yourself or run the skill in a locked-down container; do not provide production API keys until you are confident.

Review Dimensions

Purpose & Capability: concernThe code and SKILL.md implement a web search via a Turing Tavily proxy and require TURING_API_KEY, TURING_CLIENT, TURING_ENVIRONMENT — these credentials are proportional to the stated purpose. However, the registry-level metadata provided earlier declares no required env vars or primary credential, which is inconsistent with the skill's actual behavior.
Instruction Scope: noteSKILL.md instructs running the bundled script and configuring credentials in ~/.openclaw/openclaw.json (skills.entries.turing-skills.env). The script only reads that file and sends search queries to the Turing proxy; it does not attempt to read other system files. This scope is appropriate, but the reliance on a user config file (instead of environment variables at runtime) should be noted.
Install Mechanism: noteThere is no install spec (lowest install risk) and no network-downloaded code. However, the bundled script uses the Python 'requests' package but the skill does not declare this dependency; runtime failures or unexpected local installs may occur if 'requests' is missing.
Credentials: concernThe script requires TURING_API_KEY (Bearer token), TURING_CLIENT, and TURING_ENVIRONMENT, plus an optional TURING_API_BASE. Those are appropriate for calling the proxy API, but the registry metadata omitted these requirements. The mismatch between declared and actual credential needs is a red flag that could lead to misconfiguration or inadvertent secret exposure.
Persistence & Privilege: okThe skill is not always-enabled and does not request elevated or persistent system privileges. It only reads its own config file (~/.openclaw/openclaw.json) and does not write system-wide settings or modify other skills.