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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-infrastructure-as-code68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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.
This is a strong skill description that clearly defines its purpose, provides excellent trigger terms users would naturally use, and distinguishes itself from other skills through specific tool and platform mentions. The description effectively communicates both capabilities and usage triggers. Minor issue: 'Execute use when' appears to be a grammatical error that should read 'Use when'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and outputs: 'Produces production-ready code for Terraform, CloudFormation, Pulumi, ARM templates, and CDK across multiple cloud providers.' Names specific tools and formats. | 3 / 3 |
Completeness | Clearly answers both what ('Produces production-ready code for Terraform, CloudFormation, Pulumi, ARM templates, and CDK') and when ('Execute use when generating infrastructure as code configurations. Trigger with phrases like...'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'create Terraform config', 'generate CloudFormation template', 'write Pulumi code', 'IaC for AWS/GCP/Azure'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific IaC tools (Terraform, CloudFormation, Pulumi, ARM, CDK) and cloud providers. Unlikely to conflict with general coding or document skills due to clear infrastructure focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides useful IaC code examples across multiple platforms but suffers from abstract workflow instructions and missing validation checkpoints critical for infrastructure operations. The content has structural issues (duplicate Overview section) and the instructions describe what to do conceptually rather than providing executable guidance for the generation and deployment process.
Suggestions
Replace the abstract 8-step instructions with concrete commands: show actual terraform init/validate/plan/apply sequence with explicit validation checkpoints before any apply
Add a validation workflow with feedback loop: 'Run terraform validate -> fix errors -> re-validate -> terraform plan -> review plan output -> only then apply'
Remove the duplicate/corrupted Overview section that appears mid-document inside the Terraform code block
Include complete variable files (variables.tf, terraform.tfvars) alongside main.tf to demonstrate the promised 'modular structure'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary padding like the generic 'This skill provides automated assistance' opener and redundant Overview sections. The prerequisites list includes obvious items Claude would know (like 'Understanding of target infrastructure architecture'). However, the code examples are reasonably lean. | 2 / 3 |
Actionability | Provides executable code examples for Terraform, CloudFormation, and Pulumi, but the 8-step instructions are abstract process descriptions rather than concrete commands. Missing actual deployment commands (terraform init/plan/apply) and the examples show only basic VPC creation without the promised 'modular structure' or variable files. | 2 / 3 |
Workflow Clarity | The 8 steps are vague process descriptions without validation checkpoints. For IaC generation involving infrastructure changes, there's no explicit validate-before-apply workflow, no plan review step, and no feedback loop for catching errors before deployment. Error handling is listed separately but not integrated into the workflow. | 1 / 3 |
Progressive Disclosure | References external resources and a docs file, but the skill itself is somewhat monolithic with inline code examples that could be split. The structure is reasonable with clear sections, but there's a corrupted/duplicated Overview section mid-document that breaks organization. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.