CtrlK
BlogDocsLog inGet started
Tessl Logo

terraform-infrastructure

Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale.

52

Quality

58%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 workflow is well-structured into clear sequenced phases with a closing checklist, and it stays concise without over-explaining. Its main gaps are a lack of executable, concrete guidance and missing validation checkpoints within destructive operations.

Suggestions

Replace high-level action lists with executable commands or code, e.g. `terraform init`, `terraform plan -out=tfplan`, and a minimal module skeleton, so each phase is copy-paste runnable.

Add explicit validation checkpoints inside destructive phases — e.g. 'Run `terraform validate` and review `terraform plan` before `terraform apply`' — to lift workflow clarity above the cap.

Move per-phase detail (skills-to-invoke mapping, examples) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and stays mostly lean with short action lists and minimal copy-paste prompts, though the seven near-identical phase blocks add some repetitive token weight that could be trimmed.

4 / 5

Actionability

Guidance is high-level — numbered tasks like 'Initialize Terraform' and 'Configure backend' plus delegation prompts ('Use @terraform-skill to set up Terraform project') — without executable commands, real Terraform code, or the concrete steps needed to actually perform each action.

2 / 5

Workflow Clarity

The seven phases are clearly sequenced and a quality-gate checklist closes the workflow, but destructive/batch operations (provisioning, state management, CI/CD apply) lack inline validation checkpoints such as `terraform validate` or plan-before-apply, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

The single file is reasonably sectioned into phases, but no bundle files exist and all phase detail is inlined with no external references, so content that could be split out remains monolithic.

3 / 5

Total

12

/

20

Passed

Description

66%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 specific and well-targeted to a Terraform IaC niche, with solid trigger terms and low conflict risk. Its main weakness is the complete absence of explicit 'when to use' guidance, which caps its completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when provisioning cloud infrastructure with Terraform, building reusable modules, or managing multi-environment state.'

Add natural trigger synonyms users might say ('Terraform modules', 'IaC', 'state management', '.tf files') to broaden keyword coverage.

Tighten 'managing infrastructure at scale' to a more concrete action like 'managing Terraform state and multi-environment deployments' to reduce overlap with generic DevOps skills.

DimensionReasoningScore

Specificity

The description names the domain (Terraform IaC) and lists several concrete actions — 'provisioning cloud resources, creating reusable modules, and managing infrastructure at scale' — though 'managing infrastructure at scale' is somewhat abstract, leaving minor coverage gaps rather than full comprehensiveness.

4 / 5

Completeness

It clearly answers 'what' the skill does but omits any explicit 'when'/'Use when...' trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

It surfaces natural terms a user would say ('Terraform', 'infrastructure as code', 'cloud resources', 'modules') with good coverage, but lacks synonyms or file-extension variants that would push it to comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Terraform-specific framing creates a clear niche with minimal conflict risk against non-Terraform skills, though 'managing infrastructure at scale' leaves minor overlap with adjacent DevOps/IaC skills.

4 / 5

Total

15

/

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.

Validation — 15 / 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.