Azsdk Common Prepare Release Plan
Azure/azure-sdk-for-android
Create and manage release plan work items for Azure SDK releases across languages.
Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases.
Install Azsdk Common Prepare Release Plan
$ npx skills add Azure/azure-sdk-tools --skill azsdk-common-prepare-release-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/azure-sdk-tools 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-tools.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-tools/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-tools/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-tools --skill azsdk-common-prepare-release-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/azure-sdk-tools 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-tools.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-tools/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-tools --skill azsdk-common-prepare-release-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/azure-sdk-tools 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-tools.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-tools/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-tools.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-tools --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-tools 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-tools.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-tools/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-tools 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-tools --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-tools.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-tools/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-tools --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-tools 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-tools.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-tools/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
- 134
- Token cost
- ~2.7k tokens
- SKILL.md length
- 1,240 words
- Files
- 6 (incl. references)
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases.
- Works in 6 steps: Create Release Plan → Get Release Plan → Update Release Plan / Update API Spec in… → …
- : create release plan
- SKILL.md covers Triggers, Rules, MCP Tools and Use Cases, plus 2 more sections
- 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-tools, published by the product's own GitHub organization. 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:azsdkcreatereleaseplan…
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `evals/eval.yaml`, `evals/schedule-risk.eval.yaml` and `evals/trigger.eval.yaml`). Compatibility notes: azure-sdk-mcp server, API spec PR in Azure/azure-rest-api-specs
It sits in Product & Project Management, covering Feature launches and release readiness and OpenAPI specifications. It works with Microsoft Azure, Model Context Protocol and Azure DevOps. The repository describes itself as: Tools repository leveraged by the Azure SDK team. The licence is MIT.
When your agent uses it
- : create release plan
- Get release plan
- Update release plan
- Update API spec in release plan
Example prompts
- “create release plan”
- “get release plan”
- “update release plan”
- “/azsdk-common-prepare-release-plan”
Requirements
- Python 3
- Compatibility (from SKILL.md): azure-sdk-mcp server, API spec PR in Azure/azure-rest-api-specs
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 942ef24. 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 in Azure/azure-rest-api-specs
From compatibility in the SKILL.md frontmatter.
Context cost
Azsdk Common Prepare Release Plan loads about 2.7k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 233 tokens; SKILL.md has 1,240 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-tools at commit 942ef24, republished under its MIT licence (© Azure). 1,240 words, ~2,735 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 5 other files; get the full folder from GitHub.- name
- azsdk-common-prepare-release-plan
- description
- 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.
- compatibility
- azure-sdk-mcp server, API spec PR in Azure/azure-rest-api-specs
- license
- MIT
- metadata.version
- 1.0.0
- metadata.distribution
- shared
Prepare Release Plan
This skill creates, gets, updates, abandons, and links SDK PRs to release plan work items for Azure SDK releases, helping gather required release data, validate spec inputs, and link related approvals or SDK pull requests without exposing internal work item URLs.
Triggers
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 WHEN: "create release plan", "get release plan", "update 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
Rules
- Do not display Azure DevOps work item URLs; only provide the Release Plan Link and ID.
- Require an API spec PR link or a TypeSpec project path before creating or updating a plan.
- Validate that the spec PR repository matches the requested API release type before creation.
- Release plan tools accept either a Release Plan ID or an Azure DevOps work item ID, except metadata updates:
azure-sdk-mcp:azsdk_update_release_planrequires the exactWorkItemId. If only a Release Plan ID is known, get that plan and use its returnedWorkItemId; do not treat the two IDs as interchangeable. - Create/update accept optional
specCommitSha; omission on update preserves the saved SHA. - Always relay schedule-risk
warningsandnext_stepsreturned by release plan tools. For each past-due plan, show its Release Plan ID and dashboard link, then present both choices: update its target release month or abandon it and record the reason in the dashboard.
MCP Tools
| Tool | Purpose |
|---|---|
azure-sdk-mcp:azsdk_create_release_plan | Create a new release plan |
azure-sdk-mcp:azsdk_get_release_plan | Get plan by ID, path, or spec PR |
azure-sdk-mcp:azsdk_update_release_plan | Update release plan metadata |
azure-sdk-mcp:azsdk_update_release_plan_target | Update the target release month |
azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan | Update API spec PR URL in plan |
azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan | Update SDK/package details in plan |
azure-sdk-mcp:azsdk_abandon_release_plan | Abandon a release plan |
azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan | Link SDK PR to release plan |
azure-sdk-mcp:azsdk_link_namespace_approval_issue | Link namespace approval issue |
Use Cases
1. Create Release Plan
When: User wants to create a release plan for a TypeSpec project.
Steps:
- Get TypeSpec Project Path — Ask the user for the relative TypeSpec project path (directory containing
tspconfig.yaml, e.g.specification/contosowidgetmanager/Contoso.WidgetManager). Always use the relative path from the repo root, not an absolute path. - Check Existing — Run
azure-sdk-mcp:azsdk_get_release_planwith the relativetypeSpecProjectPathto check if a release plan already exists.- If a release plan exists with the same API release type the user requested: inform the user that a release plan already exists, show the Release Plan ID, status, and API release type. Suggest the user use the existing release plan. Do NOT create a new one.
- If a release plan exists but for a different API release type: inform the user about the existing plan and its API release type, then proceed to create a new release plan using
forceCreateReleasePlan: truefor the user's requested API release type. Do NOT attempt to update the existing release plan's API release type. - If no release plan exists, proceed to step 3.
- Gather Info — Collect required details from the user. See details:
- Target release month/year (format: "Month YYYY", e.g. "June 2026"). Do NOT use formats like "2026-06" or "06/2026" — these are invalid.
- API release type: Value must be one of the following: "Private Preview", "Public Preview", or "GA"
- Spec PR URL (optional)
- Service Tree ID (GUID) — optional if previously created
- Product Tree ID (GUID) — optional if previously created
- Create — Run
azure-sdk-mcp:azsdk_create_release_planwith the collected parameters. UseforceCreateReleasePlan: trueonly if an existing release plan was found for a different API release type. - Namespace — For first management plane releases, link namespace approval issue using
azure-sdk-mcp:azsdk_link_namespace_approval_issue.
IMPORTANT: Do NOT update an existing release plan to change its API release type. If a release plan exists for a different API release type, force-create a new one instead.
Tool: azure-sdk-mcp:azsdk_create_release_plan
2. Get Release Plan
When: User wants to check the status or details of an existing release plan.
Steps:
- Identify Plan — Ask user for one of:
- Release plan ID or work item ID
- Relative TypeSpec project path (e.g.
specification/contosowidgetmanager/Contoso.WidgetManager) - Spec PR URL
- Query — Run
azure-sdk-mcp:azsdk_get_release_planwith the provided identifier. Always use a relative path fortypeSpecProjectPath; usespecPullRequestUrlwhen the user provides only a spec PR URL. - Display — Show the release plan ID, status, linked PRs, and SDK details. Always relay schedule-risk warnings and recommended actions from the response.
Tool: azure-sdk-mcp:azsdk_get_release_plan
Show full SKILL.md (503 more words)Show less
3. Update Release Plan / Update API Spec in Release Plan
When: User needs to update release plan metadata (spec PR URL, TypeSpec project path, SDK release type, service/product IDs) or update the API spec PR link.
Steps:
- Identify Plan — Use the exact Azure DevOps work item ID. If only a Release Plan ID is known, get the plan and use its returned
WorkItemId. - Update Metadata — Run
azure-sdk-mcp:azsdk_update_release_planwith:typeSpecProjectPath(required)workItemId(required — exact Azure DevOps work item ID; no PR/path fallback)specPullRequestUrl(optional)sdkReleaseType(required — do NOT default this from API release type; always ask user explicitly)serviceTreeId(optional)productTreeId(optional)
- Update API Spec PR — If only the spec PR URL needs updating, run
azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_planwith:specPullRequestUrl(required)workItemIdorreleasePlanId
Tools: azure-sdk-mcp:azsdk_update_release_plan, azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan
4. Update SDK/Package Details in Release Plan
When: User needs to update SDK language and package name details in the release plan after code generation or configuration changes.
Steps:
- Identify Plan — Get the Release Plan ID or work item ID from the user (either is accepted).
- Identify TypeSpec Project — Get or confirm the TypeSpec project path.
- Update — Run
azure-sdk-mcp:azsdk_update_sdk_details_in_release_planwith:workItemId(required — accepts either the Release Plan ID or the work item ID)typeSpecProjectPath(required)
Tool: azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan
5. Abandon a Release Plan
When: User decides to cancel or discard a release plan that is no longer needed.
Steps:
- Identify Plan — Get the work item ID or release plan ID from the user.
- Confirm — Ask user to confirm abandonment: "Are you sure you want to abandon this release plan? This action updates the status to Abandoned."
- Abandon — Run
azure-sdk-mcp:azsdk_abandon_release_planwith:workItemIdorreleasePlanId
Tool: azure-sdk-mcp:azsdk_abandon_release_plan
6. Link SDK Pull Request to Release Plan
When: SDK pull requests have been created and need to be associated with the release plan.
Steps:
- Identify Plan — Get the Release Plan ID or work item ID from the user (either is accepted).
- Collect PR Info — Get the SDK pull request URL and language from the user.
- Link — Run
azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_planwith:pullRequestUrl(required)language(required — e.g., ".NET", "Java", "JavaScript", "Python", "Go")workItemIdorreleasePlanId(either accepts the Release Plan ID or the work item ID)
- Repeat — If multiple SDK PRs exist for different languages, repeat for each.
Tool: azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan
Examples
- "Create a release plan for my spec PR"
- "Get the release plan for work item 12345"
- "What is the status of my release plan?"
- "Update the API spec PR in my release plan"
- "Update SDK details in release plan 67890"
- "Abandon release plan 11111"
- "Link my SDK PR to release plan"
- "Link Python SDK PR #100 to release plan 67890"
Troubleshooting
- Requires
azure-sdk-mcpserver; no CLI fallback — prompt user to configure MCP if unavailable. - If creation fails, verify spec PR URL and Service Tree IDs.
- If update fails, ensure the Release Plan ID or work item ID is correct and the plan is not already abandoned.
- If linking fails, verify the SDK PR URL is valid and the language matches a supported value.
© 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 5 other files (references) in .github/skills/azsdk-common-prepare-release-plan of Azure/azure-sdk-tools.
- SKILL.md
- evals/eval.yaml
- evals/schedule-risk.eval.yaml
- evals/trigger.eval.yaml
- fixtures/tspconfig.yaml
- references/release-plan-details.md
Open the folder on GitHubat commit 942ef24
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-tools | 134 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Azsdk Common Prepare Release PlanAzure/azure-sdk-for-android | 121 | — | ~733 | Automated safety check: Pass | MIT | |
| Azsdk Common SDK ReleaseAzure/azure-sdk-for-android | 121 | — | ~478 | 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 Pipeline TroubleshootingAzure/azure-sdk-for-android | 121 | — | ~496 | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Azsdk Common SDK Release
Azure/azure-sdk-for-android
Check release readiness and trigger the release pipeline for Azure SDK packages.
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 Pipeline Troubleshooting
Azure/azure-sdk-for-android
Diagnose and resolve failures in Azure SDK CI and generation pipelines.
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-tools
All 35 skills in this repo- Official
Apiview Feedback Resolution
Azure/azure-sdk-tools
Analyze and resolve APIView review feedback on Azure SDK PRs.
- Official
Azsdk Common Apiview Feedback Resolution
Azure/azure-sdk-tools
Analyze and resolve APIView review feedback on Azure SDK PRs.
- Official
Azsdk Common Live And Recorded Tests
Azure/azure-sdk-tools
Deploy test resources and run Azure SDK tests in live, record, or playback mode.
- 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.
- Official
Azure Typespec Assessment
Azure/azure-sdk-tools
Assess Azure TypeSpec Git diffs for semantic intent, REST and downstream SDK breaking changes, Azure Guidelines compliance, and documentation completeness.
- Official
Azure Typespec Author
Azure/azure-sdk-tools
Authors and modifies Azure TypeSpec (.tsp) API specifications.
Related
Categories
Questions about Azsdk Common Prepare Release Plan
What does Azsdk Common Prepare Release Plan do?
Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases. Azsdk Common Prepare Release Plan is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases.
When should I use Azsdk Common Prepare Release Plan?
Azsdk Common Prepare Release Plan fits situations like: : create release plan; get release plan; update release plan; update API spec in release plan.
How do I install Azsdk Common Prepare Release Plan in Claude Code?
Run `npx skills add Azure/azure-sdk-tools --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-tools) 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-tools --skill azsdk-common-prepare-release-plan -a codex`. Or copy the skill folder (.github/skills/azsdk-common-prepare-release-plan in Azure/azure-sdk-tools) 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-tools --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. Our summary lists: Python 3. Compatibility (from SKILL.md): azure-sdk-mcp server, API spec PR in Azure/azure-rest-api-specs.
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 2.7k tokens (SKILL.md is roughly 11k 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 624 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-for-android, 121 stars), Azsdk Common SDK Release (Azure/azure-sdk-for-android, 121 stars), Repo Genome (ruvnet/metaharness, 696 stars) and Verify Witness (ruvnet/metaharness, 696 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-tools, which has 134 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 10, 2026.
Source: Azure/azure-sdk-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.