Security audit
Security checks for vulnerabilities and agentic risk
This SQLite helper appears non-malicious, but it asks for broad database-changing capability while leaving API key use, data flow, and destructive-operation safeguards unclear.
Review this skill before installing in workflows that touch important or sensitive databases. Use it only on intended SQLite files, avoid giving it broad workspace access, confirm any update or delete operation explicitly, keep backups, and clarify whether any LLM/API integration can see database contents.
The skill markets itself as a lightweight local SQLite capability, but elsewhere requires an API key and an LLM API, creating a misleading trust boundary. Users may provide sensitive local data under the assumption it stays local when the documented dependencies imply potential remote processing or telemetry.
The security/compliance table claims protections such as encryption in storage and transit, but the file provides no implementation details or configuration proving those controls exist. Unsupported security claims can cause operators to overtrust the skill and store sensitive data without applying needed compensating controls.
The activation guidance is broad and repetitive, effectively suggesting use for generic database operations without clear boundaries, exclusions, or safety conditions. In an agent environment, vague triggers increase the chance the skill is invoked on inappropriate tasks or sensitive datasets without deliberate user intent.
The usage example includes a direct delete operation without any warning, confirmation flow, backup guidance, or mention that the action is irreversible. In an agent-assisted workflow, this can normalize destructive behavior and lead to accidental data loss if copied or auto-generated into real tasks.
No suspicious patterns detected.
