cnoe-io/cluster-resource-health
charts/ai-platform-engineering/data/skills/cluster-resource-health/SKILL.md
Check Kubernetes cluster health including pod status, node conditions, resource utilization, and pending alerts across EKS clusters. Use when monitoring infrastructure health, investigating capacity issues, or performing cluster audits.
$ install --global
skillsauthnpx skillsauth add cnoe-io/ai-platform-engineering cluster-resource-healthInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 4:51 PM9.3s2 files scanned
SKILL.md
- name:
- cluster-resource-health
- description:
- Check Kubernetes cluster health including pod status, node conditions, resource utilization, and pending alerts across EKS clusters. Use when monitoring infrastructure health, investigating capacity issues, or performing cluster audits.
Cluster Resource Health
Query AWS EKS clusters for node health, pod status, resource utilization, and alerts to produce a cluster health dashboard.
Instructions
Phase 1: Cluster Overview (AWS Agent)
- List EKS clusters and their status
- Check Kubernetes version - current vs. latest, end-of-support date
Phase 2: Node Health
- Inspect node conditions - Ready, MemoryPressure, DiskPressure, PIDPressure
- Resource utilization per node - CPU, Memory, Pod count
Phase 3: Pod Health
- Identify problematic pods - CrashLoopBackOff, ImagePullBackOff, OOMKilled, Pending
- Namespace-level summary - pods running, pending, failed per namespace
Phase 4: Resource Capacity Analysis
- Cluster-wide utilization - total CPU/Memory requested vs. allocatable
- Capacity risks - nodes at >80%, namespaces exceeding quotas
Output Format
```markdown
Cluster Resource Health Report
Cluster Summary
| Cluster | Version | Nodes | Status | Overall Health | |---------|---------|-------|--------|----------------| | prod-us-west-2 | 1.29 | 12/12 Ready | Active | HEALTHY |
Resource Utilization
| Resource | Requested | Allocatable | Utilization | |----------|-----------|-------------|-------------| | CPU | 38 cores | 48 cores | 79% | | Memory | 96 Gi | 128 Gi | 75% | ```
Examples
- "Check the health of our EKS clusters"
- "Are there any failing pods in production?"
- "Show me cluster resource utilization"
- "Which nodes are under memory pressure?"
Guidelines
- Check all clusters unless a specific cluster is requested
- Flag any node above 85% resource utilization as a capacity risk
- For CrashLoopBackOff pods, suggest checking logs as the immediate action
- EKS version end-of-support should be flagged at least 90 days before EOL
- Use kubectl read-only commands only (never modify cluster state during health checks)
Related Skills
cnoe-io/streaming-testing
testing
VerifiedTrustedCommunity
Compare A2A streaming behaviour across supervisor versions. Captures SSE events, analyzes metadata flags (is_narration, is_final_answer), and produces side-by-side comparison reports.
345SKILL.mdUpdated Apr 15, 2026
cnoe-io/sprint-progress-report
testing
VerifiedTrustedCommunity
Generate a comprehensive sprint progress report from Jira with velocity metrics, burndown analysis, blocker identification, and team workload distribution. Use when preparing sprint reviews, standups, or tracking sprint health mid-cycle.
345SKILL.mdUpdated Apr 4, 2026
cnoe-io/security-vulnerability-report
development
VerifiedTrustedCommunity
Scan GitHub repositories for security vulnerabilities including Dependabot alerts, code scanning results, and secret scanning findings. Use when auditing repository security, preparing compliance reports, or triaging vulnerability alerts.
345SKILL.mdUpdated Apr 4, 2026
cnoe-io/review-specific-pr
development
VerifiedTrustedCommunity
Perform a comprehensive code review of a specific GitHub Pull Request. Analyzes code changes, checks for bugs, security issues, test coverage, and coding standards compliance. Use when a user provides a PR URL or asks to review a specific pull request.
345SKILL.mdUpdated Apr 4, 2026