CtrlK
BlogDocsLog inGet started
Tessl Logo

terraform-infrastructure

Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale.

39

Quality

37%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/terraform-infrastructure/SKILL.md

The canonical home for this skill is terraform-infrastructure in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

21%Scale 1-5

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

This skill is essentially a hollow orchestration document that delegates all actual work to other skills without providing any concrete Terraform knowledge, code examples, or executable commands. It follows a repetitive template across 7 phases that adds structural bulk without substance. The complete absence of HCL code, CLI commands, or specific configuration guidance makes it nearly useless as a standalone skill for Terraform infrastructure work.

Suggestions

Add concrete, executable Terraform examples: at minimum include HCL snippets for provider configuration, a basic resource definition, and module structure, plus key CLI commands like `terraform init`, `terraform plan`, `terraform apply`.

Add explicit validation steps within the workflow: include `terraform validate`, `terraform plan` review before apply, and `terraform state list` for state verification — these are critical for destructive infrastructure operations.

Replace vague action items ('Configure networking', 'Set up compute') with specific, actionable guidance or at least concrete examples of what these look like in Terraform HCL.

Either inline essential Terraform content or ensure the referenced skills (terraform-skill, terraform-specialist, etc.) actually exist in the bundle — currently the skill delegates everything but provides nothing itself.

DimensionReasoningScore

Conciseness

The skill is heavily padded with repetitive structure across 7 phases that all follow the same template of 'Skills to Invoke / Actions / Copy-Paste Prompts' without providing any actual Terraform knowledge. It lists vague action items like 'Design infrastructure' and 'Configure networking' that add no value. The 'Copy-Paste Prompts' sections are just one-line delegations to other skills.

2 / 5

Actionability

There is zero executable guidance anywhere in this skill — no Terraform code, no HCL examples, no CLI commands (not even `terraform init` or `terraform plan`), no configuration snippets. Every 'action' is a vague directive like 'Configure backend' or 'Set up compute' with no concrete steps. The 'Copy-Paste Prompts' just delegate to other skills without providing any actual instructions.

1 / 5

Workflow Clarity

While there is a rough 7-phase sequence, the steps within each phase are vague bullet points with no specifics. There are no validation checkpoints within phases — the Quality Gates at the end are superficial checklists ('Resources provisioned', 'Modules working') with no guidance on how to verify. For infrastructure operations that are destructive/batch in nature, the complete absence of validation steps like `terraform plan` review before `terraform apply` is a critical gap.

2 / 5

Progressive Disclosure

The skill references multiple external skills and workflows (terraform-skill, terraform-specialist, terraform-module-library, etc.), which suggests an intent for progressive disclosure. However, none of these referenced files are provided in the bundle, and the SKILL.md itself contains no substantive content — it's essentially just a routing table to other skills with no useful overview content of its own.

3 / 5

Total

8

/

20

Passed

Description

53%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 identifies the domain (Terraform) and lists a few high-level capabilities, but lacks a 'Use when...' clause which is critical for skill selection. The trigger terms are reasonable but miss common synonyms, file extensions, and specific Terraform commands that users would naturally mention. Adding explicit trigger guidance and more concrete actions would significantly improve this description.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Terraform', '.tf files', 'HCL', 'terraform plan', 'terraform apply', 'infrastructure as code', 'IaC'.

Include more specific concrete actions such as 'writing HCL configurations', 'managing Terraform state', 'running plan/apply workflows', 'configuring providers (AWS, GCP, Azure)'.

Add common synonyms and file extensions like 'IaC', '.tf', '.tfvars', 'HCL' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Terraform/infrastructure as code) and mentions a few actions ('provisioning cloud resources', 'creating reusable modules', 'managing infrastructure at scale'), but these are somewhat high-level and not deeply concrete (e.g., no mention of plan/apply, state management, specific providers, etc.).

3 / 5

Completeness

Has a clear 'what' (Terraform workflow for provisioning, modules, managing infrastructure) but completely lacks a 'when' clause or explicit trigger guidance. Per rubric guidelines, missing 'Use when...' caps completeness at 3.

3 / 5

Trigger Term Quality

Includes 'Terraform', 'infrastructure as code', 'cloud resources', and 'modules' which are relevant keywords, but misses common natural terms like 'IaC', '.tf files', 'terraform plan', 'terraform apply', 'HCL', 'state file', or specific cloud providers (AWS, GCP, Azure).

3 / 5

Distinctiveness Conflict Risk

Mentioning 'Terraform' specifically makes it fairly distinct from other infrastructure or cloud skills (e.g., CloudFormation, Pulumi, Ansible). However, 'provisioning cloud resources' and 'managing infrastructure at scale' could overlap with other IaC or cloud management skills.

4 / 5

Total

13

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.