Security audit
Security checks for vulnerabilities and agentic risk
The skill appears purpose-built for Qinghu product-image generation, but it asks agents to install and update tools, use persistent configuration, upload images, and spend credits under trigger rules that are too broad.
Install only if you intend to use the China-region Qinghu qhkit service for e-commerce product images. Confirm before uploading local images or spending credits, prefer a pinned and reviewed qhkit version, avoid adding PATH changes to shell startup files unless you want them to persist, and keep API tokens scoped and removable.
The metadata says the skill 'must trigger' for broad, common requests like image optimization or improving quality. In an agent environment, overly broad mandatory triggers can cause unintended invocation, leading to unexpected external tool use, uploads, installation attempts, or paid API consumption without sufficiently specific user intent.
The example trigger phrases are generic and can match many benign photo-editing requests outside the intended e-commerce main-image use case. Because this skill performs generation, installation, and remote-service interaction, ambiguous activation increases the chance of unintended execution and user data transfer.
The skill instructs use of npx @iqinghu/qhkit without pinning a specific version, which allows whatever package version is current at execution time to be fetched and run. That creates a supply-chain risk: a compromised or breaking upstream release could execute unexpected code or change behavior in a privileged automation context.
The skill directs installation of Node into $HOME/.local/lib and suggests adding it to PATH, including guidance to append PATH changes to ~/.bashrc. This creates persistence beyond the immediate task and modifies the user environment, which is risky in agent contexts because it changes future command resolution and can outlive the current session.
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 skill directs installation of Node into $HOME/.local/lib and suggests adding it to PATH, including guidance to append PATH changes to ~/.bashrc. This creates persistence beyond the immediate task and modifies the user environment, which is risky in agent contexts because it changes future command resolution and can outlive the current session.
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 instructions require directing users to China-specific iqinghu.com flows and state that CLI messages are already user-facing Chinese to be relayed as-is. This imposes a locale/language expectation without opt-in or an alternative path for users who may need another language or region.