Security audit
Security checks for vulnerabilities and agentic risk
This looks like a Python guidance skill, but it asks for broad write, command, and external-service abilities that are not clearly bounded.
Review this skill before installing. It may be acceptable as a read-only Python reference, but do not grant write, command execution, API key, callback URL, or broad automation authority unless the platform enforces explicit user approval and tight scoping for each action.
The skill describes file writes, external API calls, and command execution but does not provide a clear, prominent warning that these actions can change the local system or send data externally. Users may reasonably believe they are invoking a passive guidance skill, making this especially dangerous in an agent environment with powerful tools.
Documenting system command execution in a skill whose purpose is teaching robust Python practices is unjustified privilege expansion. If the agent exposes exec based on this skill, an attacker could pivot a benign coding-assistance request into shell command execution, potentially affecting the host environment.
The description uses broad invocation language such as improving efficiency, automating workflows, and batch processing, which can cause the skill to match many generic requests unrelated to Python robustness. Over-broad routing increases the likelihood that a high-capability skill is activated in inappropriate contexts.
Advertising generic automation and configuration capabilities without clear activation constraints makes the skill eligible for a wide range of requests. In combination with write/exec capabilities, this broad matching increases the risk of unintended or unsafe tool exposure.
The early description frames the skill as Python robustness guidance, but later sections broaden it into a general automation tool with file handling, API integration, and command execution. That mismatch weakens informed consent and can cause the agent or user to treat the skill as educational when it is actually operationally capable.
Broad file read/parse/write capability exceeds what is needed for a guidance-oriented skill and creates unnecessary opportunities to alter user files. In an agent environment, this can lead to unauthorized modification of source code, configuration, or other local data during routine assistance tasks.
External API integration is not necessary for a Python robustness guidance skill and unnecessarily expands the trust boundary. This can enable data exfiltration, unintended outbound requests, or use of sensitive environment-provided credentials under the guise of educational assistance.
The skill presents itself as a pure Markdown guidance skill at the end, yet elsewhere advertises exec, write, and API/network-style capabilities. This inconsistency can mislead users and policy layers about the skill's true power, increasing the chance that a seemingly low-risk documentation skill is invoked in contexts where system-impacting actions occur.
No suspicious patterns detected.
