podman-tool

Wraps the Podman CLI to return structured TOON output for container, image, pod, and machine management.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/vinzenz/workflows --skill podman-tool-vinzenz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: podman-tool
Source: https://github.com/vinzenz/workflows/tree/main/.agents/skills/podman-tool
Command: npx skills add https://github.com/vinzenz/workflows --skill podman-tool-vinzenz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running raw podman commands forces agents to parse human-shaped output, re-read help text, and guess at next steps. This Skill wraps the Podman CLI and returns structured TOON output with explicit counts, stable key sets, runnable next-step suggestions, and machine-readable error codes an agent can branch on. ## Core Features & Use Cases - Container lifecycle management: list, inspect, run, stop, and remove containers, plus build, pull, tag, and prune images across pods, volumes, networks, and secrets. - Safe mutations: every write subcommand supports --dry-run with a would_* preview block, and secret create only accepts --from-file or --from-env so values never appear in process arguments. - Connection and machine management: resolve connections via flag, environment variables, or local socket, and inspect or start podman machines on macOS and Windows. - Use Case: An agent needs to deploy a test stack. It runs podman-tool container run nginx:latest --name web -p 8080:80 --dry-run to preview the mutation, then executes it and reads the help: block for the exact inspect and logs commands to run next. ## Quick Start Ask the agent to list running containers with podman-tool and follow the suggested next-step commands in the output's help block.

Frequently Asked Questions about podman-tool

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Podman containers from an AI agent?▼

Use podman-tool instead of raw podman commands. It wraps container list, inspect, run, stop, and remove operations and returns structured TOON output with counts and suggested next commands, so the agent never parses human-formatted text.

How do I preview a destructive podman command before running it?▼

Every write subcommand in podman-tool accepts `--dry-run`, which makes zero mutating calls and returns `dry_run: true` with a `would_*` block describing the planned action. Use it before rm, prune, or run operations.

Can podman-tool connect to a remote podman machine?▼

Yes. Pass `-c/--connection <name>` or `--url <uri>` with `--identity <key>`, or set the CONTAINER_CONNECTION or CONTAINER_HOST environment variables. Without any of these, commands target the local rootless socket.

How do I create a podman secret without exposing the value?▼

Use `podman-tool secret create --name <name> --from-env VAR` or `--from-file <path>`. The secret value never appears in the process argument list, preventing leakage through shell history or process inspection.

When should I use raw podman instead of podman-tool?▼

Use plain podman for operations the tool deliberately does not wrap: podman login, podman compose, interactive attach, podman cp to the host filesystem, and unbounded streaming like logs -f. For anything else, `podman-tool raw -- <args>` is the escape hatch.