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.

1.19x

Quality

74%

Does it follow best practices?

Impact

97%

1.19x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/terraform-module-library/SKILL.md

The canonical home for this skill is terraform-module-library in wshobson/agents

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 content is highly actionable with complete executable code, but it is token-heavy with full inlined module files, lacks an explicit workflow with validation checkpoints, and cites reference/asset files that do not exist in the bundle, weakening navigation and progressive disclosure.

Suggestions

Move the full main.tf/variables.tf/outputs.tf and Go test into bundle files under assets/ and keep only a concise representative snippet in SKILL.md to improve conciseness and progressive disclosure.

Add an explicit step-by-step workflow with a validation checkpoint (e.g., `terraform fmt`, `terraform validate`, then `terraform plan`) before apply/destroy to raise workflow clarity.

Fix the Reference Files list by either creating the missing assets/vpc-module, assets/rds-module, references/azure-modules.md, and references/gcp-modules.md, or removing the broken links so references resolve correctly.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable HCL, but it inlines three full files (main.tf, variables.tf, outputs.tf) plus a composition example and a full Go test, much of which could live in referenced bundle files rather than the SKILL.md overview.	3 / 5
Actionability	It provides fully executable, copy-paste-ready HCL and Go code covering the common VPC module case, with concrete variables, validation blocks, outputs, and a Terratest example.	5 / 5
Workflow Clarity	There is no explicit multi-step workflow with validation checkpoints; the guidance is a list of best practices and an example, and for destructive batch operations like terraform apply/destroy it lacks a validate-then-proceed feedback loop, capping clarity at 3.	3 / 5
Progressive Disclosure	The Reference Files section points to assets and references that do not exist (assets/vpc-module, assets/rds-module, references/azure-modules.md, references/gcp-modules.md are missing) while large inline blocks could be externalized, so references are broken and structuring is poor.	2 / 5
	Total	13 / 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 clearly states what the skill does and when to use it with concrete, natural trigger phrases and a distinct multi-cloud IaC niche. Minor gains are available from adding file-extension triggers and slightly more granular action verbs.

Dimension	Reasoning	Score
Specificity	The description names concrete actions ("Build reusable Terraform modules", "standardizing cloud provisioning", "implementing reusable IaC components") but the actions are still somewhat generic and missing the breadth of specificity a 5 would require.	4 / 5
Completeness	It explicitly answers both what ("Build reusable Terraform modules for AWS, Azure, and GCP infrastructure") and when ("Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger terms are present ("creating infrastructure modules", "standardizing cloud provisioning", "reusable IaC components"), but it omits file extensions like ".tf" and common phrasings users might say, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	The multi-cloud Terraform module niche is clearly defined with distinct triggers (Terraform modules, AWS/Azure/GCP, IaC), giving it minimal overlap with unrelated 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
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/terraform-module-library/SKILL.md
Commit: 6453c0b

Reviewed: about 9 hours 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.