CtrlK
BlogDocsLog inGet started
Tessl Logo

terraform-aws

Comprehensive AWS infrastructure management with Terraform. Covers provider configuration, state management (S3 backend with native locking in Terraform 1.11+), common resource patterns (VPC, IAM, S3, RDS, EKS), module usage, and production best practices. Use when provisioning AWS infrastructure, managing Terraform state, creating VPCs, configuring IAM roles/policies, deploying databases, or troubleshooting Terraform/AWS issues.

71

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 strong, code-rich skill body with executable patterns across the major AWS resource types and well-signaled references. Its main weaknesses are redundant command listings and destructive workflows that lack explicit validation checkpoints.

Suggestions

Add explicit validation checkpoints to destructive workflows: in 'Plan and Apply', insert a step like 'Review the plan output; only proceed if changes are expected' before `terraform apply tfplan`, and add a post-apply verify step (e.g., re-run `terraform plan` to confirm no drift).

Remove the standalone 'Quick Reference Commands' section or fold it into 'Common Workflows' — it duplicates the terraform init/plan/apply/workspace commands already presented there.

Trim the repeated version banners and 'Keywords' line at the top, and move the full inline VPC/IAM/RDS resource patterns into the existing references to reduce overlap with vpc-networking.md and iam-security.md.

DimensionReasoningScore

Conciseness

The body is mostly lean, code-focused content rather than concept re-explanation, but carries minor trimmable redundancy: the 'Quick Reference Commands' section duplicates init/plan/apply/workspace commands already shown in 'Common Workflows', and version banners plus a 'Keywords' line are repeated at top and bottom.

4 / 5

Actionability

Provides copy-paste-ready, executable HCL (VPC, S3, IAM, RDS, state backend, EKS module) and concrete bash commands covering the common cases, matching the level-5 anchor.

5 / 5

Workflow Clarity

Workflows list command groups (init, plan, apply, import, workspace) but destructive operations (apply, destroy, state rm, force-unlock) lack explicit validation checkpoints or feedback loops; per the rubric cap, destructive/batch workflows without validation cannot score above 3.

3 / 5

Progressive Disclosure

A 'Detailed Documentation' section clearly signals three real, one-level-deep reference files with descriptive bullets, but the inline resource patterns (VPC, S3, IAM, RDS) are fairly heavy and overlap in topic with those reference files — a minor organization gap keeping it below 5.

4 / 5

Total

16

/

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 well-crafted description that concisely states concrete capabilities and provides a rich, natural-language 'Use when' trigger clause covering the main AWS/Terraform use cases. It is specific, complete, and distinct with no over-claims.

DimensionReasoningScore

Specificity

Names concrete resource types (VPC, IAM, S3, RDS, EKS) plus specific capabilities (provider configuration, S3 native locking, module usage) and concrete actions in the trigger clause (provisioning, creating VPCs, deploying databases) — comprehensive coverage matching the level-5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' (Covers provider configuration, state management, resource patterns, module usage, best practices) and 'when' (Use when provisioning... or troubleshooting) with concrete trigger phrases, matching the level-5 anchor.

5 / 5

Trigger Term Quality

The 'Use when...' clause lists natural phrases users actually say ('provisioning AWS infrastructure', 'creating VPCs', 'configuring IAM roles/policies', 'deploying databases', 'troubleshooting Terraform/AWS issues'), giving comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

The combined Terraform-on-AWS niche with distinct resource-specific triggers (VPC, IAM, RDS, EKS, S3 state locking) is clearly distinguishable with minimal overlap risk against generic Terraform or AWS skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (634 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

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.