Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent Amazon product-image generation helper, but it uses a third-party CLI that may install tools, handle an API key, upload product images, and spend credits after user confirmation.
Install only if you are comfortable using Qinghu/LinkPix qhkit for Amazon image generation. Review package installation, avoid sharing sensitive product images unnecessarily, protect the API key, and confirm estimated credits before any generate command runs.
The metadata description says Amazon image requests 'must trigger' this skill for broad categories, which can cause unintended invocation for common user requests. Overbroad trigger rules are dangerous because they may route unrelated prompts into tool execution flows involving package installation, credential setup, and external service calls without sufficiently clear user intent.
The '何时触发' section relies on natural-language examples like '做亚马逊的商品图 / 主图 / 套图' without enough guardrails, making accidental activation likely. In this skill, unintended activation matters because the downstream workflow can lead to software installation, token handling, file uploads, and billable API calls.
The skill instructs use of npx @iqinghu/qhkit without pinning a version, which causes execution of whatever package version is current at runtime. That creates a supply-chain risk: a compromised latest release or malicious dependency update could be fetched and executed automatically on the host.
This same installation block creates lasting user-environment changes by placing Node under the home directory and exporting a new PATH entry. In an agent setting, such persistence is risky because it changes the execution baseline for subsequent tasks and may enable unreviewed binaries to be reused later.
cd /tmp && curl -fsSLO https://nodejs.org/dist/v22.22.3/node-v22.22.3-linux-x64.tar.xz cd /tmp && curl -fsSL https://nodejs.org/dist/v22.22.3/SHASUMS256.txt | grep ' node-v22.22.3-linux-x64.tar.xz$' | sha256sum -c - mkdir -p "$HOME/.local/lib" && tar -xJf /tmp/node-v22.22.3-linux-x64.tar.xz -C "$HOME/.local/lib" export PATH="$HOME/.local/lib/node-v22.22.3-linux-x64/bin:$PATH"
This same installation block creates lasting user-environment changes by placing Node under the home directory and exporting a new PATH entry. In an agent setting, such persistence is risky because it changes the execution baseline for subsequent tasks and may enable unreviewed binaries to be reused later.
cd /tmp && curl -fsSLO https://nodejs.org/dist/v22.22.3/node-v22.22.3-linux-x64.tar.xz cd /tmp && curl -fsSL https://nodejs.org/dist/v22.22.3/SHASUMS256.txt | grep ' node-v22.22.3-linux-x64.tar.xz$' | sha256sum -c - mkdir -p "$HOME/.local/lib" && tar -xJf /tmp/node-v22.22.3-linux-x64.tar.xz -C "$HOME/.local/lib" export PATH="$HOME/.local/lib/node-v22.22.3-linux-x64/bin:$PATH"
The fallback image-compression command uses npx --yes sharp-cli without a pinned version, allowing an arbitrary current package release to be downloaded and executed. Because this path is triggered automatically during error handling, it increases the chance of silently introducing unreviewed third-party code execution.