Scaffold Terraform 1.9+ infrastructure with provider configuration (AWS/GCP/Azure), modular structure, remote state, variables, outputs, workspaces, and common resource patterns.
79
Quality
73%
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 ./infrastructure/terraform-starter/SKILL.mdQuality
Discovery
67%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 description with excellent specificity and clear domain focus on Terraform infrastructure scaffolding. The main weakness is the absence of explicit 'Use when...' guidance, which would help Claude know exactly when to select this skill. The trigger terms are good but could include more user-friendly variations.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to create Terraform projects, set up infrastructure as code, or scaffold cloud resources with Terraform'
Include common user-facing trigger terms like 'IaC', 'infrastructure as code', '.tf files', or 'terraform project setup'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'provider configuration (AWS/GCP/Azure), modular structure, remote state, variables, outputs, workspaces, and common resource patterns' - these are all concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with detailed capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through the capability list. | 2 / 3 |
Trigger Term Quality | Includes good technical terms like 'Terraform', 'AWS/GCP/Azure', 'remote state', 'workspaces' that users would say, but missing common variations like 'IaC', 'infrastructure as code', 'tf files', '.tf', or 'terraform init/plan/apply'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche with 'Terraform 1.9+' version specification and cloud provider enumeration. Unlikely to conflict with other infrastructure or cloud skills due to explicit Terraform focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, actionable Terraform skill with excellent executable examples and efficient token usage. The main weaknesses are the lack of explicit validation checkpoints in the workflow (e.g., reviewing plan output before apply, handling state conflicts) and the monolithic structure that could benefit from splitting detailed module examples into separate files.
Suggestions
Add explicit validation workflow: 'Review plan output for unexpected changes before apply' and 'If plan shows drift, investigate before proceeding'
Include error recovery guidance: what to do when apply fails mid-way, how to handle state lock issues, and when to use -target
Consider splitting detailed module examples (networking, database, storage) into separate reference files to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing executable code without explaining basic Terraform concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Fully executable HCL code throughout, copy-paste ready scaffold commands, and specific terraform CLI commands. All examples are complete and production-ready, not pseudocode. | 3 / 3 |
Workflow Clarity | Commands are listed clearly but lack explicit validation checkpoints. The 'Common Commands' section shows the workflow but doesn't emphasize validating plan output before apply or checking for drift. Missing feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but this is a monolithic file with ~300 lines of inline code. Module examples could be split into separate reference files. The Integration Notes hint at other skills but don't provide clear navigation structure. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
181fcbc
Table of Contents
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.