Security audit
Security checks for vulnerabilities and agentic risk
The skill is a real storyboard-generation integration, but it asks the agent to install and update external tooling in the user environment automatically, so it needs review before use.
Install only if you are comfortable with the agent installing or updating qhkit/Node tooling and configuring a Qinghu API token. Prefer reviewing the package source/version, pinning qhkit where possible, and approving any PATH or shell startup changes manually.
The manifest says the skill 'must trigger' whenever the user asks to write storyboards, storyboard images, storyboard, shot scripts, or filming scripts. Several of these phrases are broad, common request forms, and the file does not provide exclusion conditions or negative examples to distinguish when this skill should not activate.
The skill description is entirely in Chinese and directs use of the domestic CN site and Chinese-language workflow, but it does not state that language/locale is optional or user-selectable. This creates a locale constraint that appears imposed by default rather than offered as a choice.
The skill instructs fallback execution via npx @iqinghu/qhkit without pinning a specific version. That makes behavior non-deterministic and can pull whatever package version is current at execution time, increasing supply-chain risk if a bad release or compromised dependency is published.
This duplicate finding reflects the same persistence issue: installing Node under the user's home directory and exporting a modified PATH can outlive the immediate skill invocation. In a skill context, self-bootstrapping that alters the host environment is more dangerous because users may not expect content-generation tooling to install or reconfigure execution dependencies.
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 duplicate finding reflects the same persistence issue: installing Node under the user's home directory and exporting a modified PATH can outlive the immediate skill invocation. In a skill context, self-bootstrapping that alters the host environment is more dangerous because users may not expect content-generation tooling to install or reconfigure execution dependencies.
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"