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.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill terraform-module-library84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
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 excellent completeness and trigger term coverage. It clearly identifies when to use the skill and includes relevant keywords users would naturally mention. The main weakness is the lack of specific concrete actions - it could benefit from listing specific module types or operations (e.g., 'create VPC modules, configure state backends, implement module versioning').
Suggestions
Add specific concrete actions like 'create VPC modules, configure remote state, implement module versioning, define input/output variables' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Terraform modules) and mentions multi-cloud support (AWS, Azure, GCP), but lacks specific concrete actions beyond 'build reusable modules'. Doesn't specify what types of modules or what operations (e.g., networking, compute, storage, state management). | 2 / 3 |
Completeness | Clearly answers both what ('Build reusable Terraform modules for AWS, Azure, and GCP infrastructure') and when ('Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms: 'Terraform', 'modules', 'AWS', 'Azure', 'GCP', 'infrastructure', 'IaC', 'cloud provisioning'. These are terms users would naturally use when seeking this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Terraform modules across major cloud providers. The combination of 'Terraform', 'modules', and 'reusable IaC' creates distinct triggers unlikely to conflict with general cloud or coding skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong, actionable Terraform module patterns with executable code examples and good progressive disclosure. The main weaknesses are some verbosity in introductory sections and missing validation/verification steps in the workflow, which is important for infrastructure-as-code operations that can have destructive consequences.
Suggestions
Remove or condense the 'Purpose' and 'When to Use' sections - Claude understands when to use Terraform modules
Add explicit validation workflow: terraform fmt -> terraform validate -> terraform plan review -> apply, with checkpoints for reviewing plan output before destructive changes
Convert the 10-item best practices list to a more concise format or move to a reference file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary sections like 'Purpose' and 'When to Use' that explain concepts Claude already understands. The best practices list could be more concise. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready Terraform code with complete main.tf, variables.tf, and outputs.tf examples. The module composition and testing examples are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The module structure and patterns are clear, but lacks explicit validation checkpoints for the module development workflow. No guidance on terraform validate, plan review, or state management verification steps before applying changes. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from structure to examples to testing. References to additional files (assets/, references/) are clearly signaled and one level deep. Content is appropriately split between overview and detailed examples. | 3 / 3 |
Total | 10 / 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.
- 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.