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.
72
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/devops/infrastructure-as-code-generator/skills/generating-infrastructure-as-code/SKILL.mdQuality
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 identifies its domain (infrastructure as code), lists specific tools and platforms it supports, and provides explicit trigger phrases. The description is concise yet comprehensive, covering both what the skill does and when it should be invoked. Minor note: the opening 'Execute use when' is slightly awkward phrasing but doesn't materially impact clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: Terraform, CloudFormation, Pulumi, ARM templates, CDK, and specifies 'production-ready code' across multiple cloud providers. These are concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (produces production-ready code for Terraform, CloudFormation, Pulumi, ARM templates, CDK) and 'when' (explicit trigger phrases like 'create Terraform config', 'generate CloudFormation template', etc.). Has explicit 'Use when' equivalent via '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', plus mentions ARM templates and CDK. These are terms users would naturally use when requesting infrastructure as code. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on infrastructure as code with specific tool names (Terraform, CloudFormation, Pulumi, ARM, CDK) that are unlikely to conflict with other skills. The domain is clearly delineated. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a broad overview of IaC generation but lacks the concrete, executable examples that would make it truly actionable—no actual Terraform, CloudFormation, or Pulumi code is shown despite this being a code generation skill. The workflow is sequenced but missing critical validation feedback loops for infrastructure operations. The content tries to cover too many tools and providers in a single file without sufficient depth or progressive disclosure into tool-specific guidance.
Suggestions
Add at least one complete, executable code example per major IaC tool (e.g., a minimal Terraform VPC config, a CloudFormation S3 bucket template) to make the skill actionable rather than descriptive.
Add an explicit feedback loop after validation: 'If terraform plan shows unexpected changes, review the diff, fix the configuration, and re-run plan before applying.'
Split tool-specific guidance into separate referenced files (e.g., TERRAFORM.md, CLOUDFORMATION.md, PULUMI.md) and keep SKILL.md as a concise overview with navigation links.
Remove generic prerequisites Claude already knows (like 'Understanding of the desired infrastructure architecture') and replace with specific patterns or anti-patterns to follow when generating IaC.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured but includes unnecessary padding. The 'Prerequisites' section explains things Claude already knows (e.g., 'Understanding of the desired infrastructure architecture'), and the Overview restates the description. The error handling table and resources section add bulk without being directly actionable in context. | 2 / 3 |
Actionability | Despite covering a complex topic, the skill provides zero executable code examples. The instructions are high-level descriptions ('Write resource definitions following cloud provider best practices') rather than concrete, copy-paste-ready configurations. The Examples section lists prompts but no actual output code. For an IaC generation skill, the absence of any Terraform, CloudFormation, or Pulumi code snippets is a critical gap. | 1 / 3 |
Workflow Clarity | The 10-step workflow provides a reasonable sequence, and step 10 mentions validation. However, there's no explicit feedback loop (validate -> fix -> retry), no checkpoint between generating and deploying, and no guidance on what to do if `terraform plan` reveals issues. For infrastructure operations that can be destructive, the missing feedback loops cap this at 2. | 2 / 3 |
Progressive Disclosure | The content is organized into clear sections (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources), which is good structure. However, for a skill covering 5 IaC tools across 3 cloud providers, all content is inline in a single file with no references to separate detailed guides per tool or provider. The Resources section links to external docs but doesn't reference any bundle files for tool-specific guidance. | 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.