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.

Quality

33%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/devops/terraform-module-builder/skills/building-terraform-modules/SKILL.md

Quality

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 three major issues: it is truncated mid-sentence ('sec...'), it uses first/second person framing ('empowers AI assistant'), and its trigger clause is entirely generic boilerplate with no actionable keywords. While the Terraform module domain is identifiable, the description fails to provide concrete actions, natural trigger terms, or explicit 'when to use' guidance.

Suggestions

Replace the boilerplate 'Use when appropriate context detected' with specific trigger guidance, e.g., 'Use when the user asks to create a Terraform module, scaffold infrastructure as code, or generate .tf files for reusable cloud resources.'

Complete the truncated description and list specific concrete actions, e.g., 'Generates Terraform module scaffolding with variables, outputs, README, and examples. Incorporates security best practices, input validation, and provider version constraints.'

Add natural trigger terms users would say: 'terraform module', 'tf module', 'infrastructure as code', 'IaC', 'reusable terraform', '.tf files', 'module scaffold'.

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 incomplete.	2 / 3
Completeness	The 'what' is partially present but truncated. The 'when' clause is entirely boilerplate ('Use when appropriate context detected') with no actual trigger guidance, which per the rubric guidelines should cap completeness and here effectively makes the 'when' missing entirely.	1 / 3
Trigger Term Quality	The 'Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.' is completely generic boilerplate with zero natural trigger terms. While 'terraform modules' and 'terraform-module-builder' appear in the body, there are no user-facing trigger keywords like 'terraform module', 'infrastructure as code', 'IaC', '.tf files', etc. explicitly called out.	1 / 3
Distinctiveness Conflict Risk	The mention of 'terraform modules' and 'terraform-module-builder plugin' provides some domain specificity that distinguishes it from generic coding skills, but the truncated description and boilerplate trigger clause weaken its distinctiveness. It could overlap with general Terraform or IaC 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 solid structural overview of building Terraform modules with good organization and a useful error handling table. However, it lacks executable HCL code examples that would make it truly actionable, relying instead on descriptive steps. The workflow would benefit from explicit validation checkpoints with feedback loops, and some prerequisite content is unnecessary for Claude.

Suggestions

Add concrete, executable HCL code snippets for at least versions.tf, a variables.tf with a validation block, and an example module invocation—this would significantly improve actionability.

Integrate validation feedback loops into the workflow steps (e.g., 'If terraform validate fails, review error output, fix the referenced file, and re-run validation before proceeding').

Remove prerequisites that Claude already knows (HCL familiarity, understanding of infrastructure resources) to improve conciseness.

Replace the natural language examples section with a concrete before/after showing a user request and the resulting module file structure with key code snippets.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary content that Claude already knows, such as prerequisites like 'Understanding of the infrastructure resources the module will manage' and 'Familiarity with HCL syntax.' The examples section describes use cases in natural language rather than showing concrete module code, which adds tokens without proportional value.	2 / 3
Actionability	The instructions provide a clear sequence of steps and mention specific commands like 'terraform init && terraform validate', but lack executable code examples. There are no actual HCL code snippets showing a variables.tf with validation rules, a main.tf with resource definitions, or a versions.tf with provider pinning—these would make the skill copy-paste ready rather than descriptive.	2 / 3
Workflow Clarity	The 10-step workflow is clearly sequenced and ends with validation (step 10), but lacks explicit feedback loops for error recovery. There's no 'if validation fails, fix and re-validate' checkpoint, and the error handling table is separate from the workflow rather than integrated as decision points within the steps.	2 / 3
Progressive Disclosure	The content is well-organized with clear sections (Overview, Instructions, Output, Error Handling, Examples, Resources) and links to external resources. However, the skill is somewhat monolithic—the error handling table and examples could benefit from being referenced as separate files, and there are no internal cross-references to supplementary skill files for advanced topics like Terratest integration or sub-module patterns.	2 / 3
	Total	8 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: c8a915c

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.