eks-cluster-config
Eks Cluster Config - Auto-activating skill for AWS Skills. Triggers on: eks cluster config, eks cluster config Part of the AWS Skills skill category.
34
3%
Does it follow best practices?
Impact
89%
0.95xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/eks-cluster-config/SKILL.mdQuality
Discovery
7%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 description is extremely minimal and essentially just restates the skill name without providing any useful information about capabilities or trigger conditions. It fails to describe concrete actions, lacks natural trigger terms users would use, and provides no guidance on when Claude should select this skill. The only slight positive is that 'EKS' anchors it to a specific AWS service.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures Amazon EKS clusters, manages node groups, generates kubeconfig files, sets up IAM roles for service accounts.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Kubernetes on AWS, EKS cluster setup, node group configuration, kubeconfig, or managed Kubernetes deployment.'
Include common keyword variations users might say such as 'Kubernetes cluster', 'K8s on AWS', 'EKS node groups', 'managed Kubernetes', 'eksctl', '.kube/config'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only names 'eks cluster config' without describing what specific tasks it performs (e.g., create clusters, configure node groups, set up networking). The language is entirely abstract. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the name itself. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'eks cluster config' repeated twice. Missing natural variations users would say like 'Kubernetes cluster', 'EKS setup', 'AWS Kubernetes', 'kubeconfig', 'node groups', 'cluster creation', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'EKS cluster config' does narrow the domain to a specific AWS service, which provides some distinctiveness. However, it could overlap with general AWS infrastructure skills or Kubernetes skills due to lack of specificity about what exactly it handles. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder with no actual EKS cluster configuration content. It consists entirely of generic boilerplate text that could be auto-generated for any topic, providing zero actionable guidance, no code examples, no CLI commands, and no AWS/EKS-specific information whatsoever.
Suggestions
Add concrete, executable examples such as `eksctl create cluster` commands or CloudFormation/Terraform templates for EKS cluster configuration.
Define a clear multi-step workflow covering VPC setup, IAM role creation, cluster provisioning, node group configuration, and kubeconfig setup, with validation checkpoints at each stage.
Include specific EKS configuration YAML examples (e.g., eksctl ClusterConfig manifests) with key parameters explained inline.
Replace all generic boilerplate sections ('Capabilities', 'Example Triggers') with actual technical content—best practices for networking (VPC CNI), security groups, IRSA, and managed node groups.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains nothing Claude doesn't already know and provides zero EKS-specific configuration details. Every section is generic boilerplate that could apply to any topic. | 1 / 3 |
Actionability | There are no concrete code examples, no specific commands, no YAML configurations, no CLI snippets—nothing actionable whatsoever. The skill describes what it does in abstract terms ('provides step-by-step guidance') without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, no validation checkpoints. EKS cluster configuration is inherently a multi-step process (VPC setup, IAM roles, cluster creation, node groups, kubeconfig) and none of it is addressed. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no references to detailed materials, no links to related files, and no structured navigation. There is no meaningful content to disclose progressively. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.