Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward ClawEC integration for querying Shopee shop rankings, with the network request and API key use disclosed and aligned with its purpose.
Install this only if you intend to use ClawEC and are comfortable sending Shopee ranking query parameters to clawec.com with your ClawEC API key. Store the key securely in the environment, avoid sharing it in prompts or logs, and review queries before using them for sensitive business research.
The skill includes executable shell usage examples and references a local script, but it does not declare any explicit tool scope or allowed-tools boundary. That omission can let an agent invoke shell capabilities more broadly than intended, increasing the chance of unauthorized command execution or unsafe extension of the workflow beyond the documented API call.
The skill instructs the agent to send authenticated requests containing a bearer token to an external service. External transmission is expected for this integration, but it still creates a real security boundary crossing: user-supplied query parameters and account-linked data are sent off-platform to a third-party API, and the skill does not include clear data-minimization, domain-allowlisting, or secret-handling safeguards beyond 'do not hardcode' the key.
curl -s -X POST "https://www.clawec.com/api/aigc/ec/shopee/data/shop/ranking" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $CLAWEC_API_KEY" \
-d '{"site":"tw","categoryId":100630,"sortField":1,"period":3,"borderType":0,"pageNo":1,"pageSize":10}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
print(json.dumps(body, ensure_ascii=False))
' "$SITE" "$CATEGORY_ID" "$SORT_FIELD" "$PERIOD" "$BORDER_TYPE" "$SHOP_TYPE" "$PAGE_NO" "$PAGE_SIZE" "$DATE")
curl -s -X POST "https://www.clawec.com/api/aigc/ec/shopee/data/shop/ranking" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $API_KEY" \
-d "$PAYLOAD"
This shell script performs an HTTP POST to an external API using a bearer token, but there is no confirmation prompt, logging, comment, or other user-facing disclosure describing that request. For a code file, transmitting request data and credentials to a remote service should have some visible warning unless that behavior is explicitly documented elsewhere.
The markdown instructs the skill to produce a '默认中文报告', which imposes a specific language preference. The policy for this audit flags language/locale constraints unless the skill offers a user choice or clearly documents a justified regional requirement.
This markdown file presents all instructions and field descriptions exclusively in Chinese. Under the policy rule for natural-language violations, forcing a specific language without user opt-in can be a locale policy issue when no justification or alternative is provided.
The usage and error messages are presented only in Chinese, which imposes a specific language choice without any opt-in or documented locale constraint. This matches the policy concern for language/locale restrictions expressed in natural-language strings.
The script reads the sensitive environment variable CLAWEC_API_KEY and uses it for authentication, but the file contains no warning or explanatory comment about handling credentials. Under the code-file criteria, access to sensitive environment variables should not be silent when there is no other visible disclosure in the file.