eks-networking

EKS networking configuration including VPC CNI, load balancers, and network policies. Use when setting up cluster networking, configuring ingress/load balancing, implementing network security, troubleshooting connectivity, or optimizing network costs.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/eks-networking/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with comprehensive executable examples and a well-signaled reference structure, but it is hampered by repetition, some over-explanation of basics, and a lack of explicit validation checkpoints in the phased workflow.

Suggestions

De-duplicate repeated operations (ENABLE_NETWORK_POLICY, prefix delegation, CNI metrics helper appear multiple times) and consolidate each into its single canonical location.

Add explicit validation checkpoints between phases (e.g., verify addon readiness, confirm pod IP allocation, check ALB provisioning status) before proceeding to the next phase.

Move detailed manifest examples that duplicate the reference files (full ALB/NLB/NetworkPolicy YAML) into references/ and keep only concise representative snippets in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with abundant executable code, but the body repeats the same operations multiple times (ENABLE_NETWORK_POLICY, prefix delegation, CNI metrics helper each appear 2-3 times) and the Overview explains basics Claude already knows ('ALB for Layer 7, NLB for Layer 4'); could be tightened.	3 / 5
Actionability	Provides copy-paste-ready aws/eksctl/kubectl/helm commands and complete YAML manifests (Ingress, NetworkPolicy, NLB Service, SecurityGroupPolicy, IngressClass) covering the common EKS networking cases.	5 / 5
Workflow Clarity	Phases 1-6 give a clear sequence, but the workflow lacks explicit validation checkpoints between phases; because changing CNI config and applying network policies are cluster-disruptive operations, the missing validate-then-proceed feedback loop caps this at 3.	3 / 5
Progressive Disclosure	A clearly signaled 'Reference Documentation' section points to three real one-level-deep files (references/vpc-cni.md, load-balancers.md, network-policies.md), but a large amount of manifest and config content is inlined in SKILL.md that overlaps with those references, leaving minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states concrete capabilities, uses natural trigger terms, and explicitly pairs a 'what' with a 'Use when' clause. It is appropriately concise and distinct from other skills.

Dimension	Reasoning	Score
Specificity	Names the EKS networking domain and lists several specific components (VPC CNI, load balancers, network policies) plus concrete use-case actions like 'configuring ingress/load balancing', 'implementing network security', and 'troubleshooting connectivity'; minor gaps in coverage but well above generic.	4 / 5
Completeness	Explicitly answers both 'what' ('EKS networking configuration including VPC CNI, load balancers, and network policies') and 'when' ('Use when setting up cluster networking, configuring ingress/load balancing...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('EKS networking', 'load balancers', 'ingress/load balancing', 'network security', 'troubleshooting connectivity', 'network costs') with good coverage; a few natural synonyms or variant phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	EKS-specific terms (VPC CNI, EKS cluster networking) carve a clear niche with distinct triggers and minimal overlap risk with non-EKS or non-networking skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (693 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/eks-networking/SKILL.md
Commit: 93ed392

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.