Trust Assessment
todo-management received a trust score of 72/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 1 finding: 1 critical, 0 high, 0 medium, and 0 low severity. Key findings include Unquoted variable in shell command leads to command injection.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.
Last analyzed on February 13, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings1
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| CRITICAL | Unquoted variable in shell command leads to command injection The `DB` variable, which can be controlled by the `TODO_DB` environment variable, is used unquoted in the `sqlite3` commands within the `sql` and `sql_scalar` functions. This allows an attacker to inject arbitrary shell commands by setting `TODO_DB` to a malicious string containing shell metacharacters (e.g., `;`, `|`, `&`). When the `sqlite3` command is executed, the injected commands will be run by the shell. Always quote variables that contain paths or user-controlled input when used in shell commands. Modify the `sql` and `sql_scalar` functions to quote the `$DB` variable: ```bash sql() { sqlite3 -bail "$DB" "$@"; } sql_scalar() { sqlite3 -noheader -batch "$DB" "$@"; } ``` | LLM | scripts/todo.sh:37 |
Scan History
Embed Code
[](https://skillshield.io/report/5acc8f79e3039605)
Powered by SkillShield