refactor-module
Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.
81
48%
Does it follow best practices?
Impact
84%
1.05xAverage score across 10 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./terraform/module-generation/skills/refactor-module/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (Terraform modularization) but lacks the explicit trigger guidance essential for skill selection. It provides moderate specificity about the transformation goal but doesn't enumerate concrete actions or include a 'Use when...' clause that would help Claude know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger terms like 'refactor Terraform', 'modularize infrastructure', 'split up .tf files', 'create reusable Terraform modules'
List specific concrete actions such as 'extract resources into child modules', 'define input variables and outputs', 'create module directory structure', 'add module documentation'
Include natural language variations users might say: 'break up Terraform code', 'make Terraform reusable', 'organize infrastructure as code'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Terraform) and the general action (transform monolithic configurations into modules), but lacks specific concrete actions like 'extract resources', 'create variable definitions', 'generate outputs', or 'structure directories'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes 'Terraform', 'modules', and 'configurations' which are relevant, but misses common variations users might say like 'refactor', 'split up', 'modularize', '.tf files', 'infrastructure code', or 'IaC'. | 2 / 3 |
Distinctiveness Conflict Risk | Terraform-specific which helps distinguish from general coding skills, but could overlap with other Terraform skills (e.g., general Terraform writing, Terraform validation, Terraform best practices) without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionable code examples for Terraform module refactoring with complete before/after transformations and state migration commands. However, it suffers from verbosity with unnecessary meta-sections (capability statements, revision history, parameter tables) and could benefit from better progressive disclosure by splitting detailed examples into separate files. Workflow validation checkpoints are implicit rather than explicit.
Suggestions
Remove or drastically reduce meta-sections like 'Capability Statement', 'Prerequisites', 'Input Parameters' table, and 'Revision History' - these add ~50 lines without actionable value
Add explicit validation checkpoints in the workflow, e.g., 'STOP: Run terraform plan and verify no resource recreation before proceeding to step 5'
Split the detailed code examples (before/after transformation, module documentation template) into separate reference files and link to them from the main skill
Integrate the testing section more concretely - either include a complete test example or provide a clearer handoff to the terraform-test skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is verbose with extensive explanations and tables that Claude doesn't need (e.g., 'Capability Statement', 'Prerequisites' sections explaining basic concepts). The code examples are valuable but surrounded by unnecessary scaffolding like revision history tables and parameter tables that add bulk without proportional value. | 2 / 3 |
Actionability | Provides fully executable HCL code examples showing complete before/after transformations, state migration commands, and concrete patterns. The code is copy-paste ready with proper syntax and real-world applicability. | 3 / 3 |
Workflow Clarity | Steps are listed (Analysis, Design, Transformation, Migration, Documentation, Testing) but validation checkpoints are weak. The state migration section mentions testing in non-production but lacks explicit 'stop and verify' gates. Missing feedback loops for the refactoring process itself. | 2 / 3 |
Progressive Disclosure | The skill is monolithic at ~400 lines with inline content that could be split (e.g., the full module code examples, testing section). References to related skills exist but the main content itself lacks appropriate splitting. The testing section just says 'Use skill terraform-test' without clear integration. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (539 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- hashicorp/agent-skills
- Commit
9f2ede9
- 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.