Security audit
Security checks for vulnerabilities and agentic risk
This skill is mostly a Python robustness guide, but it requests execution and write authority while advertising broad automation, API, file-processing, and command-execution capabilities that are not clearly scoped or implemented.
Review before installing. Use it only for Python reliability guidance or user-directed Python code review, and do not rely on its claims about automated API calls, batch file processing, or command execution unless the publisher narrows and documents those behaviors.
The skill advertises external API integration, file handling, and command execution capabilities that are not actually implemented in the static guidance content. This is dangerous because an agent or user may over-trust the skill, invoke higher-risk tools unnecessarily, or approve actions under false assumptions about what the skill safely supports.
The performance table claims concrete automation outcomes for API calls, batch file processing, and command execution despite the file containing only static educational material. These misleading claims can cause operators to grant the skill broader trust or permissions than warranted, increasing the chance of unsafe invocation and misconfiguration.
The description frames the skill as a general automation and workflow optimization tool, but the body is a static Python robustness guide. This mismatch is risky because broad positioning can trigger the skill in unrelated contexts and encourage the agent to use dangerous tools like exec or write without a justified task fit.
The feature summary repeats claims about automation and flexible configuration that are not reflected in the actual content. While less severe than executable instructions, this still misrepresents capability and can contribute to inappropriate invocation or over-permissioning of the skill.
The activation guidance is broad enough to match generic efficiency, automation, and workflow tasks rather than narrowly scoped Python robustness work. Overbroad routing is dangerous because it can cause the agent to select a skill with exec/write tools in contexts where they are unnecessary, increasing accidental misuse risk.
The markdown states support for command execution, file writes, and external API use without prominent user-facing warnings, confirmation requirements, or scope limits. In a skill with declared read/exec/write tools, that omission increases the risk that an agent will perform impactful actions without sufficient transparency or consent.
No suspicious patterns detected.
