Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

portainer

Sterne0

Forks0

Aktualisiert29. Juni 2026 um 20:30

Manage Docker (and Kubernetes) via Portainer's REST API or the official portainer-mcp server — environments/endpoints, stacks, containers/images/networks/volumes, and the Docker API proxy. Load this when the user manages Docker with Portainer rather than Dockhand.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

Redth

Redth/homelab-assist

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	portainer
description	Manage Docker (and Kubernetes) via Portainer's REST API or the official portainer-mcp server — environments/endpoints, stacks, containers/images/networks/volumes, and the Docker API proxy. Load this when the user manages Docker with Portainer rather than Dockhand.

Portainer

Portainer (https://github.com/portainer/portainer) is a mature, well-documented control plane — a good secondary to Dockhand. Obey the homelab-core:homelab-safety skill and load docker-compose-stacks for compose fundamentals.

How to drive it

Official MCP — portainer/portainer-mcp, generated from Portainer's OpenAPI. Match the version to your Portainer (e.g. mcp-portainer~=2.42 ↔ Portainer 2.42.x). Auth via PORTAINER_URL + PORTAINER_API_KEY. Supports a read-only mode — prefer it for inspection. If configured, use it (see plugin .mcp.json).
REST API — full, version-aware, documented at https://docs.portainer.io/api/docs and https://api-docs.portainer.io/. Auth via X-API-Key: <token> header. It can also proxy straight to the underlying Docker/K8s API.

Concepts

Environments / endpoints — each managed Docker (or K8s) host. Operations are scoped to an endpoint ID (analogous to Dockhand's environmentId). Confirm which one.
Edge agents — for remote/NAT hosts (analogous to Hawser Edge).
Stacks — compose stacks managed by Portainer; can be Git-backed (GitOps) — if so, prefer changing in Git and letting Portainer redeploy.

Common tasks

Read: list endpoints, stacks, containers, images, volumes; logs; version/settings.
Significant: create/update/redeploy a stack, pull images, start/stop/restart containers.
Destructive: delete a stack/volume/endpoint, prune — summarize data risk + blast radius, confirm.

Version-matching gotcha

Portainer's API and MCP are version-sensitive. Check the running Portainer version first and use the matching MCP/client version, and verify endpoint shapes against the api-docs for that version (homelab-research). Using a mismatched client version is a common source of confusing failures.

Safety checklist

Confirm endpoint → confirm Git-managed vs not → note image tag/recreate behavior → summarize + approve → verify health after. Prefer the API/MCP over SSH to the host.

Mehr aus diesem Repository

gleiches Repository

dockhand

Redth/homelab-assist

Manage Docker via Dockhand — the preferred control plane in this homelab — and its Hawser remote agents. Covers the Dockhand architecture (central server + Hawser Standard/Edge agents), how to drive it (the mcp-dockhand MCP server or its REST API), compose-stack and container operations, multi-host/environment targeting, and Git-synced stacks. Load this when the user manages Docker with Dockhand.

2026-07-010

docker-compose-stacks

Redth/homelab-assist

Shared foundational knowledge for working with Docker Compose stacks — the compose file format, services/networks/volumes/secrets, environment and .env handling, healthchecks, common operations (up/down/pull/logs/ps), and safe-change practices. Load this for any compose-based work, alongside the control-plane skill (Dockhand/Portainer/Dockge) that actually applies the changes.

2026-06-290

docker-on-proxmox

Redth/homelab-assist

Understand and troubleshoot a Docker host running inside Proxmox — as a VM or as a privileged/unprivileged LXC — and how VLAN networking, macvlan/ipvlan, VLAN-aware bridges, and passed-through/bind-mounted storage interact across the Proxmox and Docker layers. Load this when a Docker networking or storage problem may originate at the Proxmox layer, or when planning how to host Docker on Proxmox.

2026-06-290

docker-overview

Redth/homelab-assist

Entry point and router for managing Docker in a homelab. Load this first for any Docker request — it identifies which control plane is in use (Dockhand preferred, or Portainer/Dockge/raw Engine), establishes the version check, and routes to the right skill (compose stacks, Dockhand, reverse-proxy label routing, or Docker-on-Proxmox networking).

2026-06-290

dockge

Redth/homelab-assist

Manage Docker compose stacks via Dockge — a file-based stack manager that stores stacks as compose files under /opt/stacks. Covers its file-on-disk model, the lack of a REST API/MCP (so operations are filesystem- or SSH-oriented), and how to edit stacks safely. Load this when the user manages Docker with Dockge.

2026-06-290

npm-reverse-proxy

Redth/homelab-assist

Set up and manage domain routing for homelab services using nginx-proxy-manager (NPM) driven by Docker container labels via npm-docker-sync. Load this when the user wants to expose a container/stack at a domain, debug why a service isn't routing, or understand the label-based proxy-host automation pattern. Covers the npm.* label scheme, how sync maps containers to NPM proxy hosts, and SSL/forced-host details.

2026-06-290

name	portainer
description	Manage Docker (and Kubernetes) via Portainer's REST API or the official portainer-mcp server — environments/endpoints, stacks, containers/images/networks/volumes, and the Docker API proxy. Load this when the user manages Docker with Portainer rather than Dockhand.

Portainer

How to drive it

Official MCP — portainer/portainer-mcp, generated from Portainer's OpenAPI. Match the version to your Portainer (e.g. mcp-portainer~=2.42 ↔ Portainer 2.42.x). Auth via PORTAINER_URL + PORTAINER_API_KEY. Supports a read-only mode — prefer it for inspection. If configured, use it (see plugin .mcp.json).
REST API — full, version-aware, documented at https://docs.portainer.io/api/docs and https://api-docs.portainer.io/. Auth via X-API-Key: <token> header. It can also proxy straight to the underlying Docker/K8s API.

Concepts

Environments / endpoints — each managed Docker (or K8s) host. Operations are scoped to an endpoint ID (analogous to Dockhand's environmentId). Confirm which one.
Edge agents — for remote/NAT hosts (analogous to Hawser Edge).
Stacks — compose stacks managed by Portainer; can be Git-backed (GitOps) — if so, prefer changing in Git and letting Portainer redeploy.

Common tasks

Read: list endpoints, stacks, containers, images, volumes; logs; version/settings.
Significant: create/update/redeploy a stack, pull images, start/stop/restart containers.
Destructive: delete a stack/volume/endpoint, prune — summarize data risk + blast radius, confirm.

Version-matching gotcha

Safety checklist

Confirm endpoint → confirm Git-managed vs not → note image tag/recreate behavior → summarize + approve → verify health after. Prefer the API/MCP over SSH to the host.