Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed automation-script guide, but it describes scheduled execution, automatic Git pushing, and automatic repair without enough scoping or approval safeguards.
Review before installing or using this skill for real automation. Only schedule scripts you understand, keep Git push behavior opt-in and scoped to approved repositories/remotes, require review before auto-repair actions, and verify logs/backups do not retain sensitive data longer than intended.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
skill:automation-scripts --list
# 创建新脚本
skill:automation-scripts --create --name "my-script" --type "monitor"
# 执行脚本
skill:automation-scripts --run "script-name"
The skill explicitly describes a Git automation script that will automatically add, commit, and push changes, but it provides no warning, confirmation step, scope restriction, or discussion of the risk of transmitting local repository contents to a remote. In an automation skill, this is dangerous because users may unintentionally publish sensitive files, credentials, or incomplete work through unattended execution.
The OpenCode integration describes automatic diagnosis and repair after detecting service failures, but it does not warn that such remediation may change configuration, restart services, remove files, or otherwise alter system state. In the context of an automation skill, silent self-healing behavior increases the risk of destructive or cascading changes without operator review.
The natural-language description is presented in Chinese and the file consistently assumes Chinese-language operation, with no indication that users may choose another language. Under the locale policy, forcing a specific language without opt-in or justification is a policy concern.