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 description with explicit 'Use when' triggers, good keyword coverage across Terraform and multi-cloud domains, and clear distinctiveness. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., defining variables, outputs, provider configurations, module structure).
Suggestions
Add more specific concrete actions to boost specificity, e.g., 'define module inputs/outputs, configure provider blocks, set up remote state, create resource compositions'.
| 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 multi-cloud infrastructure) and 'when' with an explicit 'Use when...' clause covering creating infrastructure modules, standardizing provisioning, and 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, reusable modules, and multi-cloud (AWS/Azure/GCP) creates a clear niche. Unlikely to conflict with general cloud skills, Ansible skills, or non-modular Terraform usage. | 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 and good module structure guidance, but lacks a clear workflow for actually creating and validating modules. The content is somewhat verbose for a skill file, inlining a complete module example that could be referenced externally. The absence of any validation workflow (terraform validate, plan, fmt) is a significant gap for infrastructure-as-code work where mistakes can be destructive.
Suggestions
Add a clear step-by-step workflow for creating a module: scaffold structure → write resources → run terraform fmt → terraform validate → write tests → run terratest, with explicit validation checkpoints at each stage.
Move the complete VPC module example to a referenced file (e.g., assets/vpc-module/) and keep only a minimal illustrative snippet in the main skill file to improve conciseness.
Remove the 'Purpose' and 'When to Use' sections - these describe obvious context that Claude can infer from the skill's description and content.
Add terraform validate, terraform fmt, and terraform plan as explicit validation steps, especially before any apply operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the 'Purpose' and 'When to Use' sections that explain obvious context Claude already knows. The VPC module example is thorough but quite long - the variables.tf and outputs.tf sections could be trimmed since the patterns are standard Terraform conventions Claude would already understand. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready HCL code for a complete VPC module including main.tf, variables.tf, outputs.tf, module composition examples, and even a Go test file. The code is concrete, uses real resource types, and demonstrates practical patterns like validation blocks and conditional resources. | 3 / 3 |
Workflow Clarity | There is no clear workflow sequence for creating a module. The content presents components (structure, code, tests) but never sequences them into a step-by-step process. There are no validation checkpoints - no 'terraform validate', 'terraform plan', or 'terraform fmt' steps mentioned, which are critical for IaC workflows involving potentially destructive infrastructure changes. | 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 the full VPC module inlined. The VPC example could be referenced rather than fully included, keeping the SKILL.md as a concise overview with pointers to 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
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- 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.