terraform-starter

Scaffold Terraform 1.9+ infrastructure with provider configuration (AWS/GCP/Azure), modular structure, remote state, variables, outputs, workspaces, and common resource patterns.

Quality

71%

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 ./infrastructure/terraform-starter/SKILL.md

Quality

Content

72%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 highly actionable with complete, copy-paste-ready Terraform code, but it presents destructive terraform workflows without explicit validation checkpoints and inlines all module examples in a single monolithic file rather than progressively disclosing them via reference files.

Suggestions

Add an explicit sequenced workflow with validation gates, e.g. 'init -> fmt -> validate -> plan -out -> review plan -> apply the saved plan', with a 'do not apply until plan is reviewed' checkpoint.

Move the full VPC/RDS/S3 module implementations into reference files (e.g. references/modules-networking.md) and keep SKILL.md as an overview that links to them one level deep.

Remove the redundant Project Structure listing since the Scaffold Command already conveys the same file tree, trimming tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code and brief rule lists with no over-explanation of concepts Claude already knows; the only minor redundancy is the Project Structure section re-listing files already created by the Scaffold Command, keeping it just below the every-token-earns-its-place anchor 5.	4 / 5
Actionability	Fully executable, copy-paste-ready guidance throughout: a runnable scaffold script, complete HCL for backend/providers/variables/main composition, full VPC/RDS/S3 modules, and concrete terraform CLI commands covering the common cases.	5 / 5
Workflow Clarity	Common Commands gives an implicit sequence (init, fmt, validate, plan -out, apply) but no explicit validation checkpoints or feedback loops; because apply/destroy are destructive, the rubric caps workflow clarity at 3, and the lack of a 'review plan before applying' gate confirms the cap rather than pushing lower.	3 / 5
Progressive Disclosure	No bundle files exist and the entire ~400-line reference (full module implementations included) is inlined in SKILL.md rather than split into one-level-deep reference files; internal section headers give some structure, but content that belongs in separate files is inlined with no references, matching anchor 3.	3 / 5
	Total	15 / 20 Passed

Description

70%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 concrete, domain-specific, and clearly distinguishable, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness at the midpoint and limits overall quality.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when scaffolding new Terraform 1.9+ projects, setting up multi-cloud provider config, or establishing remote state and module structure.'

Add natural synonyms users say, such as 'infrastructure as code' or 'IaC', to broaden trigger coverage.

Replace the generic tail 'common resource patterns' with a concrete action (e.g. 'provision VPC, RDS, and S3 resource patterns') to push specificity toward anchor 5.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates concrete components — "provider configuration (AWS/GCP/Azure), modular structure, remote state, variables, outputs, workspaces, and common resource patterns" — but a single verb ("Scaffold") carries the action list, with "common resource patterns" remaining generic, so it sits just below the comprehensive-multi-action anchor 5.	4 / 5
Completeness	The "what" is clear (scaffold Terraform infra with the listed components), but there is no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 3 — the "when" is only weakly implied.	3 / 5
Trigger Term Quality	Strong natural keywords a user would say ("Terraform", "infrastructure", "AWS/GCP/Azure", "remote state", "workspaces"), but common synonyms like "infrastructure as code" / "IaC" are absent, leaving it a step below the comprehensive-synonym anchor 5.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (Terraform 1.9+ multi-cloud scaffolding with remote state and workspaces) with distinct, domain-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: infrastructure/terraform-starter/SKILL.md
Commit: 181fcbc

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.