BigModel Web Search Fallback
Analysis
This appears to be a coherent BigModel/Zhipu web-search fallback, with the main user-visible risks being use of a BigModel API key and sending search queries to an external provider.
Findings (2)
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.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
os.environ.get("ZAI_API_KEY") or os.environ.get("ZHIPUAI_API_KEY") or os.environ.get("BIGMODEL_API_KEY") ... "Authorization": f"Bearer {api_key}"The script reads a BigModel/Zhipu API key from environment variables and sends it as bearer authentication to the provider. This is expected for the stated API integration, but it gives the skill access to the user's API account/quota and is not reflected in the registry credential declarations.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
WEB_SEARCH_URL = f"{BASE_URL}/paas/v4/web_search"
CHAT_URL = f"{BASE_URL}/paas/v4/chat/completions"The skill sends search queries or chat prompts to BigModel/Zhipu endpoints. This is disclosed and purpose-aligned, but it means user-provided query text crosses an external provider boundary.
