.claude/skills/multi-cloud-architect/SKILL.md
--- name: multi-cloud-architect description: Design and implement portable Kubernetes infrastructure across cloud providers. Use for Terraform/IaC, Kustomize overlays, provider-agnostic patterns, and cloud migrations. Keywords: multi-cloud, AWS, Azure, GCP, Oracle, Terraform, Kustomize, portability, migration. --- # Multi-Cloud Architect Expert in designing portable Kubernetes infrastructure that can run on any cloud provider (Oracle, Azure, AWS, GCP) or on-premises with minimal changes. ## W
npx skillsauth add adask-b/agent-ready-k8s .claude/skills/multi-cloud-architectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Expert in designing portable Kubernetes infrastructure that can run on any cloud provider (Oracle, Azure, AWS, GCP) or on-premises with minimal changes.
+--------------------------------------------------+
| Applications |
+--------------------------------------------------+
| clusters/base/ (Provider-agnostic) |
+--------------------------------------------------+
| clusters/overlays/<provider>/ (Specific) |
+--------------------------------------------------+
| Terraform/IaC (Per-Provider) |
+--------------------------------------------------+
| AWS EKS | Azure AKS | GCP GKE | Oracle OCI |
+--------------------------------------------------+
Golden Rule: Everything in base/ must work on ALL providers. Provider-specific config ONLY in overlays/.
| Component | Base (All) | Oracle/On-Prem | Azure | AWS | GCP |
|-----------|------------|----------------|-------|-----|-----|
| Ingress Controller | NGINX Ingress | NGINX | NGINX | NGINX or ALB | NGINX or GCE |
| Load Balancer | Service type | MetalLB | Azure LB | AWS NLB/ALB | GCP LB |
| Storage Class | standard | Longhorn | Azure Disk CSI | EBS CSI | GCE-PD CSI |
| Secrets Backend | ESO CRDs | HashiCorp Vault | Azure Key Vault | Secrets Manager | Secret Manager |
| DNS Provider | ExternalDNS | Cloudflare | Azure DNS | Route53 | Cloud DNS |
| Cert Manager | cert-manager | Let's Encrypt | Let's Encrypt | ACM* | Let's Encrypt |
| Workload Identity | ServiceAccount | Vault JWT | Azure AD WI | IRSA | GKE WI |
| CNI | - | Cilium/Calico | Azure CNI | VPC CNI | Dataplane V2 |
| Registry | GHCR | GHCR/Harbor | ACR | ECR | GAR |
*ACM for AWS-native, cert-manager for portability
clusters/
├── base/ # Provider-agnostic
│ ├── kustomization.yaml
│ ├── namespaces/
│ │ └── demo-platform.yaml
│ ├── ingress/
│ │ └── nginx-config.yaml # Generic NGINX config
│ ├── storage/
│ │ └── storageclass.yaml # Abstract StorageClass
│ └── secrets/
│ └── external-secrets.yaml # ESO CRDs (no provider)
│
└── overlays/
├── kind/ # Local development
│ ├── kustomization.yaml
│ └── patches/
│ ├── ingress-nodeport.yaml
│ └── storage-local-path.yaml
│
├── oracle/ # Oracle Cloud Free Tier
│ ├── kustomization.yaml
│ └── patches/
│ ├── metallb-config.yaml
│ ├── longhorn-storage.yaml
│ └── vault-secretstore.yaml
│
├── azure/ # Azure AKS
│ ├── kustomization.yaml
│ └── patches/
│ ├── azure-disk-storage.yaml
│ ├── keyvault-secretstore.yaml
│ └── azure-dns-external.yaml
│
├── aws/ # AWS EKS
│ ├── kustomization.yaml
│ └── patches/
│ ├── ebs-storage.yaml
│ ├── secretsmanager-store.yaml
│ └── route53-external.yaml
│
└── gcp/ # GCP GKE
├── kustomization.yaml
└── patches/
├── gce-pd-storage.yaml
├── secretmanager-store.yaml
└── clouddns-external.yaml
infra/terraform/
├── modules/
│ ├── cluster/
│ │ ├── main.tf # Generic cluster interface
│ │ ├── variables.tf
│ │ ├── outputs.tf
│ │ └── providers/
│ │ ├── aks.tf # Azure implementation
│ │ ├── eks.tf # AWS implementation
│ │ ├── gke.tf # GCP implementation
│ │ └── oci.tf # Oracle implementation
│ │
│ ├── network/
│ │ ├── main.tf
│ │ └── providers/
│ │ ├── azure-vnet.tf
│ │ ├── aws-vpc.tf
│ │ ├── gcp-vpc.tf
│ │ └── oci-vcn.tf
│ │
│ └── dns/
│ ├── main.tf
│ └── providers/
│ ├── azure-dns.tf
│ ├── route53.tf
│ ├── clouddns.tf
│ └── cloudflare.tf
│
└── envs/
├── oracle-free/
│ ├── main.tf
│ ├── terraform.tfvars
│ └── backend.tf
├── azure-dev/
├── azure-prod/
├── aws-dev/
└── gcp-dev/
# CRITICAL: All images MUST support ARM64
image:
# Use multi-arch images or build for linux/arm64
repository: ghcr.io/your-org/app
tag: v1.0.0@sha256:... # Always pin by digest
# Resources are limited (24 GB RAM total, 4 OCPUs)
resources:
requests:
memory: "256Mi"
cpu: "100m"
limits:
memory: "512Mi"
cpu: "500m"
# Enable workload identity
resource "azurerm_kubernetes_cluster" "main" {
workload_identity_enabled = true
oidc_issuer_enabled = true
}
# IRSA for workload identity
module "irsa" {
source = "terraform-aws-modules/iam/aws//modules/iam-role-for-service-accounts-eks"
}
resource "google_container_cluster" "main" {
workload_identity_config {
workload_pool = "${var.project}.svc.id.goog"
}
}
When migrating between providers:
Images
Storage
Secrets
Networking
Identity
latest tags anywheredevelopment
--- name: security-compliance-guard description: Implement zero-trust security, secrets management, and compliance. Use for Vault, ESO, Kyverno, OPA, Pod Security, RBAC, and supply chain security. Keywords: security, secrets, Vault, ESO, Kyverno, OPA, RBAC, compliance, SBOM, Cosign. --- # Security & Compliance Guard Expert in implementing zero-trust security posture, secrets management, and compliance controls for Kubernetes environments. ## When to Use This Skill - Setting up secrets manage
testing
--- name: observability-engineer description: Design and implement observability stack with metrics, logs, and traces. Use for Prometheus, Grafana, Loki, Tempo, OpenTelemetry, alerting, and SLO/SLI design. Keywords: observability, monitoring, tracing, Prometheus, Grafana, Loki, Tempo, OpenTelemetry, OTEL, alerting, SLO, SLI. --- # Observability Engineer Expert in designing and implementing comprehensive observability solutions for Kubernetes environments. Covers the three pillars: metrics, log
testing
--- name: k8s-platform-expert description: Complete Kubernetes platform expertise - deployment, security hardening, and systematic troubleshooting. Use for workload deployment, Helm charts, RBAC, NetworkPolicies, incident response, and diagnostics. Keywords: Kubernetes, K8s, kubectl, Helm, RBAC, troubleshooting, incident response, GitOps. --- # Kubernetes Platform Expert A comprehensive Kubernetes skill combining deployment expertise with systematic troubleshooting capabilities. Covers the ful
tools
--- name: gitops-pipeline-master description: Design and implement GitOps workflows with ArgoCD and CI/CD pipelines. Use for GitHub Actions, image promotion, rollout strategies, and deployment automation. Keywords: GitOps, ArgoCD, CI/CD, GitHub Actions, deployment, rollout, canary, blue-green. --- # GitOps Pipeline Master Expert in designing GitOps-based deployment workflows with Argo CD and CI/CD automation. ## When to Use This Skill - Setting up Argo CD Applications and ApplicationSets - D