How do I install the Azsdk Common Sdk Release skill?

Run npx skillmds@latest add azure-azure-sdk-for-js/azsdk-common-sdk-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Azsdk Common Sdk Release safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Azsdk Common Sdk Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Azsdk Common Sdk Release free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Azsdk Common Sdk Release?

Azure (@azure-azure-sdk-for-js) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Azsdk Common Sdk Release by azure-azure-sdk-for-js

Name: Azsdk Common Sdk Release
Rating: 4.666666666666667 (3 reviews)
Author: Azure

Azsdk Common Sdk Release

Check release readiness and trigger the release pipeline for Azure SDK packages. **UTILITY SKILL**. USE FOR: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK". DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation. INVOKES: azure-sdk-mcp:azsdk_release_sdk.

Azure Updated Sep 10, 2026

File contents

SDK Release

This skill checks release readiness and triggers the Azure SDK release pipeline for packages that are already prepared, guiding the user through prerequisite validation, readiness review, and the final pipeline launch with required approval steps.

Triggers

USE FOR: release SDK, trigger release, check release readiness, release pipeline, publish package, ship SDK WHEN: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK" DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation

Rules

Requires the azure-sdk-mcp server; there is no CLI fallback for the release workflow.
Collect packageName and language, then run the readiness check before attempting to trigger release.
If release is triggered, show the pipeline link and remind the user that the release stage still requires approval.

MCP Tools

Tool	Purpose
`azure-sdk-mcp:azsdk_release_sdk`	Check release readiness and/or trigger the release pipeline

Steps

Collect Info — Get packageName and language from the user. Optionally get branch (defaults to main).
Determine Intent — If the user explicitly asks to "check readiness" or "check if ready", run azure-sdk-mcp:azsdk_release_sdk with checkReady: true. Otherwise, proceed to trigger the release directly.
Trigger Release — Run azure-sdk-mcp:azsdk_release_sdk with checkReady: false (the default). Show pipeline link and inform user they must approve the release stage.
Review Results — If the release fails due to readiness issues, display failing checks and guide user to resolve.

Examples

"Check if azure-storage-blob is ready for release"
"Trigger release for @azure/core-rest-pipeline on JavaScript"

Troubleshooting

If readiness check fails, review each failing prerequisite individually before re-triggering.
Requires azure-sdk-mcp server. No CLI fallback — prompt user to configure MCP if unavailable.

---name: azsdk-common-sdk-releasedescription: Check release readiness and trigger the release pipeline for Azure SDK packages. **UTILITY SKILL**. USE FOR: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK". DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation. INVOKES: azure-sdk-mcp:azsdk_release_sdk.license: MIT---# SDK ReleaseThis skill checks release readiness and triggers the Azure SDK release pipeline for packages that are already prepared, guiding the user through prerequisite validation, readiness review, and the final pipeline launch with required approval steps.## TriggersUSE FOR: release SDK, trigger release, check release readiness, release pipeline, publish package, ship SDKWHEN: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK"DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation## Rules- Requires the `azure-sdk-mcp` server; there is no CLI fallback for the release workflow.- Collect `packageName` and `language`, then run the readiness check before attempting to trigger release.- If release is triggered, show the pipeline link and remind the user that the release stage still requires approval.## MCP Tools| Tool | Purpose || --------------------------------- | ----------------------------------------------------------- || `azure-sdk-mcp:azsdk_release_sdk` | Check release readiness and/or trigger the release pipeline |## Steps1. **Collect Info** — Get `packageName` and `language` from the user. Optionally get `branch` (defaults to main).2. **Determine Intent** — If the user explicitly asks to "check readiness" or "check if ready", run `azure-sdk-mcp:azsdk_release_sdk` with `checkReady: true`. Otherwise, proceed to trigger the release directly.3. **Trigger Release** — Run `azure-sdk-mcp:azsdk_release_sdk` with `checkReady: false` (the default). Show pipeline link and inform user they must approve the release stage.4. **Review Results** — If the release fails due to readiness issues, display failing checks and guide user to resolve.## Examples- "Check if azure-storage-blob is ready for release"- "Trigger release for @azure/core-rest-pipeline on JavaScript"## Troubleshooting- If readiness check fails, review each failing prerequisite individually before re-triggering.- Requires `azure-sdk-mcp` server. No CLI fallback — prompt user to configure MCP if unavailable.

Frequently asked questions