Azsdk Common Prepare Release Plan
Azure/azure-sdk-tools
Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases.
Create and manage release plan work items for Azure SDK releases across languages.
Install Azsdk Common Prepare Release Plan
$ npx skills add Azure/azure-sdk-for-android --skill azsdk-common-prepare-release-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-prepare-release-plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Azure/azure-sdk-for-android.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/azsdk-common-prepare-release-plan .claude/skills/azsdk-common-prepare-release-plan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "azsdk-common-prepare-release-plan" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-prepare-release-plan into .claude/skills/azsdk-common-prepare-release-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-prepare-release-plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-prepare-release-planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Azure/azure-sdk-for-android --skill azsdk-common-prepare-release-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-prepare-release-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-for-android.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/azsdk-common-prepare-release-plan .agents/skills/azsdk-common-prepare-release-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "azsdk-common-prepare-release-plan" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-prepare-release-plan into .agents/skills/azsdk-common-prepare-release-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-prepare-release-plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/azure-sdk-for-android --skill azsdk-common-prepare-release-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-prepare-release-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-for-android.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/azsdk-common-prepare-release-plan .cursor/skills/azsdk-common-prepare-release-plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "azsdk-common-prepare-release-plan" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-prepare-release-plan into .cursor/skills/azsdk-common-prepare-release-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-prepare-release-plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Azure/azure-sdk-for-android.git --path .github/skills/azsdk-common-prepare-release-plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Azure/azure-sdk-for-android --skill azsdk-common-prepare-release-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-prepare-release-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-for-android.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/azsdk-common-prepare-release-plan .gemini/skills/azsdk-common-prepare-release-plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "azsdk-common-prepare-release-plan" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-prepare-release-plan into .gemini/skills/azsdk-common-prepare-release-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-prepare-release-plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-prepare-release-planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Azure/azure-sdk-for-android --skill azsdk-common-prepare-release-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-for-android.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/azsdk-common-prepare-release-plan .github/skills/azsdk-common-prepare-release-plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "azsdk-common-prepare-release-plan" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-prepare-release-plan into .github/skills/azsdk-common-prepare-release-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-prepare-release-plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/azure-sdk-for-android --skill azsdk-common-prepare-release-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-prepare-release-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-for-android.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/azsdk-common-prepare-release-plan .opencode/skills/azsdk-common-prepare-release-plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "azsdk-common-prepare-release-plan" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-prepare-release-plan into .opencode/skills/azsdk-common-prepare-release-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-prepare-release-plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
azsdk-common-prepare-release-plan- GitHub stars
- 121
- Token cost
- ~733 tokens
- SKILL.md length
- 275 words
- Files
- 5 (incl. references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create and manage release plan work items for Azure SDK releases across languages.
- Works in 8 steps: Prerequisites — Check for API spec PR… → Check Existing — Query by release plan… → Gather Info — Collect Service Tree IDs,… → …
- : create release plan
- SKILL.md covers MCP Tools, Steps, Examples and Troubleshooting
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Azsdk Common Prepare Release Plan is an agent skill from Azure/azure-sdk-for-android, published by the product's own GitHub organization. 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:azsdkcreatereleaseplan, azure-sdk-mcp:azsdkgetreleaseplan, azure-sdk-mcp:azsdklinksdkpullrequesttoreleaseplan.
Its SKILL.md is about 730 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `evals/eval.yaml`, `evals/trigger.eval.yaml` and `fixtures/tspconfig.yaml`). Compatibility notes: azure-sdk-mcp server, API spec PR, or TypeSpec project path
It sits in Product & Project Management, covering Feature launches and release readiness. It works with Microsoft Azure, Model Context Protocol and Azure DevOps. The repository describes itself as: Android client SDKs for Microsoft Azure. The licence is MIT.
When your agent uses it
- : create release plan
- Update release plan
- Link SDK PR to plan
- Namespace approval
Example prompts
- “create release plan”
- “update release plan”
- “link SDK PR to plan”
- “/azsdk-common-prepare-release-plan”
Requirements
- Compatibility (from SKILL.md): azure-sdk-mcp server, API spec PR, or TypeSpec project path
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- 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
- Create — Run azure-sdk-mcp:azsdk_create_release_plan with apiReleaseType parameter. SDK release type defaults automatically (beta for…
- Namespace — For mgmt plane first releases, link approval issue.
- Link PRs — Link SDK PRs to plan.
What it can do on your machine
Read from SKILL.md and the folder at commit 0ff8a7b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
azure-sdk-mcp server, API spec PR, or TypeSpec project path
From compatibility in the SKILL.md frontmatter.
Context cost
Azsdk Common Prepare Release Plan loads about 733 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 275 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Azure/azure-sdk-for-android at commit 0ff8a7b, republished under its MIT licence (© Azure). 275 words, ~733 tokens.
Download SKILL.mdSave it as
.claude/skills/azsdk-common-prepare-release-plan/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- azsdk-common-prepare-release-plan
- description
- 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.
- compatibility
- azure-sdk-mcp server, API spec PR, or TypeSpec project path
- license
- MIT
- metadata.version
- 1.0.0
- metadata.distribution
- shared
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
- Private Preview → must be in
- Create — Run
azure-sdk-mcp:azsdk_create_release_planwithapiReleaseTypeparameter. 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-mcpserver; 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).
© Azure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in .github/skills/azsdk-common-prepare-release-plan of Azure/azure-sdk-for-android.
- SKILL.md
- evals/eval.yaml
- evals/trigger.eval.yaml
- fixtures/tspconfig.yaml
- references/release-plan-details.md
Open the folder on GitHubat commit 0ff8a7b
Compare with similar skills
Azsdk Common Prepare Release Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Azsdk Common Prepare Release Plan this skillAzure/azure-sdk-for-android | 121 | — | ~733 | Automated safety check: Pass | MIT | |
| Azsdk Common Prepare Release PlanAzure/azure-sdk-tools | 134 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Repo Genomeruvnet/metaharness | 696 | — | ~772 | Automated safety check: Pass | MIT | |
| Verify Witnessruvnet/metaharness | 696 | — | ~472 | Automated safety check: Pass | MIT | |
| Azsdk Common Generate SDK PipelineAzure/azure-sdk-tools | 134 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Azsdk Common Pipeline AnalysisAzure/azure-sdk-tools | 134 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Repo Genome
ruvnet/metaharness
7-section readiness scorecard for a LOCAL repo. An agent skill from ruvnet/metaharness.
Verify Witness
ruvnet/metaharness
Verify the Ed25519 witness manifest of a scaffolded harness.
- Official
Azsdk Common Generate SDK Pipeline
Azure/azure-sdk-tools
Run the Azure SDK generation pipeline for a release plan and create the generated SDK pull requests, for one language or for all languages.
- Official
Azsdk Common Pipeline Analysis
Azure/azure-sdk-tools
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format.
Roam Release Readiness
Cranot/roam-code
Qualify a Roam commit or accumulated batch for package, website, or server publication; reconcile source, tests, review, CI and deployed identities, and identify the next authorized release step.
More from Azure/azure-sdk-for-android
- Official
Azsdk Common Apiview Feedback Resolution
Azure/azure-sdk-for-android
Analyze and resolve APIView review feedback on Azure SDK PRs.
- Official
Azsdk Common Generate SDK Locally
Azure/azure-sdk-for-android
Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization.
- Official
Azsdk Common Pipeline Troubleshooting
Azure/azure-sdk-for-android
Diagnose and resolve failures in Azure SDK CI and generation pipelines.
- Official
Azsdk Common SDK Release
Azure/azure-sdk-for-android
Check release readiness and trigger the release pipeline for Azure SDK packages.
Related
Categories
Questions about Azsdk Common Prepare Release Plan
What does Azsdk Common Prepare Release Plan do?
Create and manage release plan work items for Azure SDK releases across languages. Azsdk Common Prepare Release Plan is an agent skill from Azure/azure-sdk-for-android, published by the product's own GitHub organization. Create and manage release plan work items for Azure SDK releases across languages.
When should I use Azsdk Common Prepare Release Plan?
Azsdk Common Prepare Release Plan fits situations like: : create release plan; update release plan; link SDK PR to plan; namespace approval.
How do I install Azsdk Common Prepare Release Plan in Claude Code?
Run `npx skills add Azure/azure-sdk-for-android --skill azsdk-common-prepare-release-plan -a claude-code`. Or copy the skill folder (.github/skills/azsdk-common-prepare-release-plan in Azure/azure-sdk-for-android) into .claude/skills/azsdk-common-prepare-release-plan in your project. Claude Code loads it when a task matches its description.
How do I install Azsdk Common Prepare Release Plan in Codex?
Run `npx skills add Azure/azure-sdk-for-android --skill azsdk-common-prepare-release-plan -a codex`. Or copy the skill folder (.github/skills/azsdk-common-prepare-release-plan in Azure/azure-sdk-for-android) into .agents/skills/azsdk-common-prepare-release-plan in your project. Codex loads it when a task matches its description.
Can I use Azsdk Common Prepare Release Plan in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Azure/azure-sdk-for-android --skill azsdk-common-prepare-release-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azsdk-common-prepare-release-plan, .gemini/skills/azsdk-common-prepare-release-plan, .github/skills/azsdk-common-prepare-release-plan and .opencode/skills/azsdk-common-prepare-release-plan in your project.
What does Azsdk Common Prepare Release Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Azsdk Common Prepare Release Plan is instructions for the agent only. Compatibility (from SKILL.md): azure-sdk-mcp server, API spec PR, or TypeSpec project path.
Does Azsdk Common Prepare Release Plan access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Azsdk Common Prepare Release Plan safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Azsdk Common Prepare Release Plan use?
Azsdk Common Prepare Release Plan is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Azsdk Common Prepare Release Plan use?
About 733 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 454 tokens, read only when the agent opens those files.
What are the alternatives to Azsdk Common Prepare Release Plan?
Skills that share tags, products or a category with Azsdk Common Prepare Release Plan: Azsdk Common Prepare Release Plan (Azure/azure-sdk-tools, 134 stars), Repo Genome (ruvnet/metaharness, 696 stars), Verify Witness (ruvnet/metaharness, 696 stars) and Azsdk Common Generate SDK Pipeline (Azure/azure-sdk-tools, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Azsdk Common Prepare Release Plan?
Azure (a GitHub organization, an official publisher) maintains it in Azure/azure-sdk-for-android, which has 121 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on June 7, 2026.
Source: Azure/azure-sdk-for-android on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.