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.

71

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 body is a well-structured, operational skill with clear workflows, validation checkpoints, concrete commands, and explicit guardrails. Its main weaknesses are a duplicated references list, the absence of an end-to-end runnable example, and bundle references that point to non-existent files.

Suggestions

De-duplicate the References section: keep a single clearly labeled list of resource paths instead of repeating them in prose and bullets.

Add one complete, copy-paste-ready end-to-end example (e.g. a minimal provider block + resource + plan/apply sequence) to lift actionability.

Ensure referenced bundle files (resources/*.md, ../_shared/core/*.md) exist, or mark which are injected at runtime by 'oma agent spawn' so the references are not dangling.

DimensionReasoningScore

Conciseness

Efficient and largely free of explaining concepts Claude already knows, but the References section duplicates the same paths in prose and bullet form, and the dense multi-cloud mapping table is reference material that could partly live in a bundle file.

4 / 5

Actionability

Provides concrete executable commands (terraform init/fmt/validate/plan, checkov, trivy) and specific rules ('for_each over count', 'ephemeral resources TF >= 1.10'), but lacks a single end-to-end runnable example covering a common case.

4 / 5

Workflow Clarity

Clear sequenced flow (Entry -> PREPARE/ACQUIRE/REASON/ACT/VERIFY/FINALIZE) with explicit validation in the VERIFY scene, stop-on-destructive transitions, and a failure/recovery feedback loop, satisfying the destructive-skill validation requirement.

5 / 5

Progressive Disclosure

Good structure with clearly signaled one-level-deep references (execution-protocol.md, examples.md, etc.), but the referenced resources/ and ../_shared/ files do not exist in the bundle and the reference list is duplicated, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

92%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 strong: it states a concrete niche, enumerates many specific capabilities, and provides an explicit 'Use for' trigger clause with natural terms. It only loses points on trigger term quality for omitting common synonyms and file extensions like .tf, HCL, and IaC.

Suggestions

Add common synonyms and file extensions to the trigger terms, e.g. '.tf', 'HCL', 'IaC', 'Terraform state', so natural phrasings users say are covered.

DimensionReasoningScore

Specificity

Lists multiple concrete actions including 'terraform plan/apply, state management, compute, databases, storage, networking, IAM, OIDC, cost optimization, policy-as-code', giving comprehensive coverage rather than 1-2 actions.

5 / 5

Completeness

Explicitly answers both 'what' (infrastructure-as-code specialist for multi-cloud provisioning) and 'when' ('Use for terraform plan/apply...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms (Terraform, plan/apply, AWS/GCP/Azure/Oracle, IAM, OIDC), but missing common synonyms and file extensions like '.tf', 'HCL', or 'IaC' that users might say.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Terraform-based multi-cloud IaC) with distinct triggers; minimal overlap risk with unrelated skills.

5 / 5

Total

19

/

20

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.