tessl install github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-infrastructure-as-codeExecute 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.
Review Score
68%
Validation Score
13/16
Implementation Score
38%
Activation Score
100%
Generated
Validation
Total
13/16Score
Passed| Criteria | Score |
|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) |
metadata_version | 'metadata' field is not a dictionary |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata |
Implementation
Suggestions 4
Score
38%Overall Assessment
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
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | 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. |
Actionability | 2/3 | 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. |
Workflow Clarity | 1/3 | 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. |
Progressive Disclosure | 2/3 | 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. |
Activation
Score
100%Overall Assessment
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 | Score | Reasoning |
|---|---|---|
Specificity | 3/3 | 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. |
Completeness | 3/3 | 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...'). |
Trigger Term Quality | 3/3 | 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. |
Distinctiveness Conflict Risk | 3/3 | 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. |