iac-common
**UTILITY SKILL** — Shared IaC deploy patterns for Bicep + Terraform agents: deployment strategies, circuit breaker, known deploy issues. WHEN: "phased deployment", "circuit breaker", "deploy strategy", "deploy issue", "shared IaC pattern". DO NOT USE FOR: preflight (azure-validate), code generation (azure-bicep-patterns / terraform-patterns).
67
80%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/iac-common/SKILL.mdQuality
Discovery
89%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 well-structured skill description that excels at completeness and distinctiveness, particularly through its explicit WHEN triggers and DO NOT USE FOR boundaries. The main weakness is that the capabilities are described more as topic areas than concrete actions—it would benefit from specifying what the skill actually does with these patterns (e.g., recommends, applies, diagnoses). Overall it's a strong description that would perform well in a multi-skill selection scenario.
Suggestions
Replace topic-area nouns with concrete action verbs, e.g., 'Recommends deployment strategies, implements circuit breaker patterns, diagnoses known deploy issues' instead of just listing the topics.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (IaC deployment for Bicep + Terraform) and lists some actions (deployment strategies, circuit breaker, known deploy issues), but these are more like topic areas than concrete actions. It doesn't specify what it actually does with these (e.g., 'recommends strategies', 'diagnoses issues', 'applies patterns'). | 2 / 3 |
Completeness | Clearly answers both 'what' (shared IaC deploy patterns for Bicep + Terraform: deployment strategies, circuit breaker, known deploy issues) and 'when' (explicit WHEN clause with trigger terms). Also includes a helpful 'DO NOT USE FOR' clause that further clarifies boundaries. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'phased deployment', 'circuit breaker', 'deploy strategy', 'deploy issue', 'shared IaC pattern'. These are realistic phrases a user working with infrastructure deployments would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary-setting via the 'DO NOT USE FOR' clause that names specific sibling skills (azure-validate, azure-bicep-patterns, terraform-patterns). The trigger terms are specific to deployment patterns rather than code generation or validation, making conflicts unlikely. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%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 utility skill that serves effectively as a routing and orchestration document for IaC deployment workflows. Its strongest aspects are the clear 7-step workflow with explicit validation gates and the comprehensive reference index for progressive disclosure. Its main weakness is that actionable, executable content is almost entirely deferred to reference files, and the reference table includes several entries that seem out of scope for a deployment-focused skill (codegen references).
Suggestions
Add a minimal executable code block for the most common deploy path (e.g., a complete azd provision sequence with environment setup commands) so the skill is actionable without requiring reference file lookups.
Trim the Reference Index to entries directly relevant to deployment; codegen-related references (codegen-shared-workflow, codegen-file-order, codegen-do-dont) seem out of scope per the skill's own 'Out of scope' rule.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and avoids explaining basic concepts, but the large reference index table includes many entries that seem tangential to the skill's stated purpose (e.g., codegen file-order, codegen DO/DON'T, AVM module index). Some redundancy exists between the Rules section and the Steps section (e.g., circuit breaker mentioned in both). The skill could be tightened. | 2 / 3 |
Actionability | The Steps section provides a clear sequence with specific commands (azd env set, azd provision --preview, terraform plan), but most detailed procedures are deferred to reference files. The skill itself lacks executable code blocks or copy-paste-ready command sequences — it's more of a routing document than an actionable guide. | 2 / 3 |
Workflow Clarity | The 7-step deploy flow is clearly sequenced with explicit validation checkpoints: preflight before deploy, preview before apply, explicit user approval gate, circuit-break on failure, and handoff. The feedback loop (circuit-break → surface diagnostics → user decision) is well-defined for destructive/risky operations. | 3 / 3 |
Progressive Disclosure | The skill is structured as a clear overview with well-signaled one-level-deep references. The Reference Index table provides a comprehensive navigation map to detailed materials. Key details are appropriately deferred to reference files (deployment-strategies.md, circuit-breaker.md, azd-vs-deploy-guide.md) while the main body stays concise. | 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
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.