mcpbeat

Azsdk Common Prepare Release Plan

azure/azsdk-common-prepare-release-plan

Create and manage release plan work items for Azure SDK releases across languages. **UTILITY SKILL**. USE FOR: \"create release plan\", \"update 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_link_sdk_pull_request_to_release_plan.

2k tokens
context cost
the whole folder, loaded on every use
5
files
instructions only
0
copies elsewhere
how many repositories repackaged it
122
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/Azure/azure-sdk-for-net --skill azsdk-common-prepare-release-plan

What comes with it

6 831 bytes besides the instruction
evals/eval.yaml
evals/trigger.eval.yaml
fixtures/tspconfig.yaml
references/release-plan-details.md

The instruction itself

5 sections, as written by the author

Prepare Release Plan

> Do not display Azure DevOps work item URLs. Only provide Release Plan Link and ID.

MCP Tools

| Tool | Purpose |

|------|---------|

| azure-sdk-mcp:azsdk_create_release_plan | Create plan |

| azure-sdk-mcp:azsdk_get_release_plan | Get details |

| azure-sdk-mcp:azsdk_get_release_plan_for_spec_pr | Find by spec PR |

| azure-sdk-mcp:azsdk_update_release_plan | Update plan fields |

| azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan | Update SDK info |

| azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan | Link SDK PR |

| azure-sdk-mcp:azsdk_link_namespace_approval_issue | Link namespace |

| azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan | Update spec PR |

Steps

  • Prerequisites — Check for API spec PR link or a TypeSpec project path; prompt if unavailable.
  • Check Existing — Query by release plan number or spec PR link (do not query by work item ID).
  • Gather Info — Collect Service Tree IDs, timeline, and API release type. See details.
  • API Release Type — Ask user for API release type: "Private Preview", "Public Preview", or "GA". This is required.
  • Validate Spec PR — If spec PR is provided, validate it matches the API release type:
  • Private Preview → must be in azure-rest-api-specs-pr
  • Public Preview / GA → must be in azure-rest-api-specs
  • Create — Run azure-sdk-mcp:azsdk_create_release_plan with apiReleaseType parameter. SDK release type defaults automatically (beta for preview, stable for GA).
  • Namespace — For mgmt plane first releases, link approval issue.
  • Link PRs — Link SDK PRs to plan.

Examples

  • "Create a release plan for my spec PR"
  • "Create a release plan for my TypeSpec project"
  • "Create a private preview release plan"
  • "Create a GA release plan for my spec PR"
  • "Link my SDK PR to release plan"

Troubleshooting

  • Requires azure-sdk-mcp server; no CLI fallback.
  • If creation fails, verify Service Tree IDs and the provided spec PR URL or TypeSpec project path.
  • If spec PR validation fails, check that the spec PR repo matches the API release type (private repo for Private Preview, public repo for Public Preview/GA).

How to use it

Copy the folder

Take azure/azsdk-common-prepare-release-plan from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.