terragrunt-validator

Comprehensive toolkit for validating, linting, testing, and automating Terragrunt configurations, HCL files, and Stacks. Use this skill when working with Terragrunt files (.hcl, terragrunt.hcl, terragrunt.stack.hcl), validating infrastructure-as-code, debugging Terragrunt configurations, performing dry-run testing with terragrunt plan, working with Terragrunt Stacks, or working with custom providers and modules.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

70%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 an excellent, well-validated workflow, but it significantly overruns its token budget: roughly 150+ lines duplicate content already in references/best_practices.md, sections are repeated (two Troubleshooting sections, two mandatory-read instructions), and the reference/index structure is undermined by the inlining. Trimming the body to the workflow plus command reference and pointing to the existing reference files would move this to top-tier.

Suggestions

Remove the duplicated inline best-practices content (the configuration/dependency/security/DRY checklists and the 'Best Practices Integration' ✅/❌ lists) and rely on the single clearly-linked references/best_practices.md, keeping only the quick grep checks inline.

Merge the two 'Troubleshooting' sections into one and consolidate the two separate 'read references/best_practices.md' instructions into the single mandatory Step 0.

Move installation commands, CI/CD, and pre-commit examples into references/advanced_usage.md (or a new reference) to shorten the main body, and mention the bundled assets/test fixture so it is discoverable.

Dimension	Reasoning	Score
Conciseness	The ~630-line body is noticeably padded: two separate "Troubleshooting" sections, two separate passages instructing the reader to cat references/best_practices.md, inline best-practices checklists and ✅/❌ lists that duplicate the 548-line reference file, plus installation and CI/pre-commit boilerplate that could be deferred or dropped.	2 / 5
Actionability	Commands are copy-paste ready throughout — script invocations with environment-variable variations, exact tflint/trivy/checkov commands, grep one-liners, and strict-control examples that cover the common validation cases.	5 / 5
Workflow Clarity	The Validation Workflow is clearly sequenced (mandatory Step 0 read → assessment → documentation lookup → execution → checklist verification) with explicit validation checklists, an error-to-fix mapping, and troubleshooting feedback loops for error recovery.	5 / 5
Progressive Disclosure	All six references/ files and both scripts exist, are one level deep, and are clearly signaled with a summary index, but substantial content that belongs in those references (best-practices checklists, key-practices lists, strict-control detail, install commands) is inlined in SKILL.md, and the bundled assets/test fixture tree is never mentioned.	3 / 5
	Total	15 / 20 Passed

Description

95%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 is a strong example: it states concrete capabilities in third person and follows immediately with an explicit 'Use this skill when...' clause containing file extensions, synonyms, and workflow triggers. The only weakness is mild generic phrasing ('Comprehensive toolkit', 'testing and automating') in the capability list.

Dimension	Reasoning	Score
Specificity	Lists several specific actions ("validating, linting, testing, and automating Terragrunt configurations", "performing dry-run testing with terragrunt plan") but "Comprehensive toolkit" and "testing/automating" are mildly generic, leaving minor gaps versus the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both what ("Comprehensive toolkit for validating, linting, testing, and automating Terragrunt configurations, HCL files, and Stacks") and when ("Use this skill when working with Terragrunt files...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers natural terms with file extensions and synonyms: ".hcl, terragrunt.hcl, terragrunt.stack.hcl", "infrastructure-as-code", "debugging Terragrunt configurations", "terragrunt plan", "Terragrunt Stacks", "custom providers and modules" — matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Terragrunt is a clear niche with tool-specific triggers (terragrunt.hcl, terragrunt.stack.hcl, terragrunt plan); it would not plausibly fire for a non-Terragrunt skill.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (658 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: pantheon-org/tekhne
Path: skills/infrastructure/terragrunt/validator/SKILL.md
Commit: a1083f4

Reviewed: 3 hours 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.