Menu
Comprehensive AWS/EKS infrastructure health assessment
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Collaborate with other AI agents (Kiro CLI, the peer host CLI, and Agy) for a second opinion. Multi-AI review of code/architecture, decision support when you're unsure, and ADR co-authoring, plus autonomous consensus/harness pipelines. The current host chairs and synthesizes the final answer. 멀티 AI 협업: 리뷰, 의사결정 보조, ADR 협업.
Claude plans and verifies, Kiro CLI implements on its own flat-rate subscription credits — a cost-savings implementation-delegation workflow, not a second opinion (see co-agent for that). Kiro implements inside an isolated git worktree; only the captured, scope-guarded diff ever reaches the main tree. Triggers on 'kiro한테 시켜서 구현', 'kiro로 구현', 'kiro한테 구현 위임', 'delegate implementation to kiro', 'kiro implement this'. For read-only review of a diff, use the /kiro:review command instead — this skill is write-capable (it commits) and deliberately does NOT own review triggers.
AWS Workshop Studio 프로젝트 구조 생성 및 콘텐츠 작성 스킬. "워크샵 만들어", "workshop init", "랩 작성" 요청 시 활성화
After creating a PR, poll for AI and human review feedback, auto-fix issues, and push (max 3 iterations)
Create a single-page, responsive online brochure (landing page) for an AWS solution, product, or platform as one self-contained HTML file — editorial design, hero + value + features + embedded architecture diagram + CTA, deployed publicly via GitHub Pages. Use whenever the user wants a brochure, landing page, marketing one-pager, product overview page, solution showcase, '온라인 브로셔', '브로셔 만들어', '랜딩 페이지', '소개 페이지', or wants to present a cloud product's value and architecture on the web — even if they don't say the word 'brochure'. Not for slide decks (use reactive-presentation) or multi-page docs sites (use gitbook).
Create dynamic animated SVG diagrams with SMIL animations for AWS architecture traffic flow, service interactions, and deployment pipelines. Use when creating animated or dynamic diagrams.
| name | ops-health-check |
| description | Comprehensive AWS/EKS infrastructure health assessment |
| triggers | ["health check","상태 점검","헬스체크","cluster health","인프라 점검"] |
| model | sonnet |
| allowed-tools | ["Bash","Read","Grep"] |
Comprehensive infrastructure health assessment covering cluster, nodes, workloads, networking, storage, and security.
kubectl cluster-info
aws eks describe-cluster --name $CLUSTER_NAME --query 'cluster.{status:status,version:version,platformVersion:platformVersion}'
kubectl get componentstatuses 2>/dev/null
kubectl get nodes -o wide
kubectl top nodes
kubectl get nodes -o json | jq '.items[] | {name:.metadata.name, ready:[.status.conditions[] | select(.type=="Ready") | .status][0], cpu:.status.allocatable.cpu, memory:.status.allocatable.memory}'
kubectl get pods -A --field-selector=status.phase!=Running,status.phase!=Succeeded | head -20
kubectl get deployments -A -o json | jq '.items[] | select(.status.unavailableReplicas > 0) | {name:.metadata.name, ns:.metadata.namespace, unavailable:.status.unavailableReplicas}'
kubectl get daemonsets -A -o json | jq '.items[] | select(.status.desiredNumberScheduled != .status.numberReady) | {name:.metadata.name, ns:.metadata.namespace, desired:.status.desiredNumberScheduled, ready:.status.numberReady}'
kubectl get pods -n kube-system -l k8s-app=kube-dns -o wide
kubectl get pods -n kube-system -l k8s-app=aws-node -o wide
kubectl get svc -A --field-selector spec.type=LoadBalancer
kubectl get pvc -A --field-selector status.phase!=Bound
kubectl get pv --field-selector status.phase!=Bound,status.phase!=Released
kubectl get csidrivers
kubectl get pods -A -o json | jq '[.items[] | select(.spec.containers[].securityContext.privileged==true) | {name:.metadata.name, ns:.metadata.namespace}]'
kubectl get networkpolicies -A
kubectl get podsecuritypolicies 2>/dev/null
# Infrastructure Health Report
## Summary
- Overall: HEALTHY / WARNING / CRITICAL
- Checked: [timestamp]
- Cluster: [name] (v[version])
## Results
| Domain | Status | Details |
|--------|--------|---------|
| Cluster | ✅/⚠️/❌ | [Summary] |
| Nodes (N/N ready) | ✅/⚠️/❌ | [Summary] |
| Workloads | ✅/⚠️/❌ | [N unhealthy pods] |
| Network | ✅/⚠️/❌ | [Summary] |
| Storage | ✅/⚠️/❌ | [N unbound PVCs] |
| Security | ✅/⚠️/❌ | [Summary] |
## Recommendations
1. [Action item]
2. [Action item]
references/health-check-procedures.md — Detailed procedures per domainreferences/metrics-thresholds.md — Warning/critical thresholds