CtrlK
BlogDocsLog inGet started
Tessl Logo

terraform-eks

Provision production-ready AWS EKS clusters with Terraform. Covers cluster configuration, managed node groups, Fargate profiles, IRSA, EKS add-ons (CoreDNS, kube-proxy, VPC CNI, EBS CSI), VPC integration, and security best practices. Use when provisioning EKS, setting up Kubernetes on AWS, configuring node groups, implementing IRSA, or managing EKS infrastructure as code.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is terraform-eks in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

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.

A code-heavy, highly actionable skill body with good reference structure, weakened by inline duplication of content that also lives in the reference files and by the absence of explicit validation checkpoints around destructive terraform operations.

Suggestions

Add an explicit provisioning workflow with validation checkpoints: run 'terraform validate' and 'terraform plan', review the plan, then 'terraform apply' — and for teardown, require a 'terraform plan -destroy' review before 'terraform destroy'.

De-duplicate the add-ons, IRSA, and node-group blocks that appear in both the 'Basic EKS Cluster Example' and their dedicated sections; keep the basic example minimal and point to the sections.

Move or parameterize hardcoded addon version strings (e.g. 'v1.11.3-eksbuild.2', cluster_version '1.33') into variables or a versions reference so the body does not silently age.

DimensionReasoningScore

Conciseness

The body is lean in prose and assumes Claude's competence, but add-ons/IRSA/node-groups are duplicated between the basic cluster example and their dedicated sections, and hardcoded addon version strings (e.g. 'v1.11.3-eksbuild.2') bloat and date quickly without being isolated in a deprecated section.

3 / 5

Actionability

Copy-paste-ready HCL and shell commands cover the common cases — cluster, managed/spot node groups, Fargate, IRSA, add-ons, VPC, and private-cluster endpoints — giving fully executable guidance.

5 / 5

Workflow Clarity

The Quick Reference lists init/plan/apply/destroy but there is no sequenced validate→fix→retry checkpoint loop; because terraform apply/destroy are destructive/batch operations, missing validation gates caps this dimension at 3.

3 / 5

Progressive Disclosure

A 'Detailed Documentation' section signals one-level-deep links to three real reference files (cluster-config.md, node-groups.md, addons-irsa.md), but substantial inline content overlaps those references, leaving a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

100%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.

A strong, third-person description that names concrete capabilities and pairs a clear 'what' with an explicit 'Use when...' trigger clause. It is specific, comprehensive, and low-conflict.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — cluster configuration, managed node groups, Fargate profiles, IRSA, and named EKS add-ons (CoreDNS, kube-proxy, VPC CNI, EBS CSI) — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' (provision production-ready EKS clusters with Terraform, covering the listed components) and 'when' (a concrete 'Use when...' clause with multiple triggers).

5 / 5

Trigger Term Quality

'Use when provisioning EKS, setting up Kubernetes on AWS, configuring node groups, implementing IRSA, or managing EKS infrastructure as code' captures natural phrases a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear EKS-with-Terraform niche with distinct triggers, making overlap with unrelated skills unlikely.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/Skrillz
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.