portainer

How to drive the Portainer MCP server's tools correctly — both reading and mutating. Reading: project responses with `select` (JMESPath), where the heavy fields live (snapshots, status blocks, managed fields), how to handle non-JSON Docker/K8s proxy endpoints (container and pod logs, stats, exec), and how to interpret results that are easy to misread (e.g. an edge environment's health comes from its heartbeat, not its `Status` field; typed K8s tools use different field names than the raw proxy). Mutating: deploying, scaling, restarting, and deleting Portainer-managed resources — where success payloads are empty and must be verified out-of-band, and where cleanup (orphaned volumes) and recovery (name-based vs id-based calls) have gotchas. Trigger this whenever you're about to call any Portainer MCP tool — including `docker_proxy`, `kubernetes_proxy`, `EndpointList`, `GetAllKubernetes*`, `StackList`, `StackCreateKubernetes*`, `StackDelete*`, `CreateKubernetes*`, `snapshot*`, `Helm*`, or any other `mcp__portaine

How to cut a portainer-mcp release that bumps the embedded Portainer OpenAPI spec to a new Portainer minor (e.g. 2.41.x → 2.42.x). Walks through finding the upstream patch target, regenerating the spec, recounting ops/tags per profile, refreshing the orphan-tag inventory, bumping version pins across the README and distribution docs, promoting CHANGELOG entries, committing, pushing, merging to main, and tagging — in that order. Trigger this skill whenever the user mentions cutting a release, bumping the Portainer version target, supporting a new Portainer minor, regenerating the spec, running `make specs` for a new minor, or any phrasing like "let's update for Portainer X.Y" — the spec regen is only the first step of a multi-file release and the model should consult this skill before touching anything.

Cut a new SDK release for client-api-go. Rotates the [Unreleased] section in CHANGELOG.md to a versioned section, bumps VERSION in Makefile and the install examples in README.md, commits, and creates a local git tag. Does NOT push and does NOT regenerate the swagger client (run `make generate-client VERSION=X.Y.Z` separately, beforehand). Invoked as `/release X.Y.Z` or `/release vX.Y.Z`.

How to drive the Portainer REST API correctly from curl or any plain-HTTP client using an API token — authentication with X-API-Key, the undocumented Docker/Kubernetes proxy surface, resolving environment IDs, deploying and managing stacks, keeping huge responses out of context with jq, and reading results correctly (edge agent health comes from check-in time, not Status). Use this whenever the task involves calling Portainer over HTTP — curl commands, bash/Python/Ansible automation, generated scripts, webhooks, or debugging a failing Portainer API call — even if the user doesn't say "Portainer API" explicitly. Do NOT use it when Portainer MCP tools (mcp__portainer__*) are available in the session — prefer those tools instead.

Add new applications to or update existing applications in the Portainer Industrial App Portal (PIAP) catalog. Use this skill whenever the user wants to add a new app to the catalog, update an existing catalog entry, create a new variant for an app, modify app metadata or configuration, or work with catalog.yaml in any way. Also trigger when the user pastes or references a docker-compose.yml file and wants to turn it into a catalog entry. Trigger on phrases like "add app to catalog", "new catalog entry", "update the catalog", "add a variant", "onboard an application", "register an app", "I have this compose file", or any mention of editing catalog.yaml or any sibling `*.yaml` catalog file for app management purposes.