CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/terragrunt-toolkit

Complete terragrunt toolkit with generation and validation capabilities

93

Quality

93%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

criteria.jsonvalidator/evals/scenario-1/

{
  "context": "Agent applies the Configuration Pattern Checklist from the terragrunt-validator skill to HCL files with three deliberate violations: unnamed include, bare include{} syntax, and root file named terragrunt.hcl.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Root file naming violation identified",
      "description": "Agent flags that infrastructure/terragrunt.hcl should be named root.hcl per Terragrunt 0.93+ conventions and marks this item as FAIL.",
      "max_score": 25
    },
    {
      "name": "Bare (unnamed) include block violation identified",
      "description": "Agent identifies that the child module uses a bare 'include {}' without a name label and marks this as FAIL, recommending 'include \"root\" { ... }' syntax.",
      "max_score": 25
    },
    {
      "name": "find_in_parent_folders without explicit filename flagged",
      "description": "Agent identifies that find_in_parent_folders() without an argument should be updated to find_in_parent_folders(\"root.hcl\") once the root file is renamed.",
      "max_score": 20
    },
    {
      "name": "env.hcl naming and read_terragrunt_config usage assessed as pass",
      "description": "Agent correctly assesses that env.hcl naming and use of read_terragrunt_config(find_in_parent_folders(\"env.hcl\")) passes the checklist.",
      "max_score": 15
    },
    {
      "name": "Fix recommendations provided for each failure",
      "description": "Agent provides specific HCL code snippets showing the corrected include block syntax and the renamed root file reference.",
      "max_score": 15
    }
  ]
}

tile.json