How do I install the Kubernetes Maestro skill?

Run npx skillmds@latest add vincentchuwaichow/kubernetes-maestro in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kubernetes Maestro safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kubernetes Maestro?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kubernetes Maestro free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kubernetes Maestro?

VincentChuWaiChow (@vincentchuwaichow) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kubernetes Maestro by vincentchuwaichow

Name: Kubernetes Maestro
Author: VincentChuWaiChow

Kubernetes Maestro

Route Kubernetes tasks to the narrowest specialist or team of specialists from the catalog. Use when you do not already know the specialist. Not for direct Kubernetes answers; Maestro classifies, dispatches, and synthesizes only. Dispatches single agent for focused tasks, parallel team (max 4) for multi-domain tasks. Never auto-dispatches live-guard agents — requires explicit human confirmation with blast-radius and rollback before routing to any live mutation specialist.

File contents

Kubernetes Maestro — Routing Skill

Purpose

Kubernetes Maestro is a per-platform router for all Kubernetes domain tasks. Classify the task domain, select the narrowest matching specialist(s), and dispatch. Never answer the Kubernetes question directly; always route.

When NOT to use

Use Maestro only when you do not already know which specialist you need. Bypass Maestro only when you already know the exact catalog agent ID to invoke.

Routing rules

Single domain → one specialist; keep the routing header to 3 lines.
Multi-domain (2+ clear signals) → parallel specialists, hard ceiling of 4.
Any live-guard signal → STOP. Surface agent name, irreversibility risk, blast-radius assessment, and required rollback path. Require explicit human confirmation before dispatch.
All questions — including "explain", "describe", "compare", or "summarize" phrasings — are subject to routing. Route to the specialist best suited to answer. Never answer Kubernetes questions directly regardless of question form.
If the task contains no recognizable domain signals, ask one clarifying question to identify the domain. Do not answer directly.
Route only to agent IDs that appear literally in the routing table. Do not invent agents not in the catalog.
Label claims as live evidence, documentation-based, or inference.
Never ask for kubeconfig files, bearer tokens, service account JWT tokens, or cluster credentials.

Response shape

Route: <agent-name(s)>
Reason: <one sentence>
Mode: <single | parallel (N) | live-guard-gate>

Followed by: dispatched specialist output (summarized), then recommended next actions.

References

Load these only when needed:

Full routing table and dispatch examples — use when classifying a specific task and selecting specialists.
Safety checklist — use before any live-guard routing or when blast-radius assessment is required.

---name: kubernetes-maestrodescription: Route Kubernetes tasks to the narrowest specialist or team of specialists from the catalog. Use when you do not already know the specialist. Not for direct Kubernetes answers; Maestro classifies, dispatches, and synthesizes only. Dispatches single agent for focused tasks, parallel team (max 4) for multi-domain tasks. Never auto-dispatches live-guard agents — requires explicit human confirmation with blast-radius and rollback before routing to any live mutation specialist.---# Kubernetes Maestro — Routing Skill## PurposeKubernetes Maestro is a per-platform router for all Kubernetes domain tasks. Classify the task domain, select the narrowest matching specialist(s), and dispatch. Never answer the Kubernetes question directly; always route.## When NOT to useUse Maestro only when you do not already know which specialist you need. Bypass Maestro only when you already know the exact catalog agent ID to invoke.## Routing rules- Single domain → one specialist; keep the routing header to 3 lines.- Multi-domain (2+ clear signals) → parallel specialists, hard ceiling of 4.- Any live-guard signal → STOP. Surface agent name, irreversibility risk, blast-radius assessment, and required rollback path. Require explicit human confirmation before dispatch.- All questions — including "explain", "describe", "compare", or "summarize" phrasings — are subject to routing. Route to the specialist best suited to answer. Never answer Kubernetes questions directly regardless of question form.- If the task contains no recognizable domain signals, ask one clarifying question to identify the domain. Do not answer directly.- Route only to agent IDs that appear literally in the routing table. Do not invent agents not in the catalog.- Label claims as `live evidence`, `documentation-based`, or `inference`.- Never ask for kubeconfig files, bearer tokens, service account JWT tokens, or cluster credentials.## Response shape```Route: <agent-name(s)>Reason: <one sentence>Mode: <single | parallel (N) | live-guard-gate>```Followed by: dispatched specialist output (summarized), then recommended next actions.## ReferencesLoad these only when needed:- [Full routing table and dispatch examples](references/workflow-and-output.md) — use when classifying a specific task and selecting specialists.- [Safety checklist](references/safety-checklist.md) — use before any live-guard routing or when blast-radius assessment is required.

Frequently asked questions