terraform-search-import
Discover existing Azure resources and bulk import them into Terraform management. USE FOR: import Azure resources, bring unmanaged infra under Terraform, audit Azure resources, migrate to IaC, terraform import, bulk import. WHEN: import existing resources, discover Azure infrastructure, adopt Terraform for existing resources, generate import blocks. DO NOT USE FOR: Bicep code, new resource creation, architecture decisions.
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 an excellent skill description that clearly defines its niche at the intersection of Azure and Terraform import workflows. It provides comprehensive trigger terms, explicit use-when guidance, and notably includes exclusion criteria that help disambiguate it from related skills. The structured USE FOR / WHEN / DO NOT USE FOR format is effective and easy to parse.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Discover existing Azure resources', 'bulk import them into Terraform management', 'audit Azure resources', 'migrate to IaC', 'generate import blocks'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (discover and bulk import Azure resources into Terraform), 'when' (explicit USE FOR and WHEN clauses with trigger scenarios), and even includes 'DO NOT USE FOR' exclusions which further clarify scope. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'import Azure resources', 'terraform import', 'bulk import', 'bring unmanaged infra under Terraform', 'discover Azure infrastructure', 'adopt Terraform for existing resources', 'generate import blocks'. These are highly natural phrases a user would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: Azure resource discovery and Terraform import specifically. The 'DO NOT USE FOR' clause (Bicep, new resource creation, architecture decisions) explicitly reduces conflict risk with related but different skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently covers Azure resource discovery and Terraform import with good progressive disclosure and a clear decision tree. Its main weaknesses are the lack of an inline import block example (deferring entirely to a reference file for the core action) and missing validation/error recovery guidance for when terraform plan shows unexpected changes during import. The experimental Search workflow section is appropriately flagged but could benefit from a brief concrete example.
Suggestions
Add a concrete inline example of an import block + resource block pair in Step 2 (e.g., for azurerm_resource_group) so the core workflow is executable without consulting the reference file.
Add an explicit validation/error recovery step after 'terraform plan' — e.g., 'If plan shows create/destroy instead of import-only, verify the import ID format and resource type mapping before proceeding.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Terraform or Azure are, assumes Claude knows CLI tools and HCL syntax, and every section serves a clear purpose. The decision tree, mapping table, and MCP tool table are all high-density information formats. | 3 / 3 |
Actionability | The az CLI discovery commands and plan/apply steps are concrete and executable. However, the actual import block creation (Step 2) defers to a reference file rather than showing a complete executable example inline, and the Search workflow section is too vague to act on without the referenced files. | 2 / 3 |
Workflow Clarity | The 3-step manual workflow is clearly sequenced and includes a review checkpoint at 'terraform plan'. However, there's no explicit validation/error recovery loop — e.g., what to do if plan shows unexpected changes or destroy actions, which is critical for import operations that could be destructive if misconfigured. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, decision tree for workflow selection, and well-signaled one-level-deep references to detailed files (references/manual-import.md, scripts/list_resources.sh, and cross-skill references). The reference index table at the bottom provides clean navigation. | 3 / 3 |
Total | 10 / 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
- jonathan-vella/azure-agentic-infraops
- Commit
ec7b8ff
- 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.