T09 · Insecure Skill Coding Practices
- Location
SKILL.md:38- Finding
Destructive Git Synchronization Can Erase Local Work
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is not clearly malicious, but it tells an agent to automatically reset, edit, push, and possibly deploy code without enough safeguards.
Install only in a disposable or well-protected repository, preferably on a dedicated branch or isolated worktree with limited credentials. Do not give it production deployment credentials or direct protected-branch push rights unless you add explicit approval, backup, and review gates.
SKILL.md:38Destructive Git Synchronization Can Erase Local Work
SKILL.md:43Automated Push and Deployment Lack Explicit Authorization Boundaries
The workflow explicitly instructs a forced sync using git fetch + reset --hard + pull, which can discard local uncommitted changes and overwrite user work. In an automated skill that runs periodically, this is especially dangerous because it normalizes destructive repository operations without any explicit warning, confirmation, backup, or safety check.
The skill body is written entirely in Chinese and does not indicate that the user can choose another language or locale. This creates a language-policy concern because it implicitly constrains usage to a specific language without opt-in.
The skill states it will read and update TASKS.md as part of normal operation but does not clearly warn users that their project files will be modified automatically. In a recurring automation context, silent file modification can lead to unintended edits, workflow corruption, or loss of user trust, especially if the board format differs from expectations.