T09 · Insecure Skill Coding Practices
- Location
SKILL.md:95- Finding
Shell Command Injection Through Unquoted Directory Parameters
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a legitimate file organizer, but its broad cleanup trigger and unsafe shell examples create review-worthy risk for local file changes.
Install only if you are comfortable with an assistant inspecting and reorganizing local files. Use it on one explicitly named folder at a time, review the proposed move/rename/delete plan, require confirmation before deletion, and ensure any shell commands treat directory paths as safe arguments rather than interpolated command text.
SKILL.md:95Shell Command Injection Through Unquoted Directory Parameters
The trigger phrase "清理" is broad and can match many routine requests unrelated to file organization, increasing the chance this skill is invoked in contexts the user did not intend. Because this skill can analyze, move, rename, and potentially delete files after interaction, ambiguous activation raises the risk of accidental exposure of sensitive file metadata or unintended destructive operations.
The title, description, category, and tags are written entirely in Chinese, indicating a locale-specific presentation, but the manifest does not document that the skill is intended only for Chinese-speaking users or provide an opt-in language choice. This can violate language/locale policy expectations when a skill implicitly forces one language without user selection or justification.
The metadata brands the skill as a China/Chinese variant and presents Chinese language first, but the file does not explain whether language behavior is optional or region-specific. That can create an implicit language or locale constraint without explicit user opt-in.
Although the full example is about Downloads, the instruction introduces invocation with a common everyday phrase that is not itself distinctive to this skill. This can make activation expectations unclear if trigger guidance is reused or interpreted loosely.
The metadata description advertises broad local file-management capabilities such as automatic classification, renaming, and duplicate cleanup without clearly constraining when the skill should activate or what boundaries apply. In an agent ecosystem, vague activation scope can cause unintended invocation on sensitive filesystem tasks, increasing the chance of overbroad actions or user-confusing behavior.