Trust Assessment
winamp received a trust score of 88/100, placing it in the Mostly Trusted category. This skill has passed most security checks with only minor considerations noted.
SkillShield's automated analysis identified 1 finding: 0 critical, 1 high, 0 medium, and 0 low severity. Key findings include Potential Command Injection via `exec` with user-controlled file paths.
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 14, 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 | |
|---|---|---|---|---|
| HIGH | Potential Command Injection via `exec` with user-controlled file paths The skill documentation describes using the `exec` tool to run `winamp.exe` with arguments, specifically file paths (e.g., `winamp.exe "C:\path\to\file.mp3"`). If the file path argument is derived from untrusted user input and is not properly sanitized or quoted before being passed to the `exec` command, an attacker could inject arbitrary shell commands. For example, providing a path like `"; rm -rf /"` could lead to malicious execution. While the `moltbot` example shows a hardcoded path, the general usage implies dynamic, user-controlled paths, making this a significant risk. Ensure that all user-provided arguments, especially file paths, are strictly validated and properly escaped/quoted before being passed to the `exec` command. Consider using a dedicated library for command argument construction or a safer API that separates the command from its arguments. Update the documentation to explicitly warn about this and provide examples of safe argument handling. | LLM | SKILL.md:28 |
Scan History
Embed Code
[](https://skillshield.io/report/eade943af44d32b6)
Powered by SkillShield