Trust Assessment
ticktick received a trust score of 56/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 2 findings: 1 critical, 1 high, 0 medium, and 0 low severity. Key findings include Network egress to untrusted endpoints, Potential Command Injection via `ticktick` CLI arguments.
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 Findings2
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| CRITICAL | Network egress to untrusted endpoints HTTP request to raw IP address Review all outbound network calls. Remove connections to webhook collectors, paste sites, and raw IP addresses. Legitimate API calls should use well-known service domains. | Manifest | skills/kaiofreitas/ticktick-api/SKILL.md:11 | |
| HIGH | Potential Command Injection via `ticktick` CLI arguments The skill documentation describes the usage of `ticktick` command-line tools, such as `ticktick add`, `ticktick complete`, and `ticktick delete`, which accept arguments like task titles, project IDs, and task IDs. If these arguments are populated directly from untrusted user input without proper sanitization by the underlying `ticktick` tool or the skill's implementation, an attacker could inject shell metacharacters (e.g., `;`, `|`, `&`, `$(...)`) to execute arbitrary commands on the host system. The `ticktick-setup` command also takes `client_id` and `client_secret` as arguments, which could be vulnerable if generated from untrusted input. The skill's implementation should ensure that all arguments passed to the `ticktick` CLI tool are properly sanitized or escaped before execution. When constructing shell commands, use safe methods that prevent argument injection, such as passing arguments as a list to `subprocess.run()` with `shell=False`, or explicitly escaping user-provided strings. For `ticktick-setup`, ensure that `client_id` and `client_secret` are handled securely and not exposed to untrusted input. | LLM | SKILL.md:31 |
Scan History
Embed Code
[](https://skillshield.io/report/7e14bfc7516719b3)
Powered by SkillShield