Security audit
Security checks for vulnerabilities and agentic risk
This skill appears to be a container operations helper, but it asks for command and write authority while giving broad and inconsistent guidance about what it may change.
Review this skill before installing in an environment with real containers or production credentials. It should be treated as capable of running Podman/system commands and writing files, not merely inspecting logs and images; use it only where those actions are acceptable and require explicit user direction for builds, starts, deployments, or other changes.
The skill prominently uses Chinese in the display name and summaries, and much of the operational guidance is presented in Chinese without stating that users may choose another language. This creates a locale/language constraint that is not documented as optional or justified as region-specific.
The activation guidance is broad and ambiguous, encouraging use for general monitoring, logging, alerting, and deployment management without clear boundaries. For a skill that includes exec and write tools, vague triggers increase the risk of accidental invocation in contexts where users expected analysis only, potentially leading to unreviewed command execution or system modification.
The skill’s documentation materially understates its capabilities: it claims to only inspect containers, logs, and images, but elsewhere describes management actions such as building images, starting containers, and operational command execution. This mismatch can cause an agent or user to invoke a skill with a lower perceived risk profile than it actually has, increasing the chance of unintended system changes.
The FAQ says the skill directly executes Podman commands, which contradicts the narrower manifest description of mere inspection. In a skill with exec/write permissions, this discrepancy is security-relevant because reviewers and users may underestimate the operational reach of the skill and approve broader access than intended.
The skill advertises file writing and command execution but does not provide a prominent warning about system-impacting behavior. In an operations/container context, these capabilities can alter images, containers, files, and runtime state, so presenting them as routine automation without clear risk disclosures increases the chance of harmful or unauthorized changes.
The documentation asserts security properties like encrypted communication and access control without any implementation evidence in the skill file. Unsupported security claims can create false trust, leading operators to rely on protections that may not actually exist when handling logs, container metadata, or credentials.
No suspicious patterns detected.
