Name: azure-ps-design-review
Rating: 71.2 (1 reviews)
Author: Azure

azure-ps-design-review

Conversational agent that guides developers through creating complete Azure PowerShell cmdlet design specifications. Walks through an interactive interview covering service release details, contacts, scenarios, cmdlet syntax, parameter sets, piping, test cases, and spec links. Validates against PowerShell design guidelines, pre-populates fields from TypeSpec, and files the design as a GitHub Issue in Azure/azure-powershell-cmdlet-review-pr. USE FOR: 'create PowerShell design', 'PS design review', 'cmdlet design', 'PowerShell cmdlet review', 'submit PS design'. DO NOT USE FOR: SDK generation, TypeSpec authoring, releasing packages.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%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.

The content is highly actionable with a clear, validated workflow, but it is hampered by verbatim duplication of the MCP setup block and scratch-file warnings, and by referencing bundle files that are absent while inlining a large template that belongs in one of them.

Suggestions

Create the referenced references/design-guidelines-summary.md and references/issue-template.md files (or remove the dangling links) so the signaled navigation actually resolves.

Move the large inlined design-draft template into references/issue-template.md and link to it, keeping only a short usage note in SKILL.md.

De-duplicate the GitHub MCP config JSON block — keep it once in Troubleshooting and reference it from the MCP Tools section instead of repeating it verbatim.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but repeats itself: the GitHub MCP config JSON block appears verbatim in both the MCP Tools section and Troubleshooting, and the 'do not ask for multi-line content in chat' warning is restated several times. Trimming the duplicated config block and consolidating the scratch-file warnings would move it toward a 4.	3 / 5
Actionability	Guidance is fully executable — named MCP tools, exact search queries ('"AzSnapshot" language:cs path:src/Compute'), concrete file paths, a copy-paste-ready draft template, and a specific validation checklist with rules like 'PATCH operations use Update-, PUT operations use Set-'.	5 / 5
Workflow Clarity	A clearly sequenced 6-step workflow with a progress checklist, an explicit validation gate in Step 4, and a feedback loop ('If issues exist, update the scratch file with corrections and re-open' / 'Once all validations pass, proceed') before the irreversible issue-filing step.	5 / 5
Progressive Disclosure	Section structure is present and references are signaled one-level-deep, but the referenced files (references/design-guidelines-summary.md, references/issue-template.md) do not exist in the bundle, so navigation breaks, and the ~140-line draft template is inlined in SKILL.md rather than split into the referenced template file.	3 / 5
	Total	16 / 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.

The description is exemplary: third-person voice, concrete multi-step capabilities, natural trigger phrases with synonyms, and explicit use/don't-use boundaries. It cleanly matches the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'guides developers through creating complete Azure PowerShell cmdlet design specifications', an interview covering 'service release details, contacts, scenarios, cmdlet syntax, parameter sets, piping, test cases', 'Validates against PowerShell design guidelines', 'pre-populates fields from TypeSpec', and 'files the design as a GitHub Issue' — comprehensive coverage matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers both 'what' (interview, validation, pre-population, issue filing) and 'when' (concrete 'USE FOR' triggers plus 'DO NOT USE FOR' boundaries), the strongest anchor.	5 / 5
Trigger Term Quality	The 'USE FOR' clause supplies natural phrases users would say ('create PowerShell design', 'PS design review', 'cmdlet design', 'PowerShell cmdlet review', 'submit PS design') with PS/PowerShell synonyms, matching comprehensive natural-term coverage.	5 / 5
Distinctiveness Conflict Risk	A clear niche (Azure PowerShell cmdlet design review filed to a specific repo) with distinct triggers and an explicit 'DO NOT USE FOR' boundary, giving minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 missing	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: Azure/azure-rest-api-specs
Path: .github/skills/azure-ps-design-review/SKILL.md
Commit: c20bf55

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