Security audit
Security checks for vulnerabilities and agentic risk
This skill is for Shopee ranking queries, but it also tells the agent to install software, change the local environment, and handle an API token, so it should be reviewed before use.
Install only if you are comfortable with the agent installing Node/qhkit, modifying the user environment, and configuring a qhkit API token for a paid external service. Prefer a disposable environment or preinstalled, pinned qhkit version, and require explicit approval before any install, token setup, upgrade, or paid call.
The trigger definition is broad and says the skill 'must' activate for similar requests, making accidental invocation more likely. In combination with the skill's install/configure behavior and paid external calls, overly broad triggering can cause unnecessary tool use, host changes, or credential prompts from ordinary conversation.
The sample trigger phrases are generic enough that normal discussion of Shopee trends or hot products could invoke the skill. Because the skill can lead to paid API usage and environment setup steps, low-specificity triggers increase the chance of unsafe or unauthorized actions.
The skill goes well beyond querying product rankings and instructs the agent to install Node, install global packages, configure API tokens, and modify the host environment. That materially expands the attack surface from data retrieval to host-level software installation and credential handling, which is dangerous if the skill is triggered in an untrusted or sensitive environment.
The skill instructs use of npx @iqinghu/qhkit without pinning a specific version, which allows execution of whatever package version is current at runtime. In a skill context, this creates a supply-chain risk because behavior can change unexpectedly or a compromised upstream release could execute arbitrary code on the host.
This repeated finding describes persistent installation into a user directory and shell path modification, which survives beyond the immediate task. Such persistence is especially risky here because it is bundled into routine skill guidance, normalizing host alteration for a simple data-query workflow.
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 repeated finding describes persistent installation into a user directory and shell path modification, which survives beyond the immediate task. Such persistence is especially risky here because it is bundled into routine skill guidance, normalizing host alteration for a simple data-query workflow.
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"
No suspicious patterns detected.