Security audit
Security checks for vulnerabilities and agentic risk
The skill appears consistent with its stated purpose of generating LinkPix/qhkit advertising videos, with disclosed setup, API-token use, pricing checks, and delivery steps.
Before installing, confirm you want this skill to install or run qhkit from npm and store or use a qhkit API token for the LinkPix service. For bulk generation, verify the estimate before approving work that consumes account credits, and avoid making PATH or shell-profile changes unless you want the tooling to persist across sessions.
The metadata says this skill 'must trigger' for broad, common ad-video requests. Overly broad mandatory triggering can cause the agent to invoke the skill in situations where it is not necessary, increasing the chance of unnecessary external tool use, package installation, and token-handling for ordinary user requests.
The skill recommends falling back to npx @iqinghu/qhkit <命令> ... without pinning a specific package version. That allows execution of whatever version is current at invocation time, increasing supply-chain risk and making behavior non-deterministic if a malicious or compromised release is published.
This duplicated finding identifies the same persistence behavior: unpacking software into the user's home directory and advising PATH persistence across commands or via ~/.bashrc. Even with checksum verification, the pattern creates lasting environmental changes that may outlive the task and expand risk if the toolchain is later abused.
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 duplicated finding identifies the same persistence behavior: unpacking software into the user's home directory and advising PATH persistence across commands or via ~/.bashrc. Even with checksum verification, the pattern creates lasting environmental changes that may outlive the task and expand risk if the toolchain is later abused.
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 explicitly require using domestic-site key guidance and note that CLI messages are already user-facing Chinese, implying a fixed Chinese-language interaction pattern. The file does not offer the user a language choice or document a justified locale restriction, which violates the language/locale policy criteria.
The '何时触发' section gives only broad examples like preparing video assets for ads or bulk-producing platform variants. It does not clarify edge cases or when related requests should route to other skills, which can cause unintended invocation overlap.