refactor-module
tessl i github:hashicorp/agent-skills --skill refactor-moduleTransform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.
Validation
75%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (539 lines); consider splitting into references/ and linking | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
Implementation
50%This skill provides excellent, actionable Terraform code examples with realistic before/after transformations and proper HCL syntax. However, it suffers from severe verbosity—explaining concepts Claude already knows, including redundant sections like 'Capability Statement' and 'Prerequisites', and embedding content that should be referenced rather than inline. The workflow lacks explicit validation checkpoints for a process that involves destructive state operations.
Suggestions
Remove the 'Overview', 'Capability Statement', 'Prerequisites', and 'Input Parameters' sections—these explain what Claude already knows or duplicate information in the actual content
Add explicit validation checkpoints in the workflow: 'Run terraform plan and verify NO resource recreation before proceeding' after each state migration step
Move the full module code examples to a referenced EXAMPLES.md file, keeping only a minimal before/after snippet inline
Consolidate the 'Common Pitfalls' and 'Refactoring Patterns' into a single, tighter section with just the code examples and no explanatory prose
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines with significant redundancy. Explains basic concepts Claude knows (what modules are, what encapsulation means), includes lengthy markdown tables for parameters, and repeats similar patterns multiple times. The 'Capability Statement' and 'Prerequisites' sections add little value. | 1 / 3 |
Actionability | Provides fully executable, copy-paste ready HCL code throughout. The before/after transformation examples are complete and realistic, state migration commands are specific, and the module structure shows real working Terraform code with proper validation blocks. | 3 / 3 |
Workflow Clarity | Steps are listed (Analysis → Design → Transform → Migrate → Document → Test) but validation checkpoints are weak. The state migration section mentions 'test in non-production first' but lacks explicit verify-before-proceed gates. Missing feedback loops for the refactoring process itself. | 2 / 3 |
Progressive Disclosure | References external skills and resources at the end, but the main content is a monolithic wall of text. The testing section defers to 'skill terraform-test' but then includes substantial inline content anyway. Content that could be in separate files (full module examples, documentation templates) is inline. | 2 / 3 |
Total | 8 / 12 Passed |
Activation
33%The description identifies a clear domain (Terraform module refactoring) and references best practices, but suffers from missing explicit trigger guidance and lacks specific concrete actions. It would benefit significantly from a 'Use when...' clause and more detailed capability listing to help Claude distinguish this skill from other Terraform-related skills.
Suggestions
Add a 'Use when...' clause with trigger terms like 'refactor Terraform', 'modularize infrastructure', 'split Terraform code', 'create Terraform module'
List specific concrete actions such as 'extract resources into modules', 'define input variables and outputs', 'create module directory structure', 'add module documentation'
Include common user terminology variations: 'IaC', 'infrastructure as code', '.tf files', 'HCL', 'terraform refactoring'
| 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 input variables', 'define outputs', or 'structure directories'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, and the weak 'what' pushes it to 1. | 1 / 3 |
Trigger Term Quality | Includes 'Terraform', 'modules', and 'monolithic' which are relevant, but misses common user terms like 'refactor', 'split', '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 debugging) without clearer scope boundaries. | 2 / 3 |
Total | 7 / 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.