terraform-module-library

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

1.58x

Quality

—

Does it follow best practices?

Impact

76%

1.58x

Average score across 1 eval scenario

Securityby

Passed

No known issues

Quality

Content

72%

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

A well-organized, highly actionable skill body with executable HCL and Terratest examples and correctly signaled bundle references. Weaker spots are the lack of a sequenced, checkpointed workflow and some inline code blocks that could be tightened or externalized.

Suggestions

Add a numbered, sequenced module-authoring workflow with explicit validation/checkpoint steps (e.g., validate inputs -> plan -> test with Terratest -> destroy) to raise workflow clarity above level 2.

Move the full variables.tf/outputs.tf and Go test listings into the references bundle and link to them, tightening the inline SKILL.md to lift conciseness.

Provide a minimal complete example (one self-contained main.tf + variables.tf) rather than spreading the AWS VPC example across three separate fenced blocks to improve scannability.

Dimension	Reasoning	Score
Conciseness	Assumes Claude's competence (no padding about what Terraform is) and is mostly efficient, but full inline main.tf/variables.tf/outputs.tf blocks and the Go test could be tightened or referenced rather than reproduced wholesale, matching the level-2 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	Provides fully executable HCL (VPC, subnets, IGW), variable validation blocks, outputs, module composition, and a copy-paste-ready Terratest Go test, matching the level-3 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	Structure, patterns, and best practices are listed, but there is no sequenced module-authoring workflow with explicit validation checkpoints or feedback loops; the sequence is present but implicit, matching the level-2 anchor.	2 / 3
Progressive Disclosure	Well-organized sections with clearly signaled one-level-deep references to real bundle files (references/aws-modules.md, references/oci-modules.md), matching the level-3 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	10 / 12 Passed

Description

100%

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 states concrete capabilities and an explicit 'Use when' trigger clause covering natural terms across the multi-cloud Terraform module niche. It avoids verbosity and over-claims.

Dimension	Reasoning	Score
Specificity	Names the domain (Terraform modules for AWS/Azure/GCP/OCI) and multiple concrete actions (build, standardize, implement reusable IaC components), matching the level-3 anchor listing specific concrete actions.	3 / 3
Completeness	Explicitly answers 'what' (Build reusable Terraform modules...) and 'when' via an explicit 'Use when creating infrastructure modules, standardizing cloud provisioning...' trigger clause, satisfying the level-3 anchor.	3 / 3
Trigger Term Quality	Includes natural user-facing terms ('Terraform modules', 'cloud provisioning', 'IaC', 'infrastructure modules') with good coverage rather than jargon, matching the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	Has a clear niche (multi-cloud Terraform module authoring) with distinct triggers unlikely to fire for unrelated skills, matching the level-3 anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Commit: 5cc2549

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