Inspect containers, logs, and images via podman
Security Analysis
high confidenceThe skill's stated purpose (inspect containers via podman) is plausible, but the runtime instructions reference a `docker-ctl` CLI that is nowhere provided or declared, creating an incoherent and potentially non-functional skill.
Name/description claim container inspection via podman which is reasonable, and the metadata lists podman as a required binary — but the SKILL.md examples all call a `docker-ctl` command (docker-ctl ps/logs/images/inspect). There is no code or install step that provides a docker-ctl wrapper, and docker-ctl is not declared as a required binary. This mismatch suggests the skill won't work as described or the documentation is incorrect.
The SKILL.md tells the agent to run `docker-ctl ...` commands. Because this is an instruction-only skill with no code files or install steps, there is no guidance for how `docker-ctl` maps to the declared `podman` binary. The instructions do not include direct podman commands (podman ps, podman logs, etc.) and do not reference other system files or credentials.
No install spec and no code files — lowest risk from an install perspective. However, the absence of an install means there is no implementation provided for the `docker-ctl` commands shown in the docs; that makes the skill non-functional unless the environment already supplies a docker-ctl binary or alias.
The skill requests no environment variables, no credentials, and no config paths — proportional for a read-only inspection tool.
The skill does not request always:true and is user-invocable only. It does not ask to modify other skills or system-wide settings.
Guidance
Do not install or enable this skill until its documentation is fixed. Ask the author to clarify whether the skill should call podman directly (e.g., `podman ps`, `podman logs <container>`, `podman images`, `podman inspect <container>`) or to include/install a `docker-ctl` wrapper binary. If the environment already exposes a `docker-ctl` command, confirm what it does and whether it simply proxies to podman. The current mismatch means the skill is likely non-functional and the docs are inconsistent — this is suspicious but not necessarily malicious.
Latest Release
v1.0.0
Initial publish
More by @Xejrax
Published by @Xejrax on ClawHub
