Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent database lock-analysis helper, but it includes transaction termination without a clear confirmation or safety boundary, so it should be reviewed before use.
Install only if you intend agents to inspect database locks through `dbskiter`. Treat any transaction-kill recommendation as a privileged database operation: require a human confirmation, verify the database name and transaction ID, and avoid using it against production systems without an incident procedure.
Natural-language content throughout the file forces a specific language/locale for interaction and documentation. The policy allows locale constraints only when users are given a choice or when the restriction is explicitly documented and justified, neither of which appears here.
The trigger phrases are broad natural-language terms like '看锁', '死锁', and '阻塞', which can plausibly appear in ordinary troubleshooting conversation and may cause the skill to activate when the user did not intend to run database lock-analysis actions. In this skill, accidental activation is more dangerous because the documented workflow can progress from read-only inspection to recommending or invoking a destructive action such as killing a transaction.
No suspicious patterns detected.
