CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

terraform-module-library

Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/terraform-module-library/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 delivers genuinely actionable, executable Terraform patterns with a real one-level-deep reference file, but it is diluted by generic template filler and lacks validation checkpoints (terraform validate/plan) for what is ultimately batch infrastructure provisioning. Trimming the boilerplate sections and completing the code examples would lift it substantially.

Suggestions

Remove the boilerplate sections ("Do not use this skill when", "Instructions", "Purpose", "Use this skill when") that add no information beyond the frontmatter description, cutting token overhead.

Add a validation workflow for provisioning: run `terraform validate` and review `terraform plan` output before apply, with an explicit fix-and-re-validate loop, since infrastructure changes are batch operations.

Complete the actionability gaps: declare the `create_internet_gateway` variable used in main.tf, and add Azure/GCP reference files (mirroring references/aws-modules.md) so the multi-cloud claim is supported beyond directory names.

DimensionReasoningScore

Conciseness

The technical core (module layout, HCL examples, Terratest) is lean, but four boilerplate sections pad the file: "The task is unrelated to terraform module library", "Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.", plus Purpose and Use-this-skill-when sections that duplicate the frontmatter description. Mostly efficient with unnecessary sections that could be trimmed — anchor 3 rather than 2, since there is no over-explanation of concepts Claude already knows and the padding is a minority of the file.

3 / 5

Actionability

Concrete, near-complete executable artifacts: full main.tf/variables.tf/outputs.tf for the VPC module, a module composition example, and a runnable Terratest file. Not anchor 5 because main.tf references var.create_internet_gateway which is never declared in variables.tf, and Azure/GCP modules receive only directory names with no patterns or examples — minor gaps in copy-paste readiness and common-case coverage.

4 / 5

Workflow Clarity

The implicit sequence (standard pattern → write module → compose → test with Terratest) is discernible, and the Terratest example embeds a post-hoc assertion (assert.NotEmpty on vpc_id, deferred destroy). However, infrastructure provisioning is a batch operation with no terraform validate or terraform plan checkpoint before apply — the rubric caps workflow clarity at 3 for batch operations lacking validation, and here the checkpoints are implicit or missing. It is above anchor 2 because a rough sequence and one verification mechanism do exist.

3 / 5

Progressive Disclosure

The body points to references/aws-modules.md, which exists in the bundle, is one level deep, and is clearly signaled under "Reference Files" with a one-line description. Not anchor 5: the full VPC module example is lengthy content inlined in SKILL.md that could live in the reference, and only AWS has a reference file while Azure and GCP have none — minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

78%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 description that explicitly covers what the skill does and when to use it, with natural trigger terms and Terraform-specific distinctiveness. Its main weakness is limited action specificity — it names essentially one capability (building reusable modules) dressed with generic best-practices language.

DimensionReasoningScore

Specificity

"Build reusable Terraform modules for AWS, Azure, and GCP infrastructure" names the domain and one concrete action, but "following infrastructure-as-code best practices" is generic padding rather than additional specific capabilities. It lists 1-2 concrete actions without comprehensive coverage, matching anchor 3 rather than 4, which requires several specific actions.

3 / 5

Completeness

The description clearly answers both: "Build reusable Terraform modules for AWS, Azure, and GCP infrastructure..." (what) and "Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components" (when) with three concrete trigger phrases. This structurally matches the anchor-5 example; the when-clause does not need more explicitness, so it is not anchor 4.

5 / 5

Trigger Term Quality

Natural terms like "Terraform modules", "AWS, Azure, and GCP", "cloud provisioning", and the synonym pair "infrastructure-as-code" / "IaC components" give good keyword coverage a user would naturally say. Not anchor 5 because file extensions (.tf, HCL) and common variations like "terraform project" are missing.

4 / 5

Distinctiveness Conflict Risk

"Build reusable Terraform modules" carves out a clear niche with distinct triggers (module creation, IaC components), but broader phrases like "creating infrastructure modules" and "standardizing cloud provisioning" could overlap with general IaC or cloud-architecture skills. Mostly distinct with minor overlap risk, matching anchor 4 rather than 5's minimal-conflict bar.

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/terraform-module-library/SKILL.md

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.