terraform-search-import
**WORKFLOW SKILL** — Discover existing Azure resources and bulk import them into Terraform management. WHEN: "terraform import", "import Azure resources", "bring unmanaged infra under Terraform", "adopt Terraform for existing resources", "generate import blocks". DO NOT USE FOR: Bicep code (azure-bicep-patterns), new resource creation (terraform-patterns), architecture decisions (azure-adr).
72
88%
Does it follow best practices?
Impact
—
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 hits all the key criteria. It uses third person voice, provides specific actions, includes rich natural trigger terms, explicitly addresses both what and when, and proactively disambiguates from related skills with a 'DO NOT USE FOR' clause. The structured format (WORKFLOW SKILL, WHEN, DO NOT USE FOR) makes it highly scannable and effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Discover existing Azure resources' and 'bulk import them into Terraform management'. Also specifies what it does NOT do, which adds clarity about its scope. | 3 / 3 |
Completeness | Clearly answers both 'what' (discover existing Azure resources and bulk import into Terraform) and 'when' (explicit WHEN clause with multiple trigger phrases). Also includes a 'DO NOT USE FOR' section with references to alternative skills, which is excellent for routing. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'terraform import', 'import Azure resources', 'bring unmanaged infra under Terraform', 'adopt Terraform for existing resources', 'generate import blocks'. These are realistic phrases a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (importing existing Azure resources into Terraform). The explicit 'DO NOT USE FOR' section with named alternative skills (azure-bicep-patterns, terraform-patterns, azure-adr) directly addresses potential conflicts and makes disambiguation easy. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%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 workflow skill with excellent conciseness and clear decision routing between primary and experimental paths. Its main weakness is that the core actionable content (executable import block examples, az CLI commands with full syntax, bulk import scripts) is deferred to reference files that aren't provided in the bundle, making the SKILL.md itself more of a navigation document than a self-contained guide. The validation checkpoint (plan shows imports only) is a strong safety measure.
Suggestions
Include at least one complete, executable example in the SKILL.md body showing the full flow: az resource list command → generated import block → resource block → terraform plan output, rather than deferring all concrete examples to references/manual-import.md
Provide the bundle files (especially references/manual-import.md) or inline the most critical content—the Azure-type ↔ Terraform-resource mapping table for the top 3-4 services—so the skill is actionable without requiring reference file access
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Terraform, Azure, or import blocks are. Every section serves a purpose—decision tree, rules, workflow steps, tool table—without padding or redundant explanation. | 3 / 3 |
Actionability | The skill provides a clear workflow structure and references specific CLI commands (az resource list, terraform plan, terraform apply), but the actual executable examples, bulk import scripts, and resource mapping tables are deferred to references/manual-import.md. The main SKILL.md itself lacks copy-paste-ready code blocks for the core import workflow. | 2 / 3 |
Workflow Clarity | The three-step manual discovery workflow is clearly sequenced with an explicit validation checkpoint (terraform plan must show imports only—no creates/destroys before apply). The decision tree clearly routes between primary and experimental paths with explicit precondition checks. The feedback loop is implicit but the validation gate is explicit. | 3 / 3 |
Progressive Disclosure | The skill references manual-import.md and scripts/list_resources.sh appropriately, and the reference index table is well-organized. However, no bundle files were provided to verify these references exist, and the experimental search workflow section is thin—it could either be fleshed out or more clearly deferred to a reference file. The cross-skill reference to terraform-patterns refactor-module.md adds a second level of indirection. | 2 / 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
05d7617
- 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.