infrastructure-terraform

Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.

Quality

71%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/infrastructure-terraform/SKILL.md

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid description with explicit 'Use when' triggers, good keyword coverage across Terraform and multi-cloud domains, and clear distinctiveness. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., defining variables, outputs, provider configurations, module structure).

Suggestions

Add more specific concrete actions to boost specificity, e.g., 'define module inputs/outputs, configure provider blocks, set up remote state, structure module directories'.

Dimension	Reasoning	Score
Specificity	Names the domain (Terraform modules, AWS/Azure/GCP) and mentions some actions ('build reusable modules', 'standardizing cloud provisioning'), but doesn't list multiple concrete actions like 'create VPC modules, define IAM policies, configure state backends'.	2 / 3
Completeness	Clearly answers both 'what' (build reusable Terraform modules for multi-cloud infrastructure) and 'when' with an explicit 'Use when' clause covering creating infrastructure modules, standardizing provisioning, and implementing reusable IaC components.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Terraform', 'modules', 'AWS', 'Azure', 'GCP', 'infrastructure-as-code', 'IaC', 'cloud provisioning', 'reusable'. Good coverage of terms across the domain.	3 / 3
Distinctiveness Conflict Risk	The combination of Terraform, reusable modules, and multi-cloud (AWS/Azure/GCP) creates a clear niche. Unlikely to conflict with general cloud skills, Ansible skills, or non-modular Terraform usage.	3 / 3
	Total	11 / 12 Passed

Implementation

52%

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

The skill provides solid, executable Terraform module examples with good HCL code quality, but suffers from a lack of workflow guidance — there's no sequenced process for creating, validating (terraform validate/plan), and deploying modules, which is critical for infrastructure operations. The content is moderately verbose with some sections that don't add value for Claude, and the referenced bundle files don't exist, undermining the progressive disclosure structure.

Suggestions

Add a clear workflow section with sequenced steps: write module → terraform fmt → terraform validate → terraform plan → review plan output → terraform apply, with explicit validation checkpoints and error recovery guidance.

Remove or significantly condense the 'Purpose', 'When to Use', and 'Best Practices' sections — these restate information Claude already knows and consume tokens without adding actionable value.

Either provide the referenced bundle files (assets/vpc-module/, references/aws-modules.md, etc.) or remove the references; currently they point to non-existent resources.

Add a brief 'Common pitfalls' section with specific Terraform gotchas (e.g., count vs for_each migration issues, state management considerations) that would be genuinely useful guidance Claude might not infer.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary content like the 'Purpose' and 'When to Use' sections that restate obvious information. The full VPC module example with variables.tf and outputs.tf is quite lengthy and could be more condensed, though the code itself is useful. The 'Best Practices' list contains items Claude already knows (e.g., 'Document all variables with descriptions').	2 / 3
Actionability	The skill provides fully executable, copy-paste ready HCL code for a complete VPC module including main.tf, variables.tf, and outputs.tf. The module composition example and Terratest code are concrete and runnable. Variable validation blocks and tag merging patterns are specific and immediately usable.	3 / 3
Workflow Clarity	There is no clear workflow sequence for creating, validating, or deploying modules. The skill presents patterns and examples but lacks a step-by-step process with validation checkpoints. For infrastructure operations (which are destructive/batch), there's no mention of terraform plan, terraform validate, or any feedback loop for catching errors before apply.	1 / 3
Progressive Disclosure	The skill references external files (assets/vpc-module/, references/aws-modules.md, etc.) which is good structure, but no bundle files exist to support these references. The main content is somewhat monolithic with the full VPC example inline rather than referenced. The section organization is reasonable but the balance between inline content and references could be improved.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ucdavis/ai-skills-registry
Commit: c0b2e4b

Reviewed: about 14 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.