T08 · Insecure Dependencies
- Location
SKILL.md:179- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a local document generator whose file reads, writes, templates, images, formulas, and font handling mostly match its stated purpose, with some usage cautions.
Install in a virtual environment, prefer pinned dependency versions, only use the skill when you want a document file created, choose safe output paths, and avoid passing untrusted spreadsheet data as formulas unless reviewed.
SKILL.md:179Unpinned Third-Party Dependency Installation
scripts/generate_excel.py:80Unrestricted Excel Formula Injection
If the code only generates DOCX while the skill advertises Excel and PDF generation, downstream systems may send sensitive business data into an incompatible or lossy path and receive misleading artifacts. The security risk is primarily integrity and trust-related: users may believe documents were produced in a requested format when they were not, or may expose template/data handling to the wrong implementation path.
If the code only generates DOCX while the skill advertises Excel and PDF generation, downstream systems may send sensitive business data into an incompatible or lossy path and receive misleading artifacts. The security risk is primarily integrity and trust-related: users may believe documents were produced in a requested format when they were not, or may expose template/data handling to the wrong implementation path.
If the code only generates DOCX while the skill advertises Excel and PDF generation, downstream systems may send sensitive business data into an incompatible or lossy path and receive misleading artifacts. The security risk is primarily integrity and trust-related: users may believe documents were produced in a requested format when they were not, or may expose template/data handling to the wrong implementation path.
Without declared permissions the skill's intent is opaque and cannot be validated.
The trigger language is very broad, including indirect phrases like wanting data in a table or formatted as a document, which can cause over-invocation. Overly broad activation increases the chance that the skill is selected in situations involving unrelated or sensitive content, expanding file access and output generation beyond what the user clearly intended.
The when-to-use section lacks clear activation boundaries and overlaps with many normal assistant tasks such as creating reports or working with data. In an agent setting, ambiguous routing guidance can misdirect sensitive data into a file-writing workflow unnecessarily, increasing exposure and unintended side effects.
This is a JSON manifest-style file, so vague-trigger checks apply. The prompt texts begin with broad, common phrases like '我需要生成...' and '帮我创建...', which overlap with everyday user requests and do not define any trigger scope, exclusions, or activation constraints.
All user-facing prompt and assertion descriptions in this file are written in Chinese, with no indication that language choice is optional or that the skill is intentionally limited to a Chinese-language context. That can violate language/locale policy because it implicitly fixes the interaction language without user opt-in.
This code explicitly centers its behavior around Chinese fonts and uses Chinese-language comments and user-facing status messages such as the success and warning prints. The skill does not offer any language/locale choice or explain that it is a region-specific tool, which can violate language/locale policy requirements for user-facing behavior.
The instructions show commands that write output files but do not prominently warn users that the skill will create files on disk and may overwrite chosen paths. This can lead to unintended file creation, confusion about persistence, or accidental writes in sensitive working directories, especially when combined with template and image path inputs.
This markdown file contains natural-language behavior stating that Chinese text handling will automatically select a system Chinese font. Because the policy scope includes language/locale constraints across all file types, this can be interpreted as enforcing a language-specific behavior without explicit user opt-in.
No suspicious patterns detected.