T09 · Insecure Skill Coding Practices
- Location
skill.md:29- Finding
Unconfirmed Bulk Filesystem Mutation Based on Filename-Only Classification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This file-organization skill is not malicious, but it should be reviewed because it can reorganize many local files without a required preview or confirmation.
Use this only on a narrow folder you choose, ideally after a backup. Before allowing changes, ask the agent to produce a dry-run manifest with every planned move or rename, confirm there are no overwrites or symlink escapes, and avoid running it across your home folder, system folders, synced drives, or active project directories.
skill.md:29Unconfirmed Bulk Filesystem Mutation Based on Filename-Only Classification
The description is written as a Chinese-only skill description and the operational instructions later require Chinese naming conventions and folder labels, but the document does not offer a user language/locale choice. This can violate language policy when a skill imposes a specific language without opt-in or clear region-specific justification.
The skill explicitly authorizes local filesystem modifications (move, rename, create) but provides no user-facing safety gate, dry-run mode, scope restriction, or warning about the consequences. In a file-management skill, semantic misclassification or path mistakes can silently reorganize large amounts of user data, causing effective data loss, workflow disruption, or difficult recovery even without deletion.
The skill mandates a particular naming scheme tied to Chinese labels and explicitly discusses Chinese naming choices, but does not allow the user to choose another language or locale. This is a natural-language policy concern because the locale constraint is imposed rather than offered as an option.
The instruction to complete all organization in one pass and avoid repeated confirmation increases the risk of unsafe bulk filesystem changes without user review. In this context, the skill is designed to make many semantic judgments automatically, so removing checkpoints materially raises the chance of widespread unintended file movement and user lockout from expected locations.
No suspicious patterns detected.