メニュー
Swarm Mesh Provisioner atomic skill. Initializes Docker Swarm Mode, manages manager/worker nodes join processes, and provisions global Swarm Overlay networks using container-manager-mcp.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Snapshot a host's Docker/Podman/Swarm inventory into the epistemic-graph knowledge graph as typed OWL nodes via the container-manager-mcp MCP server — containers, images, volumes, networks, swarm services and nodes, with their :usesImage / :runsOn / :builtFrom links. Use when the agent must record live container state into the KG for cross-source reasoning, drift detection, or provenance. Do NOT use for operating containers (use container-manager-lifecycle) or managing swarm services (use container-manager-swarm).
End-user setup guide for the container-manager-mcp MCP server — choosing CONTAINER_MANAGER_TYPE (docker/podman/kubernetes/multi), wiring .env / mcp_config toggles, connecting remote Docker/Podman hosts via the tunnel-manager inventory versus remote Kubernetes clusters via kubeconfig contexts, and a first-run verification checklist. Use when the agent is onboarding a new environment or troubleshooting "which skill do I even use" before touching any other container-manager-mcp skill. Do NOT use for actually operating containers/clusters once configured — use the operational skills.
Full operational Kubernetes surface via the container-manager-mcp MCP server — workloads (pods/rollouts/StatefulSets/DaemonSets/ReplicaSets/Jobs/CronJobs), config (ConfigMaps/Secrets/Namespaces/CRDs/patch), networking (Ingress/native Services/NetworkPolicy/DNS), storage (PV/PVC/StorageClass/snapshots/CSI), RBAC (roles/bindings/tokens/access reviews/pod security), cluster (nodes/contexts/ CSRs/admission plugins), governance (quotas/limits/PDB/HPA), and observability (metrics/watch/debug). Use when the agent must drive real k8s migrations, sustain, or ops work on a cluster. Do NOT use for Docker/Podman single-host lifecycle (container-manager-lifecycle), Docker Swarm (container-manager-swarm), or rootless Podman pods (container-manager-podman-operations).
Operate several container backends and contexts at once — Kubernetes, Docker, Podman, and Swarm — via the container-manager-mcp MCP server's cm_multi_context tool, with per-call backend/context selection and parallel fan-out across a configured pool of contexts. Use when the agent must compare, migrate between, or simultaneously act on multiple clusters/engines/hosts. Do NOT use for single-backend operations, which are cheaper via the themed skills (container-manager-lifecycle / -swarm / -kubernetes-operations / -podman-operations).
Rootless Podman pod/kube operations via the container-manager-mcp MCP server — pods (create/list/stats/top/inspect/logs/stop/rm), Kubernetes YAML interop (generate/play kube), checkpoint/restore, pod-scoped networks and volumes, health checks, and system prune. Use when the agent must drive Podman pod-level workloads beyond single containers. Do NOT use for single-container Docker/Podman lifecycle (container-manager-lifecycle) or for a real Kubernetes cluster (container-manager-kubernetes-operations).
Kubernetes Mesh Provisioner atomic skill. Stands up an RKE2 cluster (server + agents) with Cilium CNI and the NVIDIA GPU device plugin, the Kubernetes parallel of swarm-mesh-provisioner. Idempotent — re-runnable.
| name | swarm-mesh-provisioner |
| skill_type | skill |
| description | Swarm Mesh Provisioner atomic skill. Initializes Docker Swarm Mode, manages manager/worker nodes join processes, and provisions global Swarm Overlay networks using container-manager-mcp. |
| domain | infrastructure |
| tags | ["swarm","docker","overlay-net","cluster"] |
| requires | ["container-manager-mcp","tunnel-manager-mcp"] |
Stateless atomic operation to establish multi-node container orchestration clusters and secure virtual networks.
container-manager-mcp — for executing Swarm init, join, network, and node operations.tunnel-manager-mcp — for running command execution on worker nodes.On the target Manager node, verify Swarm status. If inactive:
docker swarm init specifying advertise address.For each designated worker node listed in the inventory:
Create a secure, encrypted overlay network (e.g., overlay-net) to bridge containers across different hardware hosts:
--attachable to support dynamic containers.Confirm that all node statuses read Ready and state shows Active on the Swarm manager.