Expert in SQLCipher encrypted database development with focus on encryption key management, key rotation, secure data handling, and cryptographic best practices
Security
2 findings — 2 high severity. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Insecure credential handling detected (high risk: 1.00). The prompt contains hardcoded-looking encryption keys in tests and examples and uses direct insertion of key values into PRAGMA/SQL statements (e.g., f"PRAGMA key = {key}"), which requires handling and can lead the model to output secret values verbatim.
Detected sensitive credentials directly embedded within the skill content, such as API keys, access tokens, private keys, or service-specific secrets. Secrets should never be hardcoded in plain text within skill instructions.
Secret detected (high risk: 1.00). I found hardcoded encryption keys in the test and example code. Specifically, the Python tests and Rust examples embed literal SQLCipher keys of the form:
1086ef2
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.