Name: refactor-module
Rating: 52 (1 reviews)
Author: hashicorp

refactor-module

Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/terraform/skills/refactor-module/SKILL.md

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable HCL and a well-sequenced, validated workflow, but it is padded with Terraform-testing definitions Claude already knows and inlines material that belongs in separate bundle files. Tightening the glossary and splitting references would lift the weaker dimensions.

Suggestions

Remove or drastically condense the §6 testing glossary ('Test File', 'Run Block', 'Assert Block', 'Mock Provider', 'Test Modes') — Claude already knows the Terraform testing framework — and instead show one concrete .tftest.hcl example.

Move the full module template and documentation template into bundled reference files under references/ and link to them one level deep, instead of inlining hundreds of lines in SKILL.md.

Either create the referenced examples/ directory as a bundle asset or remove the broken '[examples/](./examples/)' link so navigation is not misleading.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with complete HCL examples, but several sections explain concepts Claude already knows (the §6 glossary defining 'Test File', 'Run Block', 'Assert Block', 'Mock Provider', 'Test Modes') and prose like the testing-concept paragraphs could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready HCL for variables/outputs/resources, `moved` blocks, and concrete `terraform state mv`/`state list`/`show -json` commands, with only a minor gap: the testing section defines concepts but gives no executable .tftest.hcl example.	4 / 5
Workflow Clarity	Clear six-phase sequence with explicit validation for the risky state-migration step ('Always test migration in non-production first', plan/show/apply-migration.tfplan with 'Apply only if plan shows no changes') and a Success Criteria checklist, but the Analysis phase and Testing section lack their own checkpoints.	4 / 5
Progressive Disclosure	Well-sectioned single file, but no bundle files exist and the body inlines bulk reference material (full module templates, a testing glossary) that would suit separate files; the referenced [examples/](./examples/) directory is not bundled, making it a broken reference.	3 / 5
	Total	14 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 clearly conveys what the skill does but lacks any explicit trigger ('Use when') guidance and leans on buzzword padding ('community best practices'). It is a competent but incomplete description that would benefit from concrete trigger phrases.

Suggestions

Add an explicit 'Use when...' clause with natural triggers, e.g. 'Use when refactoring monolithic Terraform configs into modules, or when the user mentions Terraform module extraction, reuse, or state migration.'

Replace 'following HashiCorp's module design principles and community best practices' with one or two concrete actions (e.g. 'extract variables, outputs, moved blocks, and tests') to raise specificity.

Include synonyms users actually say ('refactor Terraform', 'terraform module', 'monolithic .tf') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('monolithic Terraform configurations', 'reusable, maintainable modules') and one concrete action ('Transform... into'), but the trailing 'following HashiCorp's module design principles and community best practices' is aspirational fluff with no further concrete actions.	3 / 5
Completeness	Clearly states the 'what' (transform monolithic configs into modules) but provides no 'when'/'Use when' clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords ('Terraform', 'modules') but misses natural user phrasings like 'refactor terraform', 'terraform module', or 'monolithic', and includes no trigger synonyms or variations.	3 / 5
Distinctiveness Conflict Risk	The Terraform module-refactoring niche is mostly distinct with only minor overlap risk, though the generic 'best practices' framing slightly broadens it.	4 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (561 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: hashicorp/agent-skills
Path: plugins/terraform/skills/refactor-module/SKILL.md
Commit: 3268468

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.