Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed ClawEC Shopee search helper that sends user-chosen query parameters to ClawEC using the user's API key.
Install this only if you trust ClawEC with your Shopee search parameters and CLAWEC_API_KEY. Do not provide unrelated secrets; the reviewed artifact shows no local file harvesting, persistence, or hidden execution.
The skill includes executable shell usage (curl, bash scripts/query.sh) but does not declare any tool scope or allowed-tools restrictions. This can lead to overbroad execution privileges at runtime, making it easier for an agent to invoke shell unexpectedly or in environments where shell access should be constrained.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X POST "https://www.clawec.com/api/aigc/ec/shopee/data/item/search" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $CLAWEC_API_KEY" \
-d '{"site":"tw","categoryId":100630,"sortType":1,"sortOrder":"desc","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_TYPE" "$SORT_ORDER" "$PAGE_NO" "$PAGE_SIZE" "$TIMEST" "$FILTERS_JSON")
curl -s -X POST "https://www.clawec.com/api/aigc/ec/shopee/data/item/search" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $API_KEY" \
-d "$PAYLOAD"
This shell script performs a network POST request to an external service and includes both user-provided payload data and an authorization bearer token, but the file contains no comment, print/log message, or confirmation disclosing that data is being transmitted. For code files, outbound network calls that transmit user or system data should have some visible warning unless the disclosure is otherwise documented in the skill description.
The documentation states '默认中文报告', which imposes a specific output language by default. Under the policy, locale or language constraints should either be opt-in or clearly justified; this file does not offer a user choice or justify why Chinese is required.
This markdown file presents all operational instructions and schema descriptions exclusively in Chinese. Under the policy, forcing a specific language without user opt-in can be a natural-language policy violation unless the locale restriction is explicitly justified.
The usage and environment-variable error messages are hardcoded in Chinese, which imposes a specific language on users without any opt-in or documented regional justification. This matches the policy concern for language or locale restrictions in natural-language content.