CtrlK
BlogDocsLog inGet started
Tessl Logo

oma-tf-infra

Infrastructure-as-code specialist for multi-cloud provisioning using Terraform across any provider (AWS, GCP, Azure, Oracle Cloud). Use for terraform plan/apply, state management, compute, databases, storage, networking, IAM, OIDC, cost optimization, policy-as-code, ISO/IEC 42001 AI controls, ISO 22301 continuity, and ISO/IEC/IEEE 42010 architecture documentation.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, sequenced IaC workflow with explicit validation and destructive-change guardrails, but it is somewhat verbose with duplicated references, lacks inline HCL examples, and points to bundle files that are not actually present.

Suggestions

Remove the duplicated reference listing (lines 192-205 repeat paths already given in 182-190) and consolidate into a single clearly signaled References section to improve conciseness.

Add at least one minimal, executable inline HCL snippet (e.g., a pinned provider block with remote state backend) so the body has copy-paste-ready Terraform code rather than deferring all HCL to external files.

Either ship the referenced resources/*.md and ../_shared/core/*.md bundle files or replace the dead references with inline content, since the progressive-disclosure structure currently points to non-existent files.

DimensionReasoningScore

Conciseness

Mostly task-specific operational guidance without explaining concepts Claude already knows, but it is lengthy (~205 lines) and the References block lists the same paths twice, so it is not lean enough for the top anchor.

2 / 3

Actionability

Provides concrete executable commands (terraform fmt/validate/plan, checkov, tfsec) and specific provider-detection and multi-cloud mapping tables, but actual HCL examples are deferred to external resource files rather than shown inline, leaving the executable-code dimension incomplete.

2 / 3

Workflow Clarity

A clear sequenced workflow (Entry -> PREPARE/ACQUIRE/REASON/ACT/VERIFY/FINALIZE -> Transitions -> Failure/recovery -> Exit) with explicit validation checkpoints and destructive-change feedback loops, avoiding the validation-gap cap at 2.

3 / 3

Progressive Disclosure

References are one-level-deep and clearly signaled, but none of the referenced bundle files (resources/*.md, ../_shared/core/*.md) actually exist in the skill directory, so the structure cannot be verified and the references are not real files; the listing is also duplicated.

2 / 3

Total

9

/

12

Passed

Description

100%

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 strong: third-person voice, explicit 'what' and 'when' with a clear 'Use for' trigger clause, and concrete actions and natural keywords across the Terraform/IaC domain. It is clearly distinct from non-infrastructure skills.

DimensionReasoningScore

Specificity

Lists many specific concrete actions across multiple domains (multi-cloud provisioning, terraform plan/apply, state management, cost optimization, policy-as-code, architecture documentation), matching the 'lists multiple specific concrete actions' anchor and exceeding the 'names domain and some actions' level.

3 / 3

Completeness

Explicitly answers both what ('Infrastructure-as-code specialist for multi-cloud provisioning using Terraform...') and when via an explicit 'Use for...' trigger clause, so it is not capped at the 'when missing or only implied' level.

3 / 3

Trigger Term Quality

Core natural terms a user would say are well covered ('Terraform', 'terraform plan/apply', 'state management', 'compute, databases, storage, networking', 'IAM, OIDC', 'cost optimization'), matching good coverage despite a few technical ISO/spec references.

3 / 3

Distinctiveness Conflict Risk

Has a clear Terraform/IaC niche with provider-specific and ISO-control triggers, making it unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
first-fluke/oh-my-agent
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.