azure-quotas
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: "check quotas", "service limits", "current usage", "request quota increase", "quota exceeded", "validate capacity", "regional availability", "provisioning limits", "vCPU limit", "how many vCPUs available in my subscription".
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/azure-quotas/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 strong skill description with excellent trigger term coverage and clear completeness, explicitly answering both what the skill does and when to use it. The specificity of capabilities could be slightly improved by listing more concrete actions rather than high-level categories like 'deployment planning' and 'capacity validation'. Overall, it would perform well in a multi-skill selection scenario.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Azure quotas and usage) and some actions (check, manage, deployment planning, capacity validation, region selection), but the actions are somewhat high-level and not as concrete as listing specific operations like 'query vCPU limits, request quota increases, compare regional availability'. | 2 / 3 |
Completeness | Clearly answers both 'what' (check/manage Azure quotas and usage across providers, deployment planning, capacity validation, region selection) and 'when' with an explicit WHEN clause listing multiple trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'check quotas', 'service limits', 'current usage', 'request quota increase', 'quota exceeded', 'validate capacity', 'regional availability', 'vCPU limit', and even a full natural-language query 'how many vCPUs available in my subscription'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around Azure quotas, service limits, and capacity management. The specific trigger terms like 'quota exceeded', 'vCPU limit', and 'subscription' make it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
54%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has excellent structure and progressive disclosure, with clear workflow sequencing and well-organized reference files. However, it is severely undermined by extreme verbosity and repetition—the same warnings about CLI-first and REST API unreliability appear 3-4 times, and the overview explains basic concepts Claude already knows. The main file also lacks inline executable code examples, deferring all concrete scripts to reference files.
Suggestions
Eliminate redundant repetitions: consolidate the CLI-first warning, REST API 'No Limit' caveat, and ARM-to-quota mapping warning to single mentions each instead of 3-4 times across sections.
Remove the 'Overview' section explaining what Azure quotas are and the 'When to Use This Skill' section—Claude already knows these concepts and the frontmatter already captures trigger phrases.
Include at least one complete, copy-paste-ready bash example inline (e.g., checking vCPU quota for a specific region) rather than deferring all executable code to reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. The 'ALWAYS USE CLI FIRST' message is repeated at least 4 times across different sections (Quick Reference, critical warning box, Gotchas, Best Practices). The Overview explains what quotas are—something Claude already knows. The 'When to Use This Skill' section restates the frontmatter triggers. The warning about REST API 'No Limit' is explained 3 separate times. | 1 / 3 |
Actionability | The skill provides specific CLI commands (az quota list, az quota show, az quota usage show) and references executable scripts in external files, but the main SKILL.md itself contains no complete executable code examples—actual bash scripts are deferred to references/core-workflows.md. The workflow summary diagram is helpful but not copy-paste executable. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with a visual flowchart showing the 5-step process from extension installation through capacity validation, including a decision branch for sufficient vs insufficient capacity. The mandatory CLI-first workflow includes explicit fallback steps (CLI → BadRequest → docs). Validation checkpoints are present (validate capacity = Limit - Usage + Need). | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear Reference Index table at the bottom specifying when to load each reference file. Core workflows, troubleshooting, resource name mapping, and commands are all properly split into separate reference files with clear one-level-deep navigation. The instruction 'Load these on demand — do NOT read all at once' is well-placed. | 3 / 3 |
Total | 9 / 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.