Kubernetes Architect
CheckedDesigns, deploys, and optimizes Kubernetes clusters on various cloud platforms based on your specified requirements.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add rmyndharis/antigravity-skills --skill kubernetes-architect -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
rmyndharis
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned rmyndharis/antigravity-skills at 3eff4af253.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 3eff4af253
- Scanned
- 1 file, 171 lines
About this skill
What it does
This skill enables an AI agent to act as a Kubernetes architect specializing in cloud-native infrastructure and modern GitOps workflows. It can design, deploy, and optimize Kubernetes clusters across various platforms including AWS (EKS), Azure (AKS), Google Cloud (GKE), and on-premises environments. The agent leverages expertise in enterprise container orchestration at scale to build scalable, secure, and cost-effective solutions for enhanced developer productivity.
When to use it
- Designing a Kubernetes platform architecture or multi-cluster strategy.
- Implementing GitOps workflows and progressive delivery pipelines.
- Planning service mesh, security, or multi-tenancy patterns within your Kubernetes environment.
- Improving the reliability, cost efficiency, or developer experience of existing Kubernetes deployments.
Key capabilities
- Kubernetes Platform Expertise: EKS, AKS, GKE, Red Hat OpenShift, Rancher, VMware Tanzu, kubeadm, kops, kubespray, and bare-metal installations.
- GitOps & Continuous Deployment: ArgoCD, Flux v2, Jenkins X, Tekton, progressive delivery strategies (canary deployments, blue/green), and GitOps repository patterns.
- Modern Infrastructure as Code: Helm 3.x, Kustomize, Jsonnet, cdk8s, Pulumi Kubernetes provider, Terraform/OpenTofu modules, and Open Policy Agent (OPA).
- Cluster Lifecycle Management: Upgrades, node management, etcd operations, backup/restore strategies.
Example prompts
- "Design a multi-cluster Kubernetes strategy for our application across AWS EKS and Azure AKS."
- "Recommend GitOps tools and best practices to implement progressive delivery for our microservices."
- "How can we improve the security posture of our existing GKE cluster using Policy as Code?"
Tips & gotchas
- Requirement Gathering: Be prepared to provide workload requirements, compliance needs, and scale targets for optimal results.
- Staging is Key: Always test policy changes and admission controls in a staging environment before applying them to production.
- Rollback Plans: Ensure you have rollback plans defined before making any changes to your Kubernetes clusters.