jbvc/terraform-specialist
Expert Terraform/OpenTofu specialist mastering advanced IaC automation, state management, and enterprise infrastructure patterns. Handles complex module design, multi-cloud deployments, GitOps workflows, policy as code, and CI/CD integration. Covers migration strategies, security best practices, and modern IaC ecosystems. Use PROACTIVELY for advanced IaC, state management, or infrastructure automation.
39
39%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description covers a broad domain with relevant technology names but relies heavily on buzzwords and category labels rather than concrete actions. The 'Use PROACTIVELY' trigger clause is present but too vague to effectively guide skill selection. The description would benefit from listing specific actionable capabilities and more natural trigger terms users would actually type.
Suggestions
Replace abstract category labels with concrete actions, e.g., 'Generates Terraform modules, manages state files, writes HCL configurations, plans and debugs infrastructure deployments' instead of 'mastering advanced IaC automation'.
Expand the 'Use when...' clause with specific trigger scenarios, e.g., 'Use when the user asks about writing .tf files, running terraform plan/apply, managing tfstate, migrating from CloudFormation, or designing Terraform modules'.
Add common natural language variations users would say: 'HCL', '.tf files', 'terraform plan', 'terraform apply', 'tfstate', 'infrastructure provisioning', 'cloud resource management'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Terraform/OpenTofu, IaC) and lists several areas like 'state management', 'module design', 'multi-cloud deployments', 'GitOps workflows', 'policy as code', and 'CI/CD integration', but these read more like topic categories than concrete actions. Phrases like 'mastering advanced IaC automation' and 'enterprise infrastructure patterns' are buzzwordy rather than describing specific operations (e.g., 'generate Terraform modules', 'import existing resources into state'). | 2 / 3 |
Completeness | The 'what' is partially covered through topic areas, and there is a 'when' clause ('Use PROACTIVELY for advanced IaC, state management, or infrastructure automation'), but the 'when' is vague and doesn't provide explicit trigger scenarios. The trigger guidance is too broad ('advanced IaC') to be truly useful for skill selection. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Terraform', 'OpenTofu', 'IaC', 'state management', 'multi-cloud', 'GitOps', 'CI/CD', and 'policy as code', which are terms users might use. However, it misses common natural variations like '.tf files', 'terraform plan', 'terraform apply', 'HCL', 'infrastructure provisioning', 'cloud resources', or provider-specific terms that users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of Terraform/OpenTofu specifically helps distinguish it from generic cloud or DevOps skills, but the broad scope covering CI/CD, GitOps, security, and multi-cloud could overlap with dedicated skills for those areas. Terms like 'CI/CD integration' and 'security best practices' are generic enough to conflict with other skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a capability resume or persona description rather than actionable instructions. It exhaustively lists topics Claude already knows about Terraform without providing any concrete code, commands, configuration examples, or specific workflows. The content is almost entirely descriptive taxonomy with no executable guidance, making it ineffective as a skill file.
Suggestions
Replace the extensive 'Capabilities' taxonomy with 2-3 concrete, executable code examples showing key patterns (e.g., a module skeleton, a remote backend configuration, a CI/CD pipeline snippet).
Rewrite the 'Instructions' section as a concrete multi-step workflow with specific commands (terraform init, plan, apply) and explicit validation checkpoints (e.g., 'Run terraform plan and review output before proceeding').
Remove 'Behavioral Traits', 'Knowledge Base', 'Purpose', and 'Example Interactions' sections entirely — these describe what Claude already knows and waste tokens.
Split advanced topics (state management, CI/CD integration, multi-cloud patterns) into separate referenced files and keep SKILL.md as a concise overview with clear links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive lists of concepts Claude already knows (e.g., 'Resources, data sources, variables, outputs, locals, expressions'). The 'Capabilities' section is essentially a taxonomy of Terraform knowledge that adds no actionable value. 'Behavioral Traits' and 'Knowledge Base' sections describe general good practices Claude already understands. The content could be reduced by 80%+ without losing useful information. | 1 / 3 |
Actionability | Contains zero executable code, no concrete commands, no specific configuration examples, and no copy-paste ready snippets. Everything is described at an abstract level (e.g., 'Configure secure backends with appropriate locking and encryption') without showing how. The 'Instructions' section has only four vague steps with no specifics. | 1 / 3 |
Workflow Clarity | The four-step 'Instructions' workflow is extremely vague ('Define environments, providers, and security constraints') with no validation checkpoints, no error recovery loops, and no concrete sequencing. For a skill involving destructive operations like terraform apply and state manipulation, the absence of explicit validation steps and feedback loops is a critical gap. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline in one massive document with 10+ capability subsections that could be split into focused reference files. No navigation aids or links to deeper documentation. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents