building-terraform-modules
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill building-terraform-modulesExecute 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
0%This skill content is almost entirely boilerplate with no actionable guidance. It describes what the skill does conceptually but provides zero concrete implementation details - no actual Terraform code examples, no plugin invocation syntax, no specific commands. The content reads like a template that was never filled in with real instructions.
Suggestions
Add actual terraform-module-builder plugin invocation syntax with concrete examples (e.g., the exact command or API call to generate a module)
Replace abstract example descriptions with real Terraform code snippets showing expected input/output
Remove generic boilerplate sections (Prerequisites, Instructions, Output, Error Handling, Resources) that contain no skill-specific information
Add validation steps showing how to verify generated modules are correct (e.g., terraform validate, terraform plan)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding explaining concepts Claude already knows (what Terraform modules are, what 'infrastructure as code' means). The 'Overview', 'How It Works', 'When to Use', 'Integration', 'Prerequisites', 'Instructions', 'Output', 'Error Handling', and 'Resources' sections are mostly filler with no actionable content. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. Examples describe what 'the skill will do' abstractly rather than showing actual Terraform code, plugin invocation syntax, or specific commands. The 'Instructions' section is completely generic boilerplate. | 1 / 3 |
Workflow Clarity | The workflow described ('Receiving User Request' -> 'Generating Module Structure' -> 'Customizing Module Content') is vague and lacks any validation checkpoints, specific commands, or error recovery steps. No concrete sequence for actually using the terraform-module-builder plugin. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. The 'Resources' section mentions 'Project documentation' and 'Related skills' without any actual links. Content is poorly organized with redundant sections that could be consolidated or removed. | 1 / 3 |
Total | 4 / 12 Passed |
Activation
17%This description has a clear domain focus (Terraform modules) but is severely undermined by placeholder trigger text that provides no actual selection guidance. The truncated content and generic 'Use when appropriate context detected' boilerplate make it nearly useless for skill selection among multiple options. The first-person framing ('empowers AI assistant') also violates the third-person voice requirement.
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 .tf files'
Complete the truncated text and list specific capabilities (e.g., 'generates variables.tf, outputs.tf, README documentation, input validation')
Rewrite in third person voice: 'Builds reusable Terraform modules...' instead of '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 marketing language rather than concrete capabilities. The truncated text ('sec...') suggests incomplete information. | 2 / 3 |
Completeness | While it partially addresses 'what' (build terraform modules), the 'when' section is entirely placeholder boilerplate ('Use when appropriate context detected') that provides zero guidance on when to select this skill. | 1 / 3 |
Trigger Term Quality | The 'Use when' clause is completely generic placeholder text ('appropriate context detected', 'relevant phrases based on skill purpose') with no actual trigger terms. Users would say 'terraform module', 'infrastructure code', 'IaC' - none of which appear as explicit triggers. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'terraform modules' and 'terraform-module-builder plugin' provides some distinctiveness, but the generic trigger guidance means it could easily conflict with other infrastructure or code generation skills. | 2 / 3 |
Total | 6 / 12 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.