azure-quotas
**UTILITY SKILL** — Check and manage Azure quotas and usage across providers for deployment planning, capacity validation, and region selection. WHEN: "check quotas", "service limits", "request quota increase", "quota exceeded", "validate capacity", "regional availability", "vCPU limit". DO NOT USE FOR: deployment execution (azure-deploy), cost analysis (azure-cost-optimization).
75
92%
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 marks. It provides specific capabilities, comprehensive trigger terms that users would naturally use, explicit when/when-not guidance, and clear boundaries against related skills. The 'DO NOT USE FOR' clause is a particularly strong addition for reducing conflict risk in a multi-skill environment.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: check quotas, manage quotas, deployment planning, capacity validation, and region selection. Also specifies the domain (Azure) and the scope (across providers). | 3 / 3 |
Completeness | Clearly answers both 'what' (check and manage Azure quotas and usage for deployment planning, capacity validation, region selection) and 'when' (explicit WHEN clause with trigger terms). Also includes a helpful 'DO NOT USE FOR' clause to reduce misselection. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'check quotas', 'service limits', 'request quota increase', 'quota exceeded', 'validate capacity', 'regional availability', 'vCPU limit'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche (Azure quotas/limits). The explicit 'DO NOT USE FOR' clause naming related skills (azure-deploy, azure-cost-optimization) directly addresses potential conflicts and makes disambiguation easy. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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 communicates Azure quota management with clear workflow sequencing, good progressive disclosure to reference files, and lean content. Its main weakness is that the inline commands use placeholders rather than concrete, executable examples — the actionable detail is deferred to reference files that aren't available for evaluation. The CLI-first mandate and fallback guidance are valuable operational constraints.
Suggestions
Add at least one fully concrete, copy-paste-ready example in the Steps section (e.g., a real scope path like `/subscriptions/{sub-id}/providers/Microsoft.Compute/locations/eastus` and a real resource name like `standardDSv3Family`) to improve actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Azure quotas are in unnecessary depth, uses tables for quick reference, and every section serves a clear purpose. The one-line explanation of quotas at the top is justified since it establishes the mental model (quotas = capacity) that drives the workflow. | 3 / 3 |
Actionability | The skill provides specific CLI commands and a clear step sequence, but the commands shown are incomplete — they use placeholders like `--scope ...` and `--resource-name <name>` without concrete, copy-paste-ready examples with real scope paths or resource names. The detailed workflows are deferred to reference files which are not provided. | 2 / 3 |
Workflow Clarity | The Steps section provides a clear 6-step sequence with an explicit validation checkpoint (step 5: Available = Limit − Usage + Need) and a decision branch (step 6: proceed or request increase/change region). The discovery-first approach (step 2 before step 3) correctly sequences the workflow to avoid the ARM-to-quota name mismatch pitfall. | 3 / 3 |
Progressive Disclosure | The skill is an excellent overview that clearly signals five one-level-deep reference files with a well-organized Reference Index table explaining when to load each. Content is appropriately split between the overview (rules, quick steps) and detailed references (workflows, troubleshooting, mappings). | 3 / 3 |
Total | 11 / 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.