Skip to content
TrustedSkillsbeta
Back to all skills

Terragrunt Validator

Listed
akin-ozer·vlatest·utilities·Apache-2.0

Validates your Terragrunt configurations for syntax and best practices, ensuring infrastructure deployments are error-free and consistent.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add akin-ozer/cc-devops-skills --skill terragrunt-validator -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

akin-ozer

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 5 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: developer.hashicorp.com, opentofu.org, registry.terraform.io, terragrunt.gruntwork.io, trivy.dev.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    raw.githubusercontent.comsource hostregistry.terraform.ioundeclaredtrivy.devundeclaredterragrunt.gruntwork.ioundeclareddeveloper.hashicorp.comundeclaredopentofu.orgundeclaredgithub.comsource host

    What it found (3 of 5)

    • devops-skills-plugin/skills/terragrunt-validator/scripts/detect_custom_resources.py:360contacts registry.terraform.io
      lines.append(f"  → Action: Visit https://registry.terraform.io/modules/{registry_source}")
    • devops-skills-plugin/skills/terragrunt-validator/scripts/validate_terragrunt.sh:174contacts trivy.dev
      print_info "Install trivy: brew install trivy (macOS) or see https://trivy.dev"
    • devops-skills-plugin/skills/terragrunt-validator/scripts/validate_terragrunt.sh:185contacts terragrunt.gruntwork.io
      echo "  - terragrunt: https://terragrunt.gruntwork.io/docs/getting-started/install/"

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 1 place.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

    What it found

    • devops-skills-plugin/skills/terragrunt-validator/SKILL.md:875remote script piped into a shell
      curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sh -s -- -b /usr/local/bin

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • Pinned to a commit: passed

    Scanned akin-ozer/cc-devops-skills at 276af751e6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
276af751e6
Manifest
devops-skills-plugin/skills/terragrunt-validator/SKILL.md
Scanned
7 files, 3,395 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The terragrunt-validator skill enables AI agents to programmatically validate Terragrunt configuration files before deployment. It ensures infrastructure-as-code integrity by checking for syntax errors, missing dependencies, and incorrect variable references within your Terraform ecosystem.

When to use it

  • Before applying terragrunt init or terragrunt apply in CI/CD pipelines to catch errors early.
  • During code reviews to automatically verify that new modules adhere to organizational standards.
  • When refactoring existing infrastructure to ensure no broken links or invalid outputs are introduced.
  • To integrate into automated testing suites that require strict compliance with Terraform best practices.

Key capabilities

  • Validates .terragrunt.hcl files for syntax and structural correctness.
  • Checks for missing remote state configurations and output dependencies.
  • Detects undefined variables and incorrect input parameter mappings.
  • Reports specific line numbers and error messages for failed validations.

Example prompts

  • "Validate my entire Terragrunt workspace at /projects/infrastructure and list all configuration errors found."
  • "Run a validation check on the aws-vpc module to ensure all required inputs are defined in the parent directory."
  • "Scan these .terragrunt.hcl files for missing dependency_blocks that could cause runtime failures during apply."

Tips & gotchas

Ensure your Terragrunt version matches the one used in your target environment, as validation rules may vary between versions. Always run this skill in a clean working directory to avoid caching issues affecting dependency resolution.