mcpbeat Sign in

Azsdk Common Prepare Release Plan Agent Skill

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).

Other skills for the same job

different authors, same section of the catalogue
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens
Commit Work
by softaworks
×2

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens
Verification & Quality Assurance
by Microck
×2

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

4k tokens
Gh CLI
by christophacham
×2

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

10k tokens
Github
by Dicklesworthstone
×2

GitHub CLI - manage repositories, issues, pull requests, actions, releases, and more from the command line.

1k tokens
Codebase Cleanup Refactor Clean
by ComeOnOliver
×2

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

9k tokens
Codebase Cleanup Tech Debt
by ComeOnOliver
×2

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

6k tokens

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.