Security audit
Security checks for vulnerabilities and agentic risk
This music-tracking skill is Markdown-only, but it asks for command execution and file-writing authority that is not clearly bounded by its music purpose.
Review before installing. This does not show malicious payloads, persistence, or exfiltration, but it gives a music-themed skill broad write and command-execution authority. Install only if you trust the publisher and are comfortable with the agent using local files, external APIs, and shell commands; otherwise ask the publisher to remove exec/write or document exact allowed actions first.
Requesting the exec tool in the manifest grants the skill direct command-execution capability despite the stated purpose being music tracking and organization. That mismatch is especially risky because tool permissions are what determine real power, and an attacker or confused user could leverage exec for actions far outside the expected music workflow.
Declaring system command execution for a music-management skill is dangerous because exec enables arbitrary local actions unrelated to the stated purpose. In this context, the capability is not clearly justified, so it expands the attack surface for filesystem access, persistence, or host compromise if the skill is invoked with unsafe instructions.
The skill uses broad applicability language spanning personal management, automation workflows, and decision support without clear trigger constraints or boundaries. Overbroad positioning makes it easier to justify unrelated or risky operations under vague intent, especially when the skill also has write and exec capabilities.
The description claims risky code and external-risk elements were removed, yet the skill still exposes command execution capability. This contradiction can mislead reviewers and users into underestimating risk, which is itself security-relevant because it weakens informed consent and scrutiny around a high-risk permission.
The skill is presented as a personal music tracking tool, but the documentation advertises generic file handling, API access, and command execution capabilities that materially exceed that scope. This mismatch increases the chance the skill could be used as a general-purpose execution wrapper, reducing user awareness and making unsafe actions appear legitimate.
The markdown advertises file writing, API integration, and command execution but does not provide strong user-facing warnings about the security impact of those actions. In a skill with elevated capabilities, insufficient disclosure increases the risk of unsafe use, accidental data modification, or trust abuse because users may assume the tool is low-risk based on its music theme.
No suspicious patterns detected.
