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.

Quality

71%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/cloud-infrastructure/skills/terraform-module-library/SKILL.md

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that clearly identifies its domain (Terraform modules for multi-cloud infrastructure) and includes an explicit 'Use when' clause with good trigger terms. Its main weakness is that the capability actions are somewhat high-level—it says 'build reusable modules' but doesn't enumerate specific types of infrastructure resources or module patterns it handles.

Suggestions

Add more specific concrete actions such as 'define networking configurations, create compute instances, set up IAM roles, configure storage buckets' to improve specificity beyond the general 'build reusable modules'.

Dimension	Reasoning	Score
Specificity	Names the domain (Terraform modules) and lists cloud providers (AWS, Azure, GCP, OCI), but the actions are somewhat generic ('build reusable modules', 'standardizing cloud provisioning') rather than listing specific concrete actions like 'define VPC configurations, create IAM policies, set up load balancers'.	2 / 3
Completeness	Clearly answers both 'what' (build reusable Terraform modules for multiple cloud providers following IaC best practices) and 'when' (explicit 'Use when' clause covering creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components).	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Terraform', 'modules', 'AWS', 'Azure', 'GCP', 'OCI', 'infrastructure-as-code', 'IaC', 'cloud provisioning'. These cover common variations and terms users would naturally use when requesting this type of work.	3 / 3
Distinctiveness Conflict Risk	The focus on Terraform modules specifically, combined with the multi-cloud provider list and IaC terminology, creates a clear niche that is unlikely to conflict with other skills like general coding, cloud console management, or other provisioning tools like Pulumi or CloudFormation.	3 / 3
	Total	11 / 12 Passed

Implementation

52%

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

The skill provides strong, actionable Terraform code examples with a complete AWS VPC module pattern that is copy-paste ready. However, it lacks a clear workflow with validation steps (terraform validate, plan, etc.) which is critical for infrastructure-as-code operations, and the content is somewhat verbose with sections that could be trimmed or split into reference files. The multi-cloud promise in the description is underdelivered since only AWS examples are provided inline.

Suggestions

Add an explicit step-by-step workflow with validation checkpoints: create module → terraform fmt → terraform validate → terraform plan → review plan output → apply, with error recovery guidance at each step.

Remove or significantly trim the 'Purpose' and 'When to Use' sections as they describe obvious concepts Claude already knows.

Move the full VPC module example into a referenced file (e.g., references/aws-vpc-example.md) and keep only a concise pattern summary inline.

Add references or brief examples for Azure, GCP, and OCI modules since the skill claims multi-cloud coverage but only provides AWS content.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary content like the 'Purpose' and 'When to Use' sections that describe obvious use cases Claude already understands. The directory tree structures are useful but the overall content could be tightened - the full VPC module example across three files is quite lengthy and could be more focused on patterns rather than a complete walkthrough.	2 / 3
Actionability	The skill provides fully executable HCL code for a complete VPC module (main.tf, variables.tf, outputs.tf), a concrete module composition example showing how modules chain together, and a working Go test file. All code is copy-paste ready with realistic values and proper syntax.	3 / 3
Workflow Clarity	There is no clear workflow sequence for creating a module. The content presents patterns and examples but lacks a step-by-step process (e.g., create files → validate with terraform validate → plan → test). For infrastructure operations that can be destructive, there are no validation checkpoints, no terraform plan step, and no feedback loops for error recovery.	1 / 3
Progressive Disclosure	There is a reference to 'references/aws-modules.md' and 'references/oci-modules.md' at the end of best practices, and related skills are mentioned. However, the main file is quite long with a full inline module example that could be split out, and the Azure, GCP, and OCI modules mentioned in the directory structure have no corresponding references or content pointers.	2 / 3
	Total	8 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Commit: 27a7ed9

Reviewed: 5 days 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.