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.
81
71%
Does it follow best practices?
Impact
97%
1.19xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/terraform-module-library/SKILL.mdQuality
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 with explicit 'Use when' triggers and good keyword coverage across the Terraform and multi-cloud domain. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., defining resource blocks, configuring providers, setting up state management) rather than staying at the level of 'build reusable modules'.
Suggestions
Add more specific concrete actions to the 'what' clause, e.g., 'define resource blocks, configure providers, set up remote state, create variable interfaces, and structure module hierarchies'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Terraform modules, AWS/Azure/GCP) and mentions some actions ('build reusable modules', 'standardizing cloud provisioning'), but doesn't list multiple concrete actions like 'create VPC modules, define IAM policies, configure state backends'. | 2 / 3 |
Completeness | Clearly answers both what ('Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices') and when ('Use when 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', 'infrastructure-as-code', 'IaC', 'cloud provisioning', 'reusable'. Good coverage of terms across the domain. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of Terraform, multi-cloud (AWS/Azure/GCP), and reusable modules creates a clear niche. Unlikely to conflict with general cloud skills or other IaC tools like Pulumi or CloudFormation since Terraform is explicitly named. | 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 solid, executable Terraform code examples with good patterns for module structure and composition. However, it lacks a clear workflow for actually creating and validating modules (no terraform validate/plan/apply sequence, no error recovery), which is critical for infrastructure operations that can be destructive. The content could be more concise by moving the full VPC example to a referenced file and trimming generic sections.
Suggestions
Add an explicit workflow sequence with validation checkpoints: terraform fmt → terraform validate → terraform plan (review) → terraform apply, with error recovery steps at each stage
Remove or significantly trim the 'Purpose' and 'When to Use' sections, and the generic 'Best Practices' list—these are well-known Terraform conventions that Claude already understands
Move the full VPC module example to a referenced file (e.g., assets/vpc-module/) and keep only a concise snippet inline showing the key patterns (validation blocks, conditional resources, tag merging)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the 'Purpose' and 'When to Use' sections that restate what Claude already knows about Terraform modules. The directory structure diagrams and best practices list are somewhat generic. However, the code examples themselves are reasonably lean. | 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, and a working Terratest Go test. These are copy-paste ready and include validation blocks, conditional resources, and proper tagging patterns. | 3 / 3 |
Workflow Clarity | There is no clear workflow sequence for creating, validating, or deploying modules. The content presents patterns and examples but never walks through the process: no 'terraform init/plan/apply' sequence, no validation checkpoints (e.g., 'terraform validate' or 'terraform fmt'), and no feedback loops for catching errors before applying infrastructure changes—which are destructive operations. | 1 / 3 |
Progressive Disclosure | The skill references external files (assets/vpc-module/, references/aws-modules.md, etc.) which is good progressive disclosure, but the main file itself is quite long with a full inline VPC module example that could be in a referenced file. The references are listed but not clearly signaled with context about what each contains. | 2 / 3 |
Total | 8 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- 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.