Security audit
Security checks for vulnerabilities and agentic risk
This skill transparently queries Clawec for Shopee item trend data and does not show hidden persistence, destructive behavior, or unrelated data access.
Install this only if you intend to send Shopee item IDs, date ranges, and your Clawec API key to clawec.com. Keep the API key in an environment variable or secret store, avoid pasting it into chat logs, and review the fixed curl endpoint before running the helper script.
The skill instructs use of shell commands and a local script, but it does not declare any explicit tool scope or allowed-tools boundary. In an agent environment, this can lead to over-broad execution privileges, making it easier for the skill to invoke shell unexpectedly or in contexts the user did not intend.
The skill sends user-supplied business parameters and an API bearer token to an external third-party service. External transmission is expected for this integration, but it still creates security risk because sensitive inputs, usage metadata, and credentials are exposed to a remote system and could be mishandled, logged, or abused if the endpoint or surrounding environment is compromised.
curl -s -X POST "https://www.clawec.com/api/aigc/ec/shopee/data/item/trend" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $CLAWEC_API_KEY" \
-d '{"site":"tw","itemId":123456789,"granularity":1,"startDate":"2025-05-27","endDate":"2026-05-27","pageNo":1,"pageSize":10}'
The file instructs the agent to '输出中文商品趋势报告' and states '默认中文报告', which imposes a specific language behavior. Under the policy rule, forcing a language without explicit user opt-in or offering alternatives is a natural-language policy violation.
The script's usage and validation messages are presented only in Chinese, including the required-argument and granularity error text, with no indication that language selection is configurable or that the tool is intentionally locale-restricted. The policy flags language/locale constraints when a specific language is forced without user opt-in or clear justification.
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" "$ITEM_ID" "$GRANULARITY" "$START_DATE" "$END_DATE" "$PAGE_NO" "$PAGE_SIZE")
curl -s -X POST "https://www.clawec.com/api/aigc/ec/shopee/data/item/trend" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $API_KEY" \
-d "$PAYLOAD"
This code performs a network POST request to an external service and includes an Authorization bearer token, but the script provides no visible user-facing warning, logging, or comment explaining that request data will be sent off-host. Under the code-file criteria, outbound transmission of user or system data without any disclosure is a reportable missing-warning issue.
This markdown file consists entirely of Chinese-language headings, field descriptions, and guidance, which effectively forces a specific language for users reading the skill reference. The policy allows locale constraints only when users are given a choice or when the constraint is explicitly documented and justified, neither of which appears here.
The script reads CLAWEC_API_KEY from the environment for authenticated API access, but there is no surrounding comment, docstring, or user-facing message explaining that a credential will be used. The rule specifically covers access to sensitive environment variables when there is no disclosure at all.