Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).
88
85%
Does it follow best practices?
Impact
89%
4.45xAverage score across 3 eval scenarios
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 covers all dimensions thoroughly. It provides specific concrete actions, comprehensive trigger terms, explicit use/don't-use guidance, and clear differentiation from related skills. The DO NOT USE FOR clause is a particularly strong addition for disambiguation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: step-by-step selection of model version, SKU types (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). Very detailed and concrete. | 3 / 3 |
Completeness | Clearly answers both 'what' (interactive guided deployment flow for Azure OpenAI models with full customization control) and 'when' (explicit USE FOR and DO NOT USE FOR clauses with specific trigger scenarios). The DO NOT USE FOR clause adds extra clarity for disambiguation. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'custom deployment', 'choose version', 'select SKU', 'set capacity', 'configure content filter', 'RAI policy', 'advanced deployment', 'PTU deployment', 'provisioned throughput'. These are terms users would naturally use when requesting these actions. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (custom/advanced Azure OpenAI deployment) and explicitly distinguishes itself from a 'quick deployment to optimal region' skill via the DO NOT USE FOR clause, minimizing conflict risk. | 3 / 3 |
Total | 12 / 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 skill with excellent workflow clarity and progressive disclosure — the 14-phase flow is clearly sequenced with validation checkpoints, and detailed implementation is properly delegated to reference files. However, the main file is somewhat verbose with redundant sections (comparison tables, emoji-laden checklists) and lacks directly executable commands for the core deployment flow, relying entirely on the reference file for actionable implementation.
Suggestions
Trim the 'When to Use This Skill' checklist and comparison table — Claude can infer when to use customize vs preset from the description alone; a single sentence suffices.
Include at least the core deployment CLI command (`az cognitiveservices account deployment create` with key parameters) directly in the SKILL.md so the main file has one executable example without requiring the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes useful tables and structured information but is verbose in places — the 'When to Use This Skill' section with checkmarks, the comparison table between customize vs preset, and the Quick Reference table all add bulk that Claude doesn't need. The phase summaries table is reasonably efficient but the overall document could be significantly tightened. | 2 / 3 |
Actionability | The skill provides some concrete CLI commands in troubleshooting and references specific Azure CLI commands in the phase table, but the actual deployment workflow delegates all executable details to references/customize-workflow.md. The SKILL.md itself contains no complete executable workflow — it describes what to do rather than providing copy-paste ready commands for the core flow. | 2 / 3 |
Workflow Clarity | The 14-phase workflow is clearly sequenced with explicit validation checkpoints (Phase 7 validates capacity min/max/step, Phase 12 requires user review/approval before proceeding, capacity query failure blocks deployment). The cross-region fallback logic and error handling table provide clear feedback loops and error recovery paths. | 3 / 3 |
Progressive Disclosure | The SKILL.md serves as a clear overview with well-signaled one-level-deep references: customize-workflow.md for full scripts/implementation and customize-guides.md for SKU comparison tables and advanced topics. The content is appropriately split between summary in the main file and details in references. | 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.
771a666
Table of Contents
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.