Name: azsdk-common-prepare-release-plan
Rating: 67.2 (1 reviews)
Author: Azure

azsdk-common-prepare-release-plan

Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases. **UTILITY SKILL**. USE FOR: "create release plan", "get release plan", "update release plan", "update API spec in release plan", "update SDK details in release plan", "abandon release plan", "link SDK PR to plan", "namespace approval", "check release plan status". DO NOT USE FOR: SDK code generation, pipeline troubleshooting, API review feedback. INVOKES: azure-sdk-mcp:azsdk_create_release_plan, azure-sdk-mcp:azsdk_get_release_plan, azure-sdk-mcp:azsdk_update_release_plan, azure-sdk-mcp:azsdk_update_release_plan_target, azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan, azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan, azure-sdk-mcp:azsdk_abandon_release_plan, azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan, azure-sdk-mcp:azsdk_link_namespace_approval_issue.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

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

A well-structured, highly actionable skill body with concrete tool calls, parameters, and value formats, but it is held back by redundant restatement of the description, missing verification in batch/update workflows, and a broken reference to a non-existent file.

Suggestions

Remove the Triggers section and intro paragraph that restate the frontmatter description, and drop the INVOKES list from frontmatter since the MCP Tools table already covers it.

Add verification steps to the batch link workflow (e.g., confirm each link succeeded before repeating) and to the update workflows to lift workflow_clarity above the batch/destructive cap of 3.

Create references/release-plan-details.md or remove the broken 'See details' link so the signaled reference resolves.

Dimension	Reasoning	Score
Conciseness	The intro paragraph and the entire Triggers section restate the frontmatter description (USE FOR / WHEN / DO NOT USE FOR), and the INVOKES tool list duplicates the MCP Tools table — noticeable tightening opportunity beyond the minor level of the 4 anchor.	3 / 5
Actionability	Gives exact MCP tool names, specific parameters (typeSpecProjectPath, sdkReleaseType, specPullRequestUrl), and concrete value enums ('June 2026', 'Private Preview'/'Public Preview'/'GA', 'beta'/'stable'); as an instruction-only skill the tool-call guidance is the executable unit and is copy-ready.	5 / 5
Workflow Clarity	Numbered steps and clear sequencing are present, but the batch linking workflow (use case 6, 'repeat for each') and several update workflows lack verification checkpoints; per the destructive/batch cap this caps the score at 3 even though the abandon flow does include a confirmation step.	3 / 5
Progressive Disclosure	Sections are well organized (Triggers, Rules, MCP Tools, Use Cases, Examples, Troubleshooting), but the one signaled external reference — 'See [details](references/release-plan-details.md)' at line 58 — points to a file that does not exist (no references/ directory), breaking navigation.	3 / 5
	Total	14 / 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.

An excellent description that follows the recommended pattern precisely: concrete actions, natural USE FOR triggers, a DO NOT USE FOR boundary, and third-person voice. It is comprehensive and clearly distinguishable with no verbosity or fluff.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions ('Create, get, update, abandon, and link SDK PRs to release plan work items') on a specific domain object, matching the comprehensive-coverage anchor rather than the 1-2-action anchor at 3.	5 / 5
Completeness	Explicitly answers both 'what' (the five release-plan operations) and 'when' (USE FOR trigger phrases) plus a DO NOT USE FOR boundary, matching the explicit what-and-when anchor at 5.	5 / 5
Trigger Term Quality	Nine natural user phrases ('create release plan', 'get release plan', 'link SDK PR to plan', 'namespace approval', 'check release plan status') with synonym coverage; these are utterances a user would actually say, fitting the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Clear Azure SDK release-plan niche with explicit DO NOT USE FOR boundary (SDK code generation, pipeline troubleshooting, API review feedback), giving minimal conflict risk per the clear-niche anchor.	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: 1 missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: Azure/azure-sdk-for-net
Path: .github/skills/azsdk-common-prepare-release-plan/SKILL.md
Commit: 3a3a26e

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