eks-reconlisted

EKS cluster reconnaissance and environment discovery. Detects compute strategy (Karpenter, MNG, Auto Mode, Fargate), IaC tooling (Terraform, CloudFormation, CDK, eksctl), CI/CD pipelines (GitHub Actions, GitLab, ArgoCD, Flux), add-on inventory, networking, security posture, and observability. Use this skill whenever someone asks about their EKS cluster, wants to understand their setup, is planning an upgrade or migration, needs cluster context for any reason, asks what version am I running, mentions wanting to review or document their cluster, or is about to make any EKS-related decision - even if they don't explicitly say reconnaissance or discovery. When in doubt about cluster state, run recon first. Skip for upgrade readiness scoring or deprecated API checks (eks-upgrade-check), operational audits with GREEN/AMBER/RED ratings (eks-operation-review), and architecture design documents or Mermaid diagrams (eks-design).
aws-samples/sample-apex-skills · ★ 37 · DevOps & Infrastructure · score 73

Install: claude install-skill aws-samples/sample-apex-skills

# EKS Reconnaissance Discover everything about an EKS cluster environment. Run this skill to gather comprehensive cluster context before making any decisions, changes, or recommendations. ## When to Use This Skill **Run this skill when the user:** - Asks about their EKS cluster ("what's my cluster running?", "tell me about my setup") - Plans an upgrade, migration, or architecture change - Needs cluster context before any EKS-related decision - Wants to document or review their cluster state - Asks questions like "what version am I on?" or "am I using Karpenter?" - Is about to modify their cluster (recon first to understand current state) **Also trigger this skill when:** - User mentions an EKS cluster name and seems to need context - Another workflow needs cluster information as input - You need to understand the cluster before giving recommendations **Do NOT use this skill for:** - **Upgrade readiness scoring or deprecated API checks** — questions like "score my upgrade readiness", "are there deprecated APIs blocking my upgrade", "can I safely upgrade to 1.33", "readiness score", or "breaking changes that would block a version bump" belong to `eks-upgrade-check`. Recon discovers *what version you're on*; it does NOT assess whether you're *ready* to move to the next version. - **Operational audits with maturity ratings** — questions like "run an operational excellence audit", "rate each area GREEN/AMBER/RED", or "audit my cluster's operational posture" belong to `eks-ope