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
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 restates the skill name without providing any meaningful information about capabilities, use cases, or trigger conditions. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection among a large set of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Terraform module scaffolding with variables, outputs, providers, and README documentation.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a Terraform module, scaffold HCL configurations, generate tf module boilerplate, or structure infrastructure-as-code modules.'
Remove the redundant 'Triggers on' line that just repeats the skill name, and replace it with diverse natural language phrases users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Terraform Module Creator') but provides no concrete actions. It does not describe what the skill actually does—no mention of creating modules, generating configurations, defining variables, outputs, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no 'when should Claude use it' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'terraform module creator' repeated twice. It misses natural user phrases like 'create terraform module', 'tf module', 'infrastructure as code', 'HCL', 'terraform configuration', or 'module scaffolding'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Terraform Module Creator' provides some domain specificity that distinguishes it from generic coding or document skills, but the lack of concrete actions or scope means it could overlap with other Terraform-related or DevOps skills. | 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 is essentially a placeholder template with no real content. It contains no Terraform code, no module structure guidance, no HCL examples, no best practices, and no actionable instructions whatsoever. It merely repeats the phrase 'terraform module creator' in various wrapper sentences without teaching Claude anything useful.
Suggestions
Add concrete, executable Terraform HCL examples showing a complete module structure (main.tf, variables.tf, outputs.tf) with realistic resource definitions.
Provide a clear step-by-step workflow for creating a Terraform module: directory structure → variable definitions → resource implementation → validation (`terraform validate`, `terraform plan`) → testing.
Include specific best practices such as input validation with variable constraints, output definitions, README generation, and versioning conventions rather than vague claims about 'industry best practices'.
Remove all meta-description content (Purpose, When to Use, Example Triggers, Capabilities) and replace with actual instructional content that teaches how to build production-ready Terraform modules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'terraform module creator' numerous times without providing any actual Terraform knowledge, code, or configuration. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete guidance—no Terraform code, no module structure, no HCL examples, no commands. The content only describes what the skill theoretically does without instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence is provided. The bullet 'Provides step-by-step guidance' is a claim, not actual step-by-step guidance. There are no validation checkpoints or any process to follow. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no references to detailed files, no structured sections with real content, and no navigation to deeper resources. The sections are superficial headers over empty platitudes. | 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 | |
c8a915c
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.