iac-common
Shared IaC deploy patterns for Bicep and Terraform deploy agents: deployment strategies, circuit breaker, known deploy issues. For preflight validation (auth, governance, stop rules), see azure-validate. USE FOR: Phased deployment, circuit breaker, deploy-specific known issues. DO NOT USE FOR: Preflight validation (use azure-validate), code generation (use azure-bicep-patterns or terraform-patterns).
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 a strong skill description that clearly defines its scope (deploy patterns for Bicep/Terraform), includes natural trigger terms, and explicitly delineates boundaries with related skills using USE FOR/DO NOT USE FOR clauses. The cross-referencing of adjacent skills (azure-validate, azure-bicep-patterns, terraform-patterns) is particularly effective for disambiguation in a multi-skill environment.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: deployment strategies, circuit breaker patterns, known deploy issues, and phased deployment. Also explicitly names related tools (Bicep, Terraform) and cross-references other skills for boundary clarity. | 3 / 3 |
Completeness | Clearly answers both 'what' (shared IaC deploy patterns for Bicep and Terraform: deployment strategies, circuit breaker, known deploy issues) and 'when' (explicit 'USE FOR' and 'DO NOT USE FOR' clauses with specific triggers and boundary conditions referencing other skills). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'deployment', 'deploy', 'circuit breaker', 'Bicep', 'Terraform', 'phased deployment', 'deploy issues', 'IaC'. These cover common variations a user working with infrastructure deployment would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Excellent distinctiveness with explicit 'DO NOT USE FOR' clauses that delineate boundaries against azure-validate, azure-bicep-patterns, and terraform-patterns. This makes it very unlikely to conflict with related skills in the same ecosystem. | 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 deployment patterns skill with strong actionability and excellent progressive disclosure through its reference index. The main weaknesses are some verbosity around the deprecated deploy.ps1 content (which could be trimmed or moved entirely to a reference) and missing explicit validation/error-recovery steps after deployment operations, which is important for destructive infrastructure changes.
Suggestions
Add explicit post-deployment validation steps after `azd provision` (e.g., check deployment status, verify resource creation, handle common failure modes inline rather than only via circuit breaker reference).
Trim the deprecated deploy.ps1 phased deployment section to 2-3 lines with a pointer to a reference file, since it's deprecated and the detail is unlikely to be needed for new work.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary content like the full deprecated deploy.ps1 phased deployment table and the lengthy azd vs deploy.ps1 comparison table when a reference file already exists for that. The deprecation notice could be shorter. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready bash commands for azd deployment, specific environment variable names to check, clear naming conventions ({project}-{env}), and explicit flags/parameters for both Bicep and Terraform phased deployment. | 3 / 3 |
Workflow Clarity | The azd deployment steps are clearly sequenced and the preflight check for --no-prompt is well-defined. However, there are no explicit validation/feedback loops after `azd provision` — no 'if deployment fails, do X' steps. The circuit breaker section references an external file but doesn't inline the stopping rule workflow, and destructive deployment operations lack explicit verification checkpoints. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview in the main file, a well-organized reference index table pointing to one-level-deep external files, and appropriate use of cross-skill references (azure-validate, terraform-patterns, azure-defaults). Content is appropriately split between inline essentials and external deep-dives. | 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.