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.
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/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 that clearly identifies its domain (Terraform modules for multi-cloud infrastructure) and includes an explicit 'Use when' clause with relevant trigger scenarios. The main weakness is that the specific capabilities could be more granular—listing concrete actions like defining networking, compute, storage modules rather than the higher-level 'build reusable modules'. Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions beyond 'build reusable modules', such as 'define networking configurations, create compute and storage modules, implement variable validation and output definitions' to improve specificity.
| 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 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 module examples with executable HCL code and testing patterns. However, it lacks a clear workflow for module creation and validation (no terraform plan/validate steps, no feedback loops), and is somewhat verbose with content that could be better organized across reference files. The 'When to Use' and 'Purpose' sections add little value for Claude.
Suggestions
Add a clear step-by-step workflow for module creation including validation checkpoints: terraform fmt, terraform validate, terraform plan review, and apply with explicit verification steps.
Remove the 'Purpose' and 'When to Use' sections as they describe obvious concepts Claude already understands, and trim the 'Best Practices' list to only non-obvious items.
Move the full VPC module example (main.tf + variables.tf + outputs.tf) to a reference file and keep only a condensed example inline, using the freed space to add the missing workflow.
| 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 structure diagrams are useful but the overall content could be tightened - the full VPC module example spanning main.tf, variables.tf, and outputs.tf is quite lengthy and could be more condensed while still being illustrative. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready HCL code for a complete VPC module including main.tf, variables.tf, and outputs.tf with proper validation blocks. The module composition example and Terratest code are also concrete and executable. | 3 / 3 |
Workflow Clarity | There is no clear workflow sequence for creating, validating, or deploying modules. The content presents patterns and examples but lacks a step-by-step process with validation checkpoints. For infrastructure operations (which are destructive/batch), missing validation steps like 'terraform plan', 'terraform validate', or review gates is a significant gap. | 1 / 3 |
Progressive Disclosure | There are references to external files ('references/aws-modules.md' and 'references/oci-modules.md') and related skills, which is good. However, the inline content is quite long with the full VPC module example that could be split into a separate reference file, and the Azure, GCP, and OCI modules mentioned in the directory structure have no corresponding examples or references. | 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
- wshobson/agents
- Commit
70444e5
- 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.