Sql Audit

SQL 语法与安全审核，它将真正执行，并返回执行的数据结果

This skill will actually run SQL against whatever database credentials you provide and may call an external LLM (Gemini) if configured. Before installing or running it: - Don't supply high-privilege DB credentials. Create and use a dedicated, read-only DB user limited to the minimal schemas/tables needed. - Verify how you will provide credentials: the code expects DB_DSN or an explicit db_dsn input, but SKILL.md lists DB_HOST/DB_USER/etc — fix this mismatch and test in a safe environment. - Be aware index.js loads ../.env (the parent .env). That can leak other project secrets into the skill; store DB/GEMINI credentials in a separate, minimal .env for the skill or avoid using a project-wide .env. - The skill may make outbound HTTP calls (Gemini) using GEMINI_API_URL/GEMINI_API_KEY/GEMINI_TOKEN. Only provide tokens that are scoped and revocable. - Review the included sql_audit.py code (especially the parts that build and send LLM requests and error handling) before use. Run the skill in an isolated environment or staging DB first. - If you cannot review the code or control the DB credentials and network egress, do not install or run this skill. I rated this 'suspicious' (not 'malicious') because many behaviors are reasonable for an SQL execution/audit tool, but the undocumented env usage, .env loading from the project root, and mismatch between docs and runtime make it unclear and potentially dangerous without careful configuration and review.

Type: OpenClaw Skill Name: sql-audit Version: 1.0.0 The skill bundle is classified as suspicious due to a significant discrepancy between its documentation and implementation, alongside high-risk credential handling. While SKILL.md claims the tool performs security auditing and intercepts write operations or full table scans, the actual code in sql_audit.py and index.js lacks these safeguards and executes raw SQL directly. Furthermore, the code contains a hardcoded JWT token and directs LLM requests to a specific IP address (47.77.199.56) instead of a standard API endpoint, which could facilitate data interception or unauthorized access.