building-terraform-modules
Execute this skill empowers AI assistant to build reusable terraform modules based on user specifications. it leverages the terraform-module-builder plugin to generate production-ready, well-documented terraform module code, incorporating best practices for sec... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
45
33%
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/devops/terraform-module-builder/skills/building-terraform-modules/SKILL.mdQuality
Discovery
17%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 description suffers from a truncated capability section and a completely boilerplate trigger clause that provides no real guidance for skill selection. While it identifies the domain (Terraform modules) and references a specific plugin, the generic 'Use when appropriate context detected' placeholder and first-person framing ('empowers AI assistant') significantly undermine its utility. The description would fail to help Claude reliably select this skill from a large skill library.
Suggestions
Replace the boilerplate 'Use when appropriate context detected' with specific trigger conditions, e.g., 'Use when the user asks to create, scaffold, or generate a Terraform module, or mentions reusable infrastructure code, module structure, or terraform-module-builder.'
Complete the truncated description to list all concrete actions (e.g., 'generates module structure with variables, outputs, README, and examples; incorporates security best practices; validates module configuration').
Rewrite in third person voice ('Builds reusable Terraform modules...') instead of the current framing ('empowers AI assistant to build...').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Terraform modules) and a general action (build/generate), but the description is truncated ('sec...') and doesn't list multiple concrete actions. It mentions 'production-ready, well-documented terraform module code' which adds some specificity but remains somewhat vague. | 2 / 3 |
Completeness | The 'what' is partially addressed (build terraform modules) but truncated. The 'when' clause is pure boilerplate placeholder text ('Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.') providing zero actionable guidance, which is effectively missing. | 1 / 3 |
Trigger Term Quality | The 'Use when' clause is entirely generic boilerplate ('appropriate context detected', 'relevant phrases based on skill purpose') with no actual natural trigger terms. While 'terraform modules' appears in the body, the trigger guidance is useless for skill selection. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'terraform modules' and 'terraform-module-builder plugin' provides some distinctiveness from other skills, but the generic trigger clause and truncated description weaken its ability to clearly differentiate from other infrastructure-as-code or Terraform-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level guide for building Terraform modules with good structural organization and a useful error handling table. However, it lacks concrete HCL code examples that would make it truly actionable, relies on descriptive instructions rather than executable snippets, and misses explicit validation feedback loops in the workflow. The content could be significantly more useful with even one complete mini-module example.
Suggestions
Add at least one concrete HCL code example showing a complete minimal module (e.g., a variables.tf with a validation block, a main.tf resource, and an outputs.tf) to make the skill actionable and copy-paste ready.
Add an explicit feedback loop at step 10: 'If terraform validate fails, review errors, fix the relevant files, and re-run validation before proceeding to terraform plan.'
Remove prerequisites that Claude already knows (HCL familiarity, understanding of infrastructure resources) and trim the overview to reduce token usage.
Consider creating bundle files (e.g., a template module skeleton or a PATTERNS.md with common module patterns) to support progressive disclosure and keep the main SKILL.md lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like prerequisites that explain what Claude already knows (HCL syntax familiarity, understanding of infrastructure resources). The error handling table and examples section add useful but somewhat verbose content. The overview restates things that could be trimmed. | 2 / 3 |
Actionability | The instructions provide a clear sequence of steps with specific file names and commands (terraform init, terraform validate, terraform-docs), but lack any concrete executable code examples—no actual HCL snippets showing a variable definition with validation, a resource block, or an output block. The 'Examples' section lists natural language prompts rather than code examples. | 2 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced and step 10 includes validation (terraform validate and terraform plan), but there's no explicit feedback loop for error recovery—no 'if validation fails, fix and re-validate' checkpoint. For a module-building workflow that involves multiple interdependent files, missing validation feedback loops caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-organized with clear sections (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources), but everything is inline in a single file with no bundle files to offload detailed content like HCL templates, example modules, or validation scripts. The Resources section links to external docs but there's no internal progressive disclosure structure. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.