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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill building-terraform-modules25
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/skillValidation for skill structure
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 completely useless placeholder trigger guidance. While it identifies the terraform module domain, the 'Use when appropriate context detected' clause is boilerplate that provides no value for skill selection. The description also incorrectly uses imperative voice ('Execute this skill empowers') rather than third person.
Suggestions
Replace the placeholder 'Use when appropriate context detected' with specific triggers like 'Use when user asks to create terraform modules, generate infrastructure-as-code, build reusable IaC components, or mentions terraform, .tf files, or module development'
Complete the truncated description to list all specific capabilities (e.g., 'generates module structure, creates variables.tf, outputs.tf, README documentation, and example usage')
Rewrite in third person voice: 'Builds reusable Terraform modules...' instead of 'Execute this skill empowers AI assistant to build...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (terraform modules) and mentions some actions (build, generate), but 'production-ready, well-documented' is vague and the description is truncated with '...' suggesting incomplete information. | 2 / 3 |
Completeness | The 'what' is partially present but truncated. The 'when' clause is placeholder text that provides zero guidance - 'Use when appropriate context detected' is meaningless for skill selection. | 1 / 3 |
Trigger Term Quality | The 'Use when' clause is completely generic boilerplate ('appropriate context detected', 'relevant phrases based on skill purpose') with no actual trigger terms. Users would say 'terraform module', 'infrastructure code', 'IaC' but none are listed. | 1 / 3 |
Distinctiveness Conflict Risk | Mentions 'terraform modules' and 'terraform-module-builder plugin' which provides some distinctiveness, but the generic trigger clause and truncated description reduce clarity about when this should be selected over other infrastructure/code generation skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a template with placeholder content that provides no actionable guidance. It describes what it claims to do in abstract terms but never shows actual Terraform code, plugin invocation syntax, or concrete examples. The content is padded with generic boilerplate sections that add no value.
Suggestions
Add actual plugin invocation syntax showing how to call the terraform-module-builder plugin with specific parameters
Replace abstract example descriptions with actual Terraform code snippets showing expected input/output
Remove placeholder sections (Prerequisites, Output, Error Handling, Resources) or populate them with concrete, useful information
Consolidate redundant sections (Overview, How It Works, When to Use) into a single concise introduction
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with excessive explanation of concepts Claude already knows. Contains redundant sections ('Overview' repeats the description, 'How It Works' is vague, 'Instructions' section is generic boilerplate). The 'Prerequisites', 'Output', 'Error Handling', and 'Resources' sections are placeholder text with no actual content. | 1 / 3 |
Actionability | No executable code, no concrete commands, no actual Terraform examples. The examples describe what 'the skill will do' abstractly rather than showing actual Terraform code or plugin invocation syntax. References a 'terraform-module-builder plugin' but never shows how to invoke it. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists vague steps without any concrete commands or validation checkpoints. No actual workflow for using the plugin is provided - just abstract descriptions like 'invoke the terraform-module-builder plugin' without showing how. | 1 / 3 |
Progressive Disclosure | Monolithic content with no references to external files. Contains placeholder sections ('Resources' just says 'Project documentation') that add no value. Content is poorly organized with redundant sections that could be consolidated or removed entirely. | 1 / 3 |
Total | 4 / 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 | |
- 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.