preset

Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured, actionable content with concrete commands and a clear phased workflow supported by a real reference file. The main weaknesses are triple-restatement of the phase list and an unlinked second workflow reference file.

Suggestions

Consolidate the 'What This Skill Does', 'Quick Workflow', and 'Deployment Phases' sections into a single phase listing to remove triple-restatement of the same 7 steps.

Either link references/preset-workflow.md from the body or remove it if superseded by workflow.md, so all bundle files are clearly signaled and navigable.

Add an explicit 'validate capacity before deploying' checkpoint in the main flow rather than relying on the error-handling table and monitoring step alone.

Dimension	Reasoning	Score
Conciseness	The body is efficient and free of basic-concept padding, but the same 7-phase deployment is restated three times (What This Skill Does, Quick Workflow, and the Deployment Phases table), which is minor redundancy that could be tightened.	4 / 5
Actionability	Concrete az CLI commands appear in the phases table and Advanced Usage section, and full copy-paste bash is available in references/workflow.md; a few table commands are abbreviated (e.g. 'az rest --method GET .../modelCapacities'), leaving minor gaps.	4 / 5
Workflow Clarity	A clear 7-phase sequence with two path variants (fast path vs. alternative region) and a terminal monitor step; validation is present via the error-handling table and deployment monitoring, though explicit pre-deploy validation checkpoints in the main flow are somewhat implicit.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview with a well-signaled one-level-deep link to references/workflow.md (a real file); however a second bundle file references/preset-workflow.md is not referenced or signaled from the body, a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description with explicit trigger guidance and clear negative boundaries that distinguish it from sibling skills. Trigger terms are good but slightly repetitive rather than offering distinct synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'deploys Azure OpenAI models to optimal regions', 'analyzing capacity across all available regions', 'checks current region first and shows alternatives' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (deploys to optimal regions by analyzing capacity) and 'when' (a USE FOR clause with concrete triggers), and adds DO NOT USE FOR boundaries, matching the top anchor.	5 / 5
Trigger Term Quality	The USE FOR list provides many natural phrases ('quick deployment', 'best region', 'fast setup', 'deploy to best location'), but several are repetitive variations on 'region' rather than distinct synonyms or file-extension-style terms, leaving a few natural variations missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Azure OpenAI optimal-region deployment) with explicit DO NOT USE FOR boundaries routing custom SKU/version/capacity/PTU cases to the 'customize' skill, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: microsoft/azure-skills
Path: .github/plugins/azure-skills/skills/microsoft-foundry/models/deploy-model/preset/SKILL.md
Commit: 16dc8c5

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.