CtrlK
BlogDocsLog inGet started
Tessl Logo

generating-infrastructure-as-code

Execute use when generating infrastructure as code configurations. Trigger with phrases like "create Terraform config", "generate CloudFormation template", "write Pulumi code", or "IaC for AWS/GCP/Azure". Produces production-ready code for Terraform, CloudFormation, Pulumi, ARM templates, and CDK across multiple cloud providers.

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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 and token-efficient with concrete commands, but it lacks executable IaC code examples, places validation only at the end, and does not link to the bundled scripts/assets that exist alongside it.

Suggestions

Add at least one minimal, copy-paste-ready code example (e.g., a Terraform provider block with remote backend) or link to the bundled templates in assets/.

Move validation earlier or add an explicit "only proceed when validation passes" checkpoint with a fix-and-revalidate loop in the Instructions, rather than validating only at step 10.

Reference the bundle files from the body (e.g., "See scripts/iac_generate.py" or "See assets/iac_config_schema.json") so detail is split one level deep instead of inlined.

DimensionReasoningScore

Conciseness

Lean, section-organized body with one tight line per instruction and no concept-explanation filler Claude already knows (e.g., no "what is Terraform"); every section earns its place.

3 / 3

Actionability

Gives concrete commands and file names ("terraform validate", "terraform import", "terraform.tfvars", "S3 + DynamoDB") but no copy-paste-ready IaC code blocks, and the Examples section shows input prompts rather than output code.

2 / 3

Workflow Clarity

Ten clearly sequenced steps with a terminal validation step and a separate error-handling table, but validation appears only at the end with no explicit mid-process checkpoints or an integrated fix-and-revalidate loop in the workflow itself.

2 / 3

Progressive Disclosure

The body is well-organized into sections but does not reference or link to the provided bundle files (scripts/iac_generate.py, assets/iac_config_schema.json, references), missing the opportunity to split detail one level deep.

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: it states concrete capabilities, supplies natural trigger phrases, and explicitly covers both what and when in third person. Minor phrasing awkwardness ("Execute use when") does not materially weaken it.

DimensionReasoningScore

Specificity

Lists concrete tools and outputs ("Terraform, CloudFormation, Pulumi, ARM templates, and CDK" producing "production-ready code") rather than vague language; not merely naming a domain.

3 / 3

Completeness

Clearly answers both what ("Produces production-ready code for Terraform, CloudFormation, Pulumi, ARM templates, and CDK") and when ("Trigger with phrases like...") with explicit trigger guidance.

3 / 3

Trigger Term Quality

Explicit natural trigger phrases users would say ("create Terraform config", "generate CloudFormation template", "write Pulumi code", "IaC for AWS/GCP/Azure") with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear IaC-generation niche with distinct tool-specific triggers, unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.