eks
AWS EKS Kubernetes management for clusters, node groups, and workloads. Use when creating clusters, configuring IRSA, managing node groups, deploying applications, or integrating with AWS services.
84
82%
Does it follow best practices?
Impact
84%
1.03xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms users would actually use, explicitly states both what the skill does and when to use it, and has a clear distinctive niche in AWS EKS management that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'clusters, node groups, and workloads' as domains, and 'creating clusters, configuring IRSA, managing node groups, deploying applications, integrating with AWS services' as specific actions. | 3 / 3 |
Completeness | Clearly answers both what ('AWS EKS Kubernetes management for clusters, node groups, and workloads') and when ('Use when creating clusters, configuring IRSA, managing node groups, deploying applications, or integrating with AWS services') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'AWS', 'EKS', 'Kubernetes', 'clusters', 'node groups', 'IRSA', 'deploying applications', 'AWS services'. These cover both technical terms and common user language. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche targeting AWS EKS specifically. The combination of 'AWS', 'EKS', 'Kubernetes', and 'IRSA' creates a unique fingerprint unlikely to conflict with generic Kubernetes or other cloud provider skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable EKS skill with excellent executable code examples covering the full lifecycle of cluster management. The main weaknesses are verbosity in concept explanations that Claude doesn't need, and missing validation checkpoints for multi-step operations like cluster creation and IRSA configuration. The content would benefit from trimming introductory explanations and adding explicit verification steps.
Suggestions
Remove or minimize concept explanations (e.g., 'EKS manages the control plane and integrates with AWS services') - Claude knows what EKS is
Add explicit validation steps after cluster creation (e.g., 'Verify: kubectl get nodes should return Ready status') and after IRSA setup
Split detailed sections like manual IRSA setup and troubleshooting into separate reference files to improve progressive disclosure
Add verification commands inline with workflows, such as checking cluster status before proceeding to node group creation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary explanations like 'Amazon Elastic Kubernetes Service (EKS) runs Kubernetes without installing and operating your own control plane' and basic concept definitions that Claude already knows. The table of contents also adds overhead. | 2 / 3 |
Actionability | Excellent executable code throughout - complete bash commands with all required flags, full YAML manifests, and copy-paste ready examples for cluster creation, IRSA setup, node groups, and deployments. Both AWS CLI and eksctl approaches are provided. | 3 / 3 |
Workflow Clarity | Steps are listed sequentially (create role, attach policy, create cluster, wait, update kubeconfig) but lacks explicit validation checkpoints. For destructive operations like cluster deletion or node group changes, there are no verification steps or rollback guidance. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a table of contents, but it's a monolithic document (~300 lines) that could benefit from splitting detailed sections (like full IRSA manual setup or troubleshooting) into separate reference files. External references are only to AWS docs, not internal skill files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- itsmostafa/aws-agent-skills
- Commit
5df6da7
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.