Terraform Module Creator - Auto-activating skill for DevOps Advanced. Triggers on: terraform module creator, terraform module creator Part of the DevOps Advanced skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/02-devops-advanced/terraform-module-creator/SKILL.mdQuality
Discovery
7%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 is essentially a placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining capabilities, use cases, or providing natural trigger terms. The repeated trigger term and boilerplate category information add no value.
Suggestions
Add specific actions the skill performs, e.g., 'Creates reusable Terraform modules with proper structure including variables.tf, outputs.tf, and main.tf files, implements best practices for module design'
Add a 'Use when...' clause with natural trigger terms like 'create terraform module', 'tf module', 'reusable infrastructure', 'HCL module', 'infrastructure as code module'
Differentiate from general Terraform skills by specifying the scope - is this for AWS, Azure, GCP modules? Does it handle testing, documentation, or versioning?
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Terraform Module Creator' without describing any concrete actions. It doesn't explain what creating a Terraform module involves - no mention of writing HCL, defining resources, outputs, variables, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' line is redundant and doesn't constitute proper usage guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'terraform module creator' repeated twice. Missing natural variations users would say like 'create terraform module', 'tf module', 'infrastructure as code', 'HCL', or 'write terraform'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Terraform Module Creator' is somewhat specific to Terraform, the lack of detail about what distinguishes this from general Terraform skills or IaC skills creates potential overlap. The category mention 'DevOps Advanced' doesn't help differentiation. | 2 / 3 |
Total | 5 / 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 content is essentially a placeholder with no actionable information. It describes what a Terraform module creator skill would do without providing any actual guidance on creating Terraform modules. The entire content could be replaced with a single executable example and would be infinitely more useful.
Suggestions
Add a concrete example showing a complete minimal Terraform module structure (main.tf, variables.tf, outputs.tf) with executable code
Include a step-by-step workflow for creating a module: 1) Create directory structure, 2) Define variables, 3) Write resources, 4) Define outputs, 5) Validate with 'terraform validate'
Provide specific commands: 'terraform fmt', 'terraform validate', 'terraform-docs' for documentation generation
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual Terraform module patterns and best practices
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no Terraform code, no module structure, no commands, no examples of actual module creation. The content describes what the skill does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Creating Terraform modules involves specific steps (directory structure, variables.tf, outputs.tf, main.tf, etc.) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual technical content to organize. There are no references to detailed materials, examples, or related documentation. | 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 | |
994edc4
Table of Contents
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.