Name: azure-ps-design-review
Rating: 75.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

92%

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

85%

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

The skill body is highly actionable with a clear, validated workflow and well-structured one-level references. Its only real weakness is verbosity from duplicated blocks that could be consolidated.

Suggestions

Deduplicate the GitHub MCP setup JSON — define it once in the MCP Tools or Troubleshooting section and reference it elsewhere instead of repeating it three times.

Consolidate the scratch-file guidance into a single, authoritative explanation; the pattern, 'when to use' table, and the 'do not paste multi-line into chat' rule are each restated multiple times.

Consider moving the full ~140-line draft template into references/design-draft-template.md and referencing it, keeping only a short skeleton inline to reduce the SKILL.md footprint.

Dimension	Reasoning	Score
Conciseness	The body is accurate and substantive but verbose: the MCP setup JSON is repeated three times and the scratch-file guidance is restated multiple times, so it could be tightened without losing clarity.	2 / 3
Actionability	It provides copy-paste-ready specifics — exact MCP tool names, search syntax, PR ref paths, a full draft template, issue title/label format, and the telemetry tag — leaving no ambiguity about what to do.	3 / 3
Workflow Clarity	A clear PR-Link-First sequence with a progress checklist, an explicit 'must execute first' step, and a validate → flag → fix → re-validate feedback loop in Step 4.	3 / 3
Progressive Disclosure	Heavy reference material (full guidelines, issue template) is split into one-level-deep, well-signaled reference files, while the central draft template stays appropriately inline.	3 / 3
	Total	11 / 12 Passed

Description

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.

The description is specific, trigger-rich, and complete, with explicit use/skip guidance that minimizes conflict risk. It follows third-person voice and avoids vague fluff throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — an interactive interview covering enumerated topics, validating against design guidelines, pre-populating from TypeSpec, and filing a GitHub Issue — rather than vague language.	3 / 3
Completeness	Explicitly answers both what the skill does (guides, validates, pre-populates, files an issue) and when to use it via a dedicated 'USE FOR' trigger clause.	3 / 3
Trigger Term Quality	The 'USE FOR' clause surfaces natural phrasings a developer would say ('create PowerShell design', 'PS design review', 'cmdlet design', 'submit PS design') with good variation coverage.	3 / 3
Distinctiveness Conflict Risk	The narrow Azure PowerShell cmdlet-design niche, named target repo, and explicit 'DO NOT USE FOR' negative guidance make it clearly distinguishable and unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

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

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.