Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
AI Product Comparison Skill
v1.0.0Extract structured product data from e-commerce URLs using the Zyte API and generate side-by-side comparison tables with intelligent purchase recommendations...
⭐ 0· 28·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's name/description match the included scripts and Zyte API usage. However the SKILL.md and README clearly require a ZYTE_API_KEY, yet the registry metadata lists no required environment variables or primary credential — an incoherence that affects installation and access control. Everything else (calling api.zyte.com/v1/extract, writing parsed output, parallel fetching) is coherent with the described purpose.
Instruction Scope
Runtime instructions tell the agent to run the bundled Python scripts which perform network requests to Zyte and write raw responses to /tmp/product_*.json. That is within the skill's purpose. Concerns: the recommended invocation passes the API key as a command-line argument (python3 scripts/fetch_products.py "$ZYTE_API_KEY" ...), which can expose secrets in process lists; the README includes a troubleshooting line that suggests overwriting /etc/resolv.conf (echo 'nameserver 8.8.8.8' > /etc/resolv.conf) — a privileged action outside the skill's core purpose and potentially dangerous if followed blindly.
Install Mechanism
No install spec that downloads external archives — code is bundled in the skill ZIP. The scripts use only Python stdlib and no external URLs for installation, which limits supply-chain risk. The README's example GitHub clone URLs are placeholders; the registry lists 'source unknown' which reduces provenance assurance but not the install mechanism risk itself.
Credentials
Functionally the skill needs a Zyte API key (ZYTE_API_KEY) to call the Zyte API; that is proportionate. But the registry metadata does not declare this required credential, which is an incoherence and a user-experience/security gap. Operationally the scripts accept the API key as a CLI argument (exposed in ps output) rather than exclusively reading a protected environment variable — this increases the chance of accidental secret exposure on multi-user hosts. The skill asks the user to store the API key in openclaw.json or export it to the environment; that is expected, but you should ensure the key is stored securely.
Persistence & Privilege
The skill does not request always:true, does not alter other skills or global agent configs, and only writes temporary files to /tmp and optional parsed outputs when invoked. The README suggests copying the skill into managed skills directories (normal). No elevated or persistent privileges are requested by the skill itself.
What to consider before installing
What to check before installing or running this skill:
- The skill requires a Zyte API key (ZYTE_API_KEY) to work, but the registry metadata did not declare that; verify you are prepared to provide that credential and understand the billing/costs on Zyte for extractions.
- The fetch script examples pass the API key as a command-line argument, which can expose the key via operating-system process listings. Prefer running the code in an isolated environment or modify the script to read the API key only from an environment variable or a protected config file if you are concerned about local exposure.
- The scripts write raw Zyte responses to /tmp/product_*.json — these files can contain scraped product data and potentially other scraped text; ensure /tmp is acceptable for temporary storage and that you or the agent will clean up sensitive artifacts.
- The README includes a troubleshooting command that overwrites /etc/resolv.conf. Do not run that unless you understand the implications and have appropriate privileges — it is unrelated to the skill's core functionality and can have system-wide effects.
- Source provenance: the registry lists 'source: unknown' and no homepage. If you rely on third-party code, prefer skills with a clear repository or vendor homepage; if unsure, review the included scripts yourself or run them in a sandboxed environment before granting the agent runtime code execution privileges.
If you trust Zyte and are comfortable providing the API key, the code itself appears consistent with the stated purpose. If you need stronger assurance, ask the publisher to update registry metadata to declare ZYTE_API_KEY as a required credential, to avoid passing keys on the command line, and to provide a canonical source/homepage for provenance.Like a lobster shell, security has layers — review code before you run it.
latestvk97e3t9s02tmp6hpmqnwdx9mdh841dkc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
