CtrlK
BlogDocsLog inGet started
Tessl Logo

terraform-aws-modules

Terraform module creation for AWS — reusable modules, state management, and HCL best practices. Use when building or reviewing Terraform AWS infrastructure.

64

Quality

77%

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-aws-modules/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

A compact, actionable skill with executable examples and concrete commands. Its main gap is workflow clarity: destructive Terraform operations are not presented as a sequenced, validated workflow.

Suggestions

Reframe the Instructions as a sequenced workflow with explicit checkpoints: write modules → terraform fmt → terraform validate → terraform plan (review) → terraform apply, with a re-validate/replan feedback loop on failure.

Drop the 'You are an expert in Terraform...' opener to tighten conciseness, since the role is already implied by the skill.

DimensionReasoningScore

Conciseness

The body is lean with no over-explanation of concepts Claude already knows, but the opening 'You are an expert in Terraform...' role statement is mild padding that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready executable HCL for a VPC module and an S3 backend, plus concrete commands (terraform fmt/validate, terraform force-unlock) covering the common cases.

5 / 5

Workflow Clarity

The numbered Instructions are best-practice rules rather than a sequenced workflow, and destructive terraform apply lacks explicit validate→plan→apply checkpoints; the destructive-operations cap applies.

3 / 5

Progressive Disclosure

Content is well-organized into clear sections (Use when, Do not use, Instructions, Examples, Best Practices, Troubleshooting) and is self-contained with no need for external references, though at ~70 lines it slightly exceeds the simple-skill threshold.

4 / 5

Total

16

/

20

Passed

Description

78%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.

A concise, well-structured description that answers both what and when with an explicit trigger clause. The main weakness is the generic 'HCL best practices' phrasing, which blunts specificity.

Suggestions

Replace 'HCL best practices' with concrete actions such as 'pin provider versions, use for_each for stable resource identity' to lift specificity.

Add natural synonyms/extensions like 'IaC' or '.tf files' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the AWS/Terraform domain plus a couple concrete actions ('module creation', 'state management'), but 'HCL best practices' is generic fluff rather than a specific action, so coverage is not comprehensive.

3 / 5

Completeness

Clearly states what it does ('Terraform module creation for AWS — reusable modules, state management, and HCL best practices') and gives an explicit 'Use when building or reviewing Terraform AWS infrastructure' trigger phrase.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('Terraform', 'AWS', 'modules', 'infrastructure', 'state management') with an explicit 'Use when building or reviewing' trigger, but misses common synonyms/extensions like 'IaC' or '.tf'.

4 / 5

Distinctiveness Conflict Risk

The Terraform-for-AWS niche is well-defined with distinct triggers, but 'infrastructure' and 'HCL best practices' leave minor overlap risk with adjacent cloud/IaC skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.