Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed ecommerce image workflow that installs and uses qhkit to generate white-background product images, with some normal dependency and setup risks.
Install only if you are comfortable sending product images to the qhkit/iqinghu service and installing its npm CLI. Prefer a reviewed or pinned qhkit version for reproducibility, avoid adding PATH changes to shell startup files unless you want a permanent setup, and verify generated product details because the workflow is generative rather than pixel-preserving.
The manifest says the skill "must trigger" whenever a user asks to cut out an image, remove a background, or make a pure-color background, and then lists many broad keywords. Several of these phrases are common image-editing requests that can overlap with other tools or contexts, and the file does not provide exclusion conditions or negative examples to narrow invocation scope.
The skill recommends invoking npx @iqinghu/qhkit without a pinned version, which can pull whatever package version is current at execution time. That creates a supply-chain risk: behavior can change unexpectedly, and a compromised or malicious upstream release could be executed immediately in the user's environment.
The same installation block creates durable local state by unpacking binaries into a user-owned directory and exporting a new PATH, potentially persisting across sessions if added to shell startup files. While not inherently malicious, this changes the execution environment in a way that can be abused or can mask system binaries 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 same installation block creates durable local state by unpacking binaries into a user-owned directory and exporting a new PATH, potentially persisting across sessions if added to shell startup files. While not inherently malicious, this changes the execution environment in a way that can be abused or can mask system binaries 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 markdown gives a couple of example requests and a general condition about marketplace white-background requirements, but it does not clearly state when the skill should not activate. Without explicit exclusions, requests like generic background removal or non-ecommerce edits could unintentionally route here.