terraform-module-creator
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 extremely weak, essentially consisting of a skill title repeated with boilerplate category metadata. It provides no concrete actions, no natural trigger terms beyond the skill name itself, and no guidance on when Claude should select this skill. It would be nearly useless for skill selection in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Terraform module scaffolding with variables.tf, outputs.tf, main.tf, and README; generates input/output variable definitions; structures reusable infrastructure components.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a Terraform module, scaffold a tf module, build reusable infrastructure components, or generate HCL module structure.'
Remove the duplicated trigger term ('terraform module creator' listed twice) and replace with varied natural language phrases users would actually say, such as 'create terraform module', 'tf module template', 'reusable terraform component'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Terraform Module Creator') but does not describe any concrete actions like 'creates module scaffolding', 'generates variables.tf', or 'writes provider configurations'. It is essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title and completely lacks a 'when should Claude use it' clause with explicit triggers. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'terraform module creator' repeated twice. It misses natural user phrases like 'create a terraform module', 'tf module', 'infrastructure as code module', 'HCL module', or 'write a terraform module'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Terraform Module Creator' does narrow the domain to Terraform modules specifically, which provides some distinctiveness. However, the lack of concrete actions or clear trigger guidance means it could still overlap with general Terraform or IaC 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 an empty placeholder with no actual content. It contains only generic boilerplate text that repeats the phrase 'terraform module creator' without providing any Terraform code, module structure patterns, best practices, or actionable guidance. It fails on every dimension because it teaches Claude nothing it doesn't already know.
Suggestions
Add concrete, executable Terraform module examples showing proper directory structure (main.tf, variables.tf, outputs.tf, versions.tf) with actual HCL code.
Define a clear workflow for module creation: 1) scaffold structure, 2) define variables/outputs, 3) implement resources, 4) validate with `terraform validate` and `terraform plan`, 5) test with examples.
Include specific best practices such as variable validation blocks, proper provider version constraints, README generation, and input/output documentation conventions.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than teaching how to create Terraform modules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'terraform module creator' excessively, and provides zero actual technical content. Every section restates the same vague idea without adding value. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no Terraform code, no module structure, no commands, no examples of actual module creation. The content describes rather than instructs, with phrases like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains zero steps for creating a Terraform module. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to supporting files, and no bundle files exist. The sections are superficial headers over empty platitudes rather than a structured information hierarchy. | 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 | |
- Commit
13d35b8
- 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.