terraform-engineer
Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.
97
100%
Does it follow best practices?
Impact
95%
1.07xAverage score across 6 eval scenarios
Passed
No known issues
Quality
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 scope around Terraform infrastructure as code. It excels at listing specific capabilities, includes natural trigger terms users would actually say, and explicitly states when to invoke the skill. The description is well-structured and distinguishable from other potential infrastructure or cloud-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create reusable modules', 'manage module versioning', 'migrate backends', 'import existing resources', 'resolve state conflicts', 'provider configuration', 'multi-environment workflows', and 'infrastructure testing'. | 3 / 3 |
Completeness | Clearly answers both what (module development, state management, provider configuration, testing) AND when ('Use when implementing infrastructure as code with Terraform', 'Invoke for...'). The 'Use when' and 'Invoke for' clauses provide explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Terraform', 'infrastructure as code', 'AWS', 'Azure', 'GCP', 'module', 'state management', 'backends', 'import', 'provider', 'multi-environment'. These are terms users naturally use when working with Terraform. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around Terraform specifically. The mention of specific cloud providers (AWS, Azure, GCP) combined with Terraform-specific concepts (state management, module versioning, backends) makes it unlikely to conflict with general cloud or IaC skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates strong Terraform expertise in a token-efficient format. The workflow includes proper validation checkpoints with explicit error recovery paths, the code examples are complete and executable, and the progressive disclosure through the reference table is well-organized. The constraints section provides clear guardrails without over-explaining.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic Terraform concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable HCL code examples for module structure, backend configuration, and provider pinning. Commands are specific and copy-paste ready (terraform fmt, validate, plan -out=tfplan). | 3 / 3 |
Workflow Clarity | Clear 6-step workflow with explicit validation checkpoint at step 5 that requires re-running until clean. Error recovery section provides specific feedback loops for validation failures, state drift, auth errors, and dependency issues with clear 'return to step 5' guidance. | 3 / 3 |
Progressive Disclosure | Well-structured overview with a clear reference table pointing to one-level-deep topic files. Content is appropriately split between quick-reference constraints/examples in the main file and detailed guidance in referenced files. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
5b76101
- 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.