Security audit
Security checks for vulnerabilities and agentic risk
This 1688 sourcing skill is purpose-aligned and disclosed, but users should understand it may use a Qinghu API token, consume paid credits, and export larger result sets to local files.
Install only if you intend to use Qinghu's 1688 data service. Use a dedicated Qinghu API key, expect credit consumption after you approve tool calls, and be aware that larger result sets may be exported to local spreadsheet files.
The metadata says the skill 'must trigger' for a broad set of sourcing and comparison intents, creating aggressive activation rules that can preempt other tools or workflows. Over-broad mandatory routing can cause the agent to invoke this skill in unrelated contexts, increasing the chance of unnecessary external API calls, credential prompts, or data export behavior.
The skill explicitly instructs the agent to source credentials from environment variables (QINGHU_TOKEN / QHKIT_TOKEN) in addition to asking the user. That grants the skill access to ambient secrets unrelated to a single user turn, which exceeds the minimum needed for a user-invocable sourcing workflow and creates a path for unintended secret use across users or contexts.
The skill directs default export of large result sets and reuse of cached local file paths, causing the agent to create and operate on local files beyond the core search/comparison function. This increases data persistence and exposure risk, especially if product data, links, or user-supplied inputs are written to shared or long-lived storage without explicit consent.
The skill mandates default export of datasets of 10+ records without clearly surfacing that user data and fetched results may be written to files. Because the skill also references cached local files and downstream export behavior, lack of an explicit warning or consent step makes data handling less transparent and raises privacy and persistence concerns.
Examples like '找货源 / 找供应商' and '比较一下这几家供应商' are common business phrases that could arise outside the intended 1688-specific workflow. The section provides positive examples but no negative examples or explicit limitation on when similar phrasing should not activate the skill.
No suspicious patterns detected.
