Name: terraform-module-library
Rating: 51.2 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

terraform-module-library

Production-ready Terraform module patterns for AWS, Azure, and GCP infrastructure.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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-module-library/SKILL.md

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

Quality

Content

57%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 content is a strong, code-heavy reference with complete executable AWS VPC examples and a Terratest harness, but it is held back by generic boilerplate sections, no explicit validated build workflow, and a reference structure where most cited files (and the cited assets/ and resources/ directories) do not exist. Tightening the filler and either creating or removing the dangling references would materially improve the score.

Suggestions

Replace the generic Instructions and "Do not use this skill when" boilerplate with a concrete numbered module-build workflow that includes an explicit validate-fix-retry checkpoint (e.g. `terraform validate`, `terraform fmt -check`, then Terratest).

Fix or remove dangling references: create references/azure-modules.md and references/gcp-modules.md, correct `resources/implementation-playbook.md` to the actual references/ path, and either add the assets/vpc-module/ and assets/rds-module/ bundles or drop those entries.

Move the full inline VPC module into assets/vpc-module/ and keep SKILL.md as a concise overview with a worked snippet, so the bulk lives one level deep as the progressive-disclosure rubric expects.

Dimension	Reasoning	Score
Conciseness	The body leads with concrete, non-padded code, but the generic Instructions ("Clarify goals, constraints, and required inputs... Provide actionable steps and verification.") and near-tautological "Do not use this skill when" section add filler Claude does not need, matching the score-3 anchor of mostly efficient with some unnecessary explanation; it is not 4 because that boilerplate is clearly trimmable.	3 / 5
Actionability	Complete, copy-paste-ready HCL for an AWS VPC module plus a Terratest Go test and module-composition examples give mostly executable guidance; it stops short of 5 because only AWS is fully exemplified while Azure and GCP rely on reference files that are largely absent.	4 / 5
Workflow Clarity	There is a loose implied sequence (module structure -> standard pattern -> test) but no explicit numbered build workflow with validation checkpoints, and Terraform apply/destroy are destructive operations run without a validate-fix-retry feedback loop, so per the rubric cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	A dedicated "Reference Files" section signals references and content is sectioned, but of the six referenced paths only references/aws-modules.md actually exists, the body points to a non-existent resources/implementation-playbook.md, and a full VPC module is inlined that belongs in the missing assets/vpc-module/; this is below 4 because the broken and missing references are more than a minor organization gap.	3 / 5
	Total	13 / 20 Passed

Description

56%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 clean, third-person noun phrase that names a specific multi-cloud niche, but it omits concrete actions and any 'Use when...' trigger guidance, capping completeness at 3. Adding explicit trigger phrases and one or two action verbs would raise specificity and completeness.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when building reusable Terraform modules, standardizing multi-cloud provisioning, or establishing organizational IaC standards.'

Include concrete action verbs (create, scaffold, test, version) so the description states what the skill does, not just what it is about.

Add natural synonyms and file extensions (e.g. 'infrastructure as code', 'IaC', '.tf') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Terraform module patterns for AWS, Azure, and GCP infrastructure" names the domain concretely but contains no action verbs, matching the score-2 anchor "Names the domain but actions are minimal or generic"; it is not a 3 because no concrete actions (e.g. create, provision, test) are listed.	2 / 5
Completeness	It clearly states what the skill provides ("Production-ready Terraform module patterns...") but has no "Use when..." clause or equivalent trigger guidance, so per the rubric cap it cannot exceed 3; it is above 2 because the "what" is clear rather than vague.	3 / 5
Trigger Term Quality	Natural terms a user would say are present ("Terraform module", "AWS", "Azure", "GCP", "infrastructure"), giving good coverage; it falls short of 5 because synonyms like "infrastructure as code"/"IaC" and file extensions (.tf) are missing.	4 / 5
Distinctiveness Conflict Risk	"Terraform module patterns for AWS, Azure, and GCP" carves a specific niche with minimal conflict risk against unrelated skills; it is not 5 because of minor overlap with broad infrastructure-as-code or multi-cloud-architecture skills.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/terraform-module-library/SKILL.md
Commit: debb2ec

Reviewed: 1 day 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.