Portainer

**Judgement** Well-designed, focused skill for managing Docker infrastructure via Portainer’s REST API. It exposes the most important operational actions (status, endpoints, container lifecycle, stacks, git-based redeploys, logs) through a simple CLI wrapper that aligns well with AI-driven automation. Suitable for small to medium setups that already use Portainer 2.x. **Key Capabilities** - Check Portainer server and endpoint status. - List and control containers (start/stop/restart). - List and inspect stacks, including git configuration. - Trigger stack redeploys from git repositories. - View container logs with line limits. **Risks & Limitations** - **Operational impact**: The skill can stop/restart containers and redeploy stacks; misuse or bad instructions can cause production downtime. It should only be enabled for trusted agents and environments. - **Scope of access**: API token grants whatever permissions are configured in Portainer; the skill itself doesn’t add extra access control or guardrails. - **Configuration sensitivity**: Misconfigured `PORTAINER_URL` or `PORTAINER_API_KEY` will break functionality; token leakage would expose infrastructure control. - **Portainer dependency**: Only useful where Portainer 2.x is deployed and reachable; not a generic Docker CLI replacement. **Recommended Scenarios** - Teams already running Portainer who want an AI agent to help with day-to-day Docker operations (restarts, log checks, simple redeploys). - Home-lab or small production environments where quick, scripted Portainer management is acceptable and risk is controlled. - Workflows where code changes are deployed via Portainer-managed stacks backed by git, and automated “redeploy from git + check logs” flows are valuable. **Not Ideal For** - Environments requiring strict change management or fine-grained RBAC at the skill level. - Users who do not already use Portainer or cannot expose the Portainer API with tokens safely.