Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
alphashop-sel-product-search
v1.0.1商品搜索API SKILL:通过关键词搜索发现Amazon/TikTok平台商品。 支持价格、销量、评分、上架时间等多维度筛选条件。 通过 AlphaShop REST API 调用遨虾AI选品系统的商品搜索服务。
⭐ 0· 64·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill claims to search Amazon/TikTok via the AlphaShop REST API and the included Python script implements exactly that (HTTP POST to https://api.alphashop.cn). That capability is coherent with the name/description. However, the registry metadata lists no required environment variables or primary credential, while README/SKILL.md and scripts/search.py explicitly require ALPHASHOP_ACCESS_KEY and ALPHASHOP_SECRET_KEY (or CLI --app-key/--app-secret). This metadata mismatch is unexpected and should be explained.
Instruction Scope
Runtime instructions direct the agent to collect platform/region from the user (via AskUserQuestion) and to run scripts/search.py with collected parameters. The script only performs parameter validation, constructs a JSON payload, generates a JWT using the provided keys, and posts to the AlphaShop endpoint. It does not attempt to read unrelated system files or other credentials. Note: the script prints the request payload to stdout (it will echo request parameters), which can expose user-supplied data in logs.
Install Mechanism
There is no install spec (instruction-only / no package installation), which limits disk writes. However the skill includes a non-trivial Python script that depends on external libraries (requests, PyJWT). Those dependencies are not declared in the registry metadata or README. The absence of declared dependencies is an operational gap (may fail at runtime or cause users to pip-install packages themselves).
Credentials
The script and documentation require ALPHASHOP_ACCESS_KEY and ALPHASHOP_SECRET_KEY for API calls (used to generate JWT). Requesting those two credentials is proportionate to calling AlphaShop. However the registry/manifest claims 'required env vars: none' and 'primaryEnv: none' — a direct inconsistency. The skill will access those environment variables at runtime (and accept them via CLI) but the platform metadata does not advertise that. That mismatch is a red flag because it may lead users to inadvertently supply credentials without realizing which skill will use them.
Persistence & Privilege
The skill does not request permanent presence (always: false), does not modify other skills or global config, and has no installation step that writes persistent system-wide artifacts. It runs as a script and performs a network call — normal for this functionality.
What to consider before installing
What to check before installing/using this skill:
- Source verification: The skill's source/homepage is missing. Confirm the publisher and that alphashop.cn is a legitimate service you trust before supplying API keys.
- Credentials: The SKILL.md and README require ALPHASHOP_ACCESS_KEY and ALPHASHOP_SECRET_KEY, but the registry metadata incorrectly lists no required env vars — treat this as a metadata bug and assume the skill will read those env vars or accept them via CLI. Do not reuse high-privilege keys: create a scoped/test key if possible.
- Dependencies: The included Python script uses requests and PyJWT but the skill does not declare dependencies. Install dependencies in an isolated environment (virtualenv) and review the script locally before running.
- Logging of inputs: The script prints the full request payload to stdout (including userId and search parameters). Avoid putting secrets into fields that get printed; rotate keys if exposed to logs.
- Network calls: The script makes outbound HTTPS POSTs to api.alphashop.cn. If organizational policy restricts external calls, block or review the endpoint. Consider testing with a network sandbox or verifying the endpoint's TLS certificate and ownership.
- Inconsistencies: Ask the maintainer to (1) correct registry metadata to list required env vars and dependencies, (2) provide a homepage/source repository, and (3) confirm the correct process for obtaining API keys.
Because of the metadata/dependency inconsistencies and missing source, treat this skill as suspicious until the publisher/source and required environment/dependency declarations are clarified.Like a lobster shell, security has layers — review code before you run it.
latestvk973cwp2p77q9zg4zkbt14ydjs83ee4p
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Primary envnone
