mariadb-errors-deadlocks
Pass
Audited by Gen Agent Trust Hub on Sep 16, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: The skill provides legitimate technical documentation and code examples for database administration and transaction handling, focusing on error recovery and lock discipline.
- [SAFE]: No evidence of prompt injection, data exfiltration, or obfuscation was found. The instructions are purely informative and do not attempt to bypass agent safety constraints.
- [SAFE]: External references are limited to official MariaDB documentation (mariadb.com) and common placeholder domains used for illustrative purposes in anti-pattern examples.
- [SAFE]: All suggested configuration changes, such as enabling deadlock logging (innodb_print_all_deadlocks), align with industry best practices for database observability and forensic analysis.
Audit Metadata