terraform-specialist

Expert Terraform/OpenTofu specialist mastering advanced IaC automation, state management, and enterprise infrastructure patterns.

Quality

48%

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

The canonical home for this skill is terraform-specialist in rmyndharis/antigravity-skills

Quality

Content

35%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 skill body is a verbose persona/capability catalog that restates Terraform concepts Claude already knows, gives no executable code or commands, and provides destructive apply workflows without validation feedback loops.

Suggestions

Cut the lengthy capability enumerations and Knowledge Base lists that restate concepts Claude already knows; keep only non-obvious guidance, conventions, and decisions to lift conciseness.

Replace abstract instructions with executable artifacts: example module skeletons, backend-config snippets, and concrete `terraform`/`tofu` commands for the common cases.

Add explicit validation checkpoints to the plan/apply workflow (e.g., 'terraform validate', review plan output, then apply) with a fix-and-retry feedback loop, since these are destructive operations.

Dimension	Reasoning	Score
Conciseness	The body is a long enumeration of concepts Claude already knows ('Resources, data sources, variables', 'for_each loops', 'Dynamic blocks') restated across many sections, fitting 'noticeably verbose; several unnecessary explanations or padded sections' rather than the mostly-efficient level 3.	2 / 5
Actionability	Guidance is high-level and abstract ('Define environments, providers, and security constraints', 'Implement plan/apply workflows') with no code, commands, or concrete steps, matching 'minimal concrete guidance; high-level hints but missing the specific steps to execute'.	2 / 5
Workflow Clarity	Numbered sequences exist (Instructions 1-4, Response Approach 1-9) but lack validation checkpoints or feedback loops, and because plan/apply operations are destructive the missing validation caps this at 3 per the guideline.	3 / 5
Progressive Disclosure	The file has section headers but is monolithic with no bundle files and no references to separate materials; capability catalogs that should live in reference files are inlined, matching 'some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	10 / 20 Passed

Description

61%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 names a clear niche and strong trigger keywords but relies on abstract expertise language instead of concrete actions and omits any 'Use when' trigger guidance, capping completeness at 3.

Suggestions

Rewrite the description as concrete actions the skill performs (e.g., 'Designs Terraform/OpenTofu modules, manages remote state backends, and implements plan/apply CI/CD pipelines') instead of 'mastering' expertise.

Add an explicit trigger clause such as 'Use when designing Terraform/OpenTofu modules, managing state backends, or setting up IaC CI/CD pipelines' to lift completeness above 3.

Include natural synonyms users say ('infrastructure as code', 'IaC', '.tf', 'modules') to push trigger-term coverage toward 5.

Dimension	Reasoning	Score
Specificity	Names the Terraform/OpenTofu domain plus concrete subject areas ('state management', 'enterprise infrastructure patterns'), but the actions are abstract ('mastering', 'specialist') rather than specific actions the skill performs, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor rather than the explicit action list of level 4.	3 / 5
Completeness	It states a clear 'what' (specialist in IaC automation, state management, enterprise patterns) but has no 'Use when...' or equivalent explicit trigger clause, so per the guideline a missing trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Strong natural keywords users say ('Terraform', 'OpenTofu', 'IaC'), matching 'good keyword coverage; a few natural terms missing' — it lacks spelled-out synonyms like 'infrastructure as code', '.tf', or 'modules'.	4 / 5
Distinctiveness Conflict Risk	'Terraform/OpenTofu specialist' carves a clear niche with minimal conflict risk, fitting 'mostly distinct; minor overlap risk' with general cloud/DevOps skills rather than the fully isolated niche of level 5.	4 / 5
	Total	14 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/terraform-specialist/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.