azure-local

Plan, deploy, operate, and troubleshoot Azure Local (formerly Azure Stack HCI): sizing and prerequisites, Arc registration, lifecycle updates, workloads (Azure Local VMs, AKS on Azure Local, images, disks, logical networks), SDN and network security, and failure triage — starting read-only and confirming before risky changes. WHEN: Azure Local, Azure Stack HCI, Arc resource bridge, custom location, Azure Local VM, Arc VM, AKS on Azure Local, AKS hybrid, SDN, Lifecycle Manager, Azure Local update, disconnected site.

Quality

94%

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

88%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-organized, lean operations skill body with a clear workflow, safety gating, and a useful error-handling table. The main weakness is broken workflow file references — five workflows/*.md links have no corresponding bundle files.

Suggestions

Create the five referenced workflow files under workflows/ (plan-and-deploy, operate-and-update, workload-management, networking-and-security, troubleshooting) or remove the dead links, since progressive_disclosure currently penalizes the missing bundle.

Add at least one inline executable example (e.g. a concrete az graph query or PowerShell one-liner) in the MCP Tools section to lift actionability from 4 to 5.

Confirm the resource-types.md and docs-map.md references are actually cited in the body; resource-types.md is listed in references/ but not linked from the body, which weakens navigation.

Dimension	Reasoning	Score
Conciseness	Lean tables and short prose; no padding or explanation of concepts Claude already knows; every line (quick reference, workflow map, error-handling table) earns its place.	5 / 5
Actionability	Concrete pointers to named reference files and a numbered workflow with specific topics, plus real CLI/MCP tool names; falls short of 5 because the body itself gives no executable commands or examples — all execution detail is deferred to referenced files.	4 / 5
Workflow Clarity	Numbered workflow with a step-0 guard for multi-rack handoff, explicit read-only/safety gate ('Start read-only. Ask before updates, deletes...'), and an Error Handling table with feedback loops (ask for scale, ask for version, follow safety-rules on risky change). Validation checkpoints are explicit despite this being an operations skill.	5 / 5
Progressive Disclosure	Clear overview body with well-signaled one-level-deep references to real files in references/; held below 5 because the workflow points to workflows/*.md paths (plan-and-deploy, operate-and-update, workload-management, networking-and-security, troubleshooting) that do not exist in the bundle.	4 / 5
	Total	18 / 20 Passed

Description

100%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, well-structured description: concrete capabilities, explicit WHEN triggers with synonyms and legacy aliases, and a clear niche. Third-person voice is maintained throughout and it is concise despite covering breadth.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the full lifecycle (plan, deploy, operate, troubleshoot; sizing/prerequisites, Arc registration, lifecycle updates, workloads, SDN, failure triage) — comprehensive coverage matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers 'what' (the full plan/deploy/operate/troubleshoot capability list) and 'when' (explicit WHEN: trigger list), matching the score-5 anchor for both what and when with concrete triggers.	5 / 5
Trigger Term Quality	The WHEN clause enumerates natural product names and aliases users actually say (Azure Local, Azure Stack HCI, Arc VM, AKS hybrid, Lifecycle Manager, disconnected site), including synonyms and the legacy name.	5 / 5
Distinctiveness Conflict Risk	Scoped to Azure Local / Azure Stack HCI with distinct product-specific triggers and an explicit boundary (multi-rack handoff), giving a clear niche with minimal overlap risk versus generic Azure skills.	5 / 5
	Total	20 / 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: 5 missing, 5 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: microsoft/GitHub-Copilot-for-Azure
Path: plugins/azure-local-skills/skills/azure-local/SKILL.md
Commit: fcf2f3b

Reviewed: 6 days 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.