Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).
94
92%
Does it follow best practices?
Impact
96%
2.66xAverage 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 key dimensions well. It provides specific capabilities, comprehensive natural trigger terms, explicit use/don't-use guidance, and clear boundaries against related skills. The DO NOT USE FOR section with specific alternative skill references is a particularly strong differentiator for routing accuracy.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: quick preset deployments, fully customized deployments with specific parameters (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. Very detailed about what it does. | 3 / 3 |
Completeness | Clearly answers both 'what' (handles preset deployments, customized deployments, capacity discovery) and 'when' (explicit USE FOR and DO NOT USE FOR clauses with specific trigger scenarios). The DO NOT USE FOR section adds extra clarity for routing. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'deploy model', 'deploy gpt', 'create deployment', 'find capacity', 'check model availability', 'where can I deploy', 'best region for model'. These are natural phrases a user would actually type. | 3 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to Azure OpenAI model deployment with explicit DO NOT USE FOR boundaries that distinguish it from listing deployments, deleting deployments, agent creation, and project creation skills. This significantly reduces conflict risk. | 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 routing skill that effectively serves as a unified entry point for model deployment workflows. Its strengths are clear intent detection logic, concrete validation commands, and excellent progressive disclosure to sub-skills. The main weakness is moderate redundancy between the flowchart and routing rules table, and slightly verbose confirmation UI mockups, though these don't significantly harm usability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy — the routing rules table largely duplicates the intent detection flowchart, and the project selection confirmation step is somewhat verbose with its mock UI. However, most content is genuinely instructive and not explaining things Claude already knows. | 2 / 3 |
Actionability | Provides concrete, executable Azure CLI commands for model catalog and quota validation, specific environment variable names, clear routing logic with exact keyword triggers, and step-by-step confirmation flows. The guidance is specific enough to act on directly. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints (model SKU support check, quota availability check before deployment), a required confirmation step before any deployment, and clear chaining patterns (Capacity → Deploy). Error prevention is well-addressed with the 'never deploy without confirmation' warning. | 3 / 3 |
Progressive Disclosure | Excellent structure as a routing/overview skill that clearly points to three sub-skills (preset, customize, capacity) with a quick reference table, and defers quota management to a separate skill. References are one level deep and well-signaled. The SKILL.md stays at the right level of abstraction for a parent routing document. | 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.
d02fd24
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.