kubernetes-specialist

Name: kubernetes-specialist
Author: 404kidwiz

github.com/404kidwizCloud & DevOps113 installs

About kubernetes-specialist

A Kubernetes-focused skill for production cluster design, deployment, operations, and security. It is intended for teams planning or troubleshooting Kubernetes environments, with checklists and decision guidance across these tasks.

Key features

01Production cluster architecture planning
02Helm, operators, and GitOps workflows
03Networking, storage, and performance troubleshooting
04Upgrade and multi-cluster strategies
05Resource, security, and observability checks

Use cases

01Plan cluster architecture for production workloads
02Develop Kubernetes upgrade or multi-cluster plans
03Troubleshoot cluster networking, storage, or performance

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/404kidwiz/claude-supercode-skills --skill kubernetes-specialist

After installing, type/kubernetes-specialistin Claude Code to confirm it loaded.

Bundled filesEXAMPLES.mdREFERENCE.md

Details

From the project README

Kubernetes Specialist

Purpose

Provides expert Kubernetes orchestration and cloud-native application expertise with deep knowledge of container orchestration, cluster management, and production-grade deployments. Specializes in Kubernetes architecture, Helm charts, operators, multi-cluster management, and GitOps workflows across EKS, AKS, GKE, and on-premises deployments.

When to Use

Designing Kubernetes cluster architecture for production workloads
Implementing Helm charts, operators, or GitOps workflows (ArgoCD, Flux)
Troubleshooting cluster issues (networking, storage, performance)
Planning Kubernetes upgrades or multi-cluster strategies
Optimizing resource utilization and cost in Kubernetes environments
Setting up service mesh (Istio, Linkerd) and observability
Implementing Kubernetes security and RBAC policies

Quick Start

Invoke this skill when:

Designing Kubernetes cluster architecture for production workloads
Implementing Helm charts, operators, or GitOps workflows
Troubleshooting cluster issues (networking, storage, performance)
Planning Kubernetes upgrades or multi-cluster strategies
Optimizing resource utilization and cost in Kubernetes environments

Do NOT invoke when:

Simple Docker container needs (use docker commands directly)
Cloud infrastructure provisioning (use cloud-architect instead)
Application code debugging (use backend-developer/frontend-developer)
Database-specific issues (use database-administrator instead)

Decision Framework

Deployment Strategy Selection

├─ Zero downtime required?
│   ├─ Instant rollback needed → Blue-Green Deployment
│   │   Pros: Instant switch, easy rollback
│   │   Cons: 2x resources during deployment
│   │
│   ├─ Gradual rollout → Canary Deployment
│   │   Pros: Test with subset of traffic
│   │   Cons: Complex routing setup
│   │
│   └─ Simple updates → Rolling Update (default)
│       Pros: Built-in, no extra resources
│       Cons: Rollback takes time
│
├─ Stateful application?
│   ├─ Database → StatefulSet + PVC
│   │   Pros: Stable network IDs, ordered deployment
│   │   Cons: Complex scaling
│   │
│   └─ Stateless → Deployment
│       Pros: Easy scaling, self-healing
│
└─ Batch processing?
    ├─ One-time → Job
    ├─ Scheduled → CronJob
    └─ Parallel processing → Job with parallelism

Resource Configuration Matrix

Workload Type	CPU Request	CPU Limit	Memory Request	Memory Limit
Web API	100m-500m	1000m	256Mi-512Mi	1Gi
Worker	500m-1000m	2000m	512Mi-1Gi	2Gi
Database	1000m-2000m	4000m	2Gi-4Gi	8Gi
Cache	100m-250m	500m	1Gi-4Gi	8Gi
Batch Job	500m-2000m	4000m	1Gi-4Gi	8Gi

Node Pool Strategy

Use Case	Instance Type	Scaling	Cost
System pods	t3.large (3 nodes)	Fixed	Low
Applications	m5.xlarge	Auto 3-20	Medium
Batch/Spot	m5.large-2xlarge	Auto 0-50	Very Low
GPU workloads	p3.2xlarge	Manual	High

Red Flags → Escalate

STOP and escalate if:

Cluster upgrade with breaking API changes (deprecated versions)
Multi-region active-active requirements
Compliance requirements (PCI-DSS, HIPAA) need validation
Custom scheduler or controller development needed
etcd corruption or cluster state issues

Quality Checklist

Cluster Configuration

Multi-AZ deployment (nodes spread across availability zones)
Node autoscaling configured (Cluster Autoscaler or Karpenter)
System node pool with taints (separate critical addons from apps)
Encryption enabled (secrets at rest with KMS)
Audit logging enabled (API server logs)

Security

Pod Security Standards enforced (restricted or baseline)
Network policies configured (default deny + explicit allow)
RBAC configured (least privilege for all service accounts)
Image scanning enabled (scan for vulnerabilities)
Private container registry configured

Resource Management

All pods have resource requests and limits
HorizontalPodAutoscalers configured for scalable workloads
PodDisruptionBudgets defined (prevent too many pods down)
ResourceQuotas set per namespace
LimitRanges defined (default limits for pods)

High Availability

Deployments have ≥2 replicas
Anti-affinity rules prevent pod co-location
Readiness and liveness probes configured
PodDisruptionBudgets allow for rolling updates
Multi-region cluster (if global scale required)

Observability

Metrics server installed (kubectl top works)
Prometheus monitoring application metrics
Centralized logging (CloudWatch, Elasticsearch, Loki)
Distributed tracing (Jaeger, Tempo)
Dashboards for cluster and application health

Disaster Recovery

Velero installed for cluster backups
Backup schedule configured (daily minimum)
Restore tested (annual drill)
etcd backups automated (cloud-managed clusters)

Additional Resources

Detailed Technical Reference: See REFERENCE.md
Code Examples & Patterns: See EXAMPLES.md

Comments

Markdown supported

Details

Author: 404kidwiz
Repository: 404kidwiz/claude-supercode-skills
Category: Cloud & DevOps
Installs: 113

Report

More skills

All skills

lark-apps

open.feishu.cn

743.6k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

wizard

github.com/mattpocock

580.6k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-prepare

github.com/microsoft

574.6k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

azure-ai

github.com/microsoft

573.9k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.