Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md node scripts/run.mjs --sample # 先看样例
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a local Chinese-language accounting table checker that reads user-provided input and runs bundled deterministic Node.js code without network, persistence, or credential use.
Install only if you want a Chinese-language local checker for ecommerce refund and settlement tables. You will provide table data to a local Node.js script; inspection found no network transmission or persistence, but users should still avoid placing unnecessary sensitive data in inputs and should understand that several advanced checks are explicitly not included in the free version.
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 先看样例
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 先看样例
The skill metadata and user-facing descriptions are predominantly in Chinese and target Chinese-language trigger phrases, but there is no statement offering users a language choice or clarifying that Chinese is optional. This can violate language/locale policy when users are not given an explicit opt-in to a single-language experience.
The file’s natural-language comments, user-facing guidance, and disclaimers are entirely in Chinese, including operational instructions and warnings. This creates a locale policy issue because the skill appears to require a specific language without any opt-in, fallback, or documented region-specific justification.
The only natural-language content in the file is a Chinese tabular template, which implicitly constrains the skill output or data format to Chinese. Under the policy, locale-specific behavior should offer user choice or be explicitly justified as region-specific; neither is present in this file.
The manifest says "触发词包括" followed by two example phrases, which implies the list may not be exhaustive and does not explain what other phrasings should or should not invoke the skill. This creates ambiguity about activation scope and increases the chance of unintended invocation from similar everyday accounting-related requests.