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.
61
71%
Does it follow best practices?
Impact
—
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 with strong trigger terms, explicit 'Use when' guidance, and clear distinctiveness. Its main weakness is that the capability description could be more specific about the concrete actions performed (e.g., generating module structures, defining variables/outputs, writing provider configurations) rather than staying at a somewhat abstract level.
Suggestions
Add more specific concrete actions like 'generate module directory structures, define input variables and outputs, configure provider blocks, and write resource definitions' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Terraform modules) and mentions some actions ('build reusable modules', 'standardizing cloud provisioning'), but doesn't list multiple specific concrete actions like creating VPCs, configuring security groups, setting up state backends, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (build reusable Terraform modules for multi-cloud infrastructure) and 'when' (explicit 'Use when' clause covering creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'Terraform', 'modules', 'AWS', 'Azure', 'GCP', 'OCI', 'infrastructure-as-code', 'IaC', 'cloud provisioning', 'infrastructure modules'. These are terms users would naturally use when requesting this kind of work. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on Terraform modules specifically, combined with multi-cloud provider names, creates a clear niche that is unlikely to conflict with other skills. It's distinct from general cloud skills, general coding skills, or other IaC 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 high-quality, executable Terraform code examples that are immediately actionable, which is its strongest aspect. However, it lacks a clear workflow for module creation (no plan/validate/apply sequence with checkpoints), includes some verbose sections that explain concepts Claude already knows (purpose, when to use, generic best practices), and references bundle files that don't exist. The content would benefit from being restructured as a concise workflow with detailed examples moved to referenced files.
Suggestions
Add a clear step-by-step workflow for creating and validating a module: e.g., 1) scaffold structure, 2) implement resources, 3) run `terraform validate`, 4) run `terraform plan` with example vars, 5) test with Terratest, with explicit validation checkpoints and error recovery.
Remove the 'Purpose' and 'When to Use' sections—Claude can infer these from context. Also trim the best practices list to only non-obvious, project-specific conventions.
Move the full VPC module example (variables.tf, outputs.tf) into a referenced file like `references/aws-modules.md` and keep only a concise snippet inline, or actually provide the referenced bundle files.
Add a `terraform plan` validation step and state management guidance, since infrastructure operations are destructive and missing feedback loops are critical.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the 'Purpose' and 'When to Use' sections that explain obvious concepts Claude already knows. The AWS VPC example is thorough but quite long—the full variables.tf and outputs.tf could be trimmed or referenced externally. The best practices list is generic Terraform knowledge Claude already possesses. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready HCL code for a complete VPC module (main.tf, variables.tf, outputs.tf), a concrete module composition example, and a working Terratest Go test. All code is complete and runnable, not pseudocode. | 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 with validation checkpoints. For infrastructure operations (which are destructive), there's no mention of plan-before-apply, state management validation, or error recovery steps. | 1 / 3 |
Progressive Disclosure | References to 'references/aws-modules.md' and 'references/oci-modules.md' are mentioned but no bundle files exist to support them. The content is somewhat monolithic with the full VPC example inline rather than split into referenced files. The related skills section is a nice touch but the overall organization could better separate overview from detailed examples. | 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
cf6059d
- 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.