oma-tf-infra

Create or review Terraform infrastructure and plans. Use for cloud resources, IAM, networking, state management, and infrastructure changes.

Quality

68%

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 ./.agents/skills/oma-tf-infra/SKILL.md

Quality

Content

67%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 well-structured, actionable, and safety-conscious with explicit validation and destructive-change controls. Main weaknesses are framework overlap across the three workflow sections and inlined bulk that could live in referenced files.

Suggestions

Collapse the Scheduling, Structural Flow, and Logical Operations sections into a single workflow description to remove overlap and recover tokens.

Move the 17-item guardrails list and the multi-cloud resource mapping table into referenced resources files, keeping only the canonical command path and key guardrails inline.

Sharpen the failure-and-recovery steps into explicit validate-fix-retry loops (e.g. 'on scan failure: fix, re-run scan, only proceed when clean').

Dimension	Reasoning	Score
Conciseness	The body uses dense tables and avoids teaching basics, but the Scheduling, Structural Flow, and Logical Operations sections re-describe the same workflow in overlapping frameworks, adding overhead that could be tightened.	3 / 5
Actionability	Copy-paste canonical commands (terraform init/fmt/validate/plan, checkov, trivy config) plus a concrete multi-cloud resource mapping table give mostly executable guidance, with a few high-level guardrail principles leaving minor gaps.	4 / 5
Workflow Clarity	The PREPARE->ACQUIRE->REASON->ACT->VERIFY->FINALIZE sequence includes a VERIFY checkpoint, a failure-and-recovery section, and an explicit destructive-change stop, but the recovery steps are slightly less crisp than the validate-fix-retry anchor 5.	4 / 5
Progressive Disclosure	A well-signaled References section points one-level-deep to resources/*.md and shared core files with clear section headers, though some bulk content (17 guardrails, the large mapping table) is inlined and no bundle files were present to verify the referenced paths.	4 / 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.

A solid, specific description that covers what and when with natural trigger terms and a clear Terraform niche. It could rise a level by adding concrete user trigger phrasing and a few synonyms/file extensions.

Suggestions

Add concrete user trigger phrasing to the 'when' clause, e.g. 'Use when the user mentions Terraform, .tf files, terraform plan output, or provisioning cloud resources'.

Include natural synonyms/extensions such as IaC, .tf, or .tfvars to lift trigger-term coverage toward comprehensive.

Tighten distinctiveness by naming the IaC/Terraform-specific boundary versus general devops or CI/CD skills.

Dimension	Reasoning	Score
Specificity	"Create or review Terraform infrastructure and plans" names the domain plus two concrete actions (create, review) but no broader action coverage, matching the 1-2-actions anchor rather than the 'several specific actions' of a 4.	3 / 5
Completeness	It states both what ("Create or review Terraform infrastructure and plans") and when ("Use for cloud resources, IAM..."), but the 'when' lists categories rather than concrete user trigger phrases, falling short of the explicit anchor 5.	4 / 5
Trigger Term Quality	"Use for cloud resources, IAM, networking, state management, and infrastructure changes" covers natural terms users say, but omits common synonyms/extensions such as IaC or .tf, so it sits at good-but-not-comprehensive.	4 / 5
Distinctiveness Conflict Risk	The Terraform/IaC niche is mostly distinct, though cloud resources, IAM, and networking carry minor overlap risk with adjacent infra or devops skills rather than the minimal-conflict anchor 5.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: first-fluke/oh-my-agent
Path: .agents/skills/oma-tf-infra/SKILL.md
Commit: 1019f7c

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.