New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Azsdk Common SDK Breaking Change

by Azure in Azure/azure-sdk-tools

Detect and mitigate SDK Breaking changes for an SDK package which is generated from TypeSpec.

OfficialMITAuto-check passedAgent Workflows

Install Azsdk Common SDK Breaking Change

skills CLI
$ npx skills add Azure/azure-sdk-tools --skill azsdk-common-sdk-breaking-change -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Azure/azure-sdk-tools azsdk-common-sdk-breaking-change --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-sdk-breaking-change .claude/skills/azsdk-common-sdk-breaking-change && rm -rf skills-src

Use ~/.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/

Facts

Skill name
azsdk-common-sdk-breaking-change
GitHub stars
134
Token cost
~1.2k tokens
SKILL.md length
539 words
Files
4
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

Detect and mitigate SDK Breaking changes for an SDK package which is generated from TypeSpec.

  • Works in 5 steps: Follow azsdk-common-generate-sdk-locally… → Detect SDK breaking Changes - Run… → Display detected breaking changes — If… → …
  • Tasks that involve MCP servers
  • 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 SDK Breaking Change is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Detect and mitigate SDK Breaking changes for an SDK package which is generated from TypeSpec. WHEN: "Detect SDK breaking changes for a service", "Detect SDK breaking changes for an SDK package", "Detect and mitigate SDK breaking changes for a service", "Detect and mitigate SDK breaking changes for an SDK package". INVOKES: skill: azsdk-common-generate-sdk-locally; MCP tools: azure-sdk-mcp:azsdkcustomizedcodeupdate, azure-sdk-mcp:azsdkpackagedetectbreakingchange.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `evals/eval.yaml` and `evals/trigger.eval.yaml`). Compatibility notes: azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools

It sits in Agent Workflows, covering MCP servers. It works with Microsoft Azure and Model Context Protocol. The repository describes itself as: Tools repository leveraged by the Azure SDK team. The licence is MIT.

When your agent uses it

  • Tasks that involve MCP servers

Example prompts

  • “Detect SDK breaking changes for a service”
  • “Detect SDK breaking changes for an SDK package”
  • “Detect and mitigate SDK breaking changes for a service”
  • “/azsdk-common-sdk-breaking-change”

Requirements

  • Compatibility (from SKILL.md): azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Follow azsdk-common-generate-sdk-locally skill to generate SDK only. For .NET, require the preparatory build to disable API compatibility…
  2. Detect SDK breaking Changes - Run azure-sdk-mcp:azsdk_package_detect_breaking_change
  3. Display detected breaking changes — If step 3 fails, display the ResponseError message and stop processing the current language. If step 3…
  4. Prompt the user to choose breaking changes to mitigate — If the user requested detection only, stop processing the current language after…
  5. Mitigate selected SDK breaking changes — If the user selects no changes in step 5, stop processing the current language. Otherwise, run…

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, local azure-sdk-for-{language} clone, language build tools

    From compatibility in the SKILL.md frontmatter.

Context cost

Azsdk Common SDK Breaking Change loads about 1.2k tokens when it runs. Until then it costs about 127 tokens; SKILL.md has 539 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~127
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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). 539 words, ~1,214 tokens.

Download SKILL.mdSave it as .claude/skills/azsdk-common-sdk-breaking-change/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
azsdk-common-sdk-breaking-change
description
Detect and mitigate SDK Breaking changes for an SDK package which is generated from TypeSpec. WHEN: "Detect SDK breaking changes for a service", "Detect SDK breaking changes for an SDK package", "Detect and mitigate SDK breaking changes for a service", "Detect and mitigate SDK breaking changes for an SDK package". INVOKES: skill: azsdk-common-generate-sdk-locally; MCP tools: azure-sdk-mcp:azsdk_customized_code_update, azure-sdk-mcp:azsdk_package_detect_breaking_change.
compatibility
azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools
license
MIT
metadata.version
1.0.0
metadata.distribution
shared

SDK Breaking Change Detection and Mitigation

MCP Tools

ToolPurpose
azure-sdk-mcp:azsdk_customized_code_updateApply customizations
azure-sdk-mcp:azsdk_package_detect_breaking_changeDetect SDK breaking changes

Prerequisites: azure-sdk-mcp server must be running.

Steps

  1. Select language — First extract one or more target languages from the user's prompt. If the prompt specifies any target languages, use them without asking the user to confirm. If it does not specify a target language, prompt the user to choose one or more from this list, presented in exactly this order: Go, Java, JavaScript, Python, .NET.
  • For each selected language in step 1, execute steps 2 through 6 one language at a time — fully complete all steps for one language before starting the next. Process multiple selected languages in the same order they appear in the list above.
  1. Follow azsdk-common-generate-sdk-locally skill to generate SDK only. For .NET, require the preparatory build to disable API compatibility checks using additionalArguments: "/p:RunApiCompat=false". This is a requirement of this workflow: compatibility findings must reach the detection and user-selection steps rather than be automatically repaired during generation.
  2. Detect SDK breaking Changes - Run azure-sdk-mcp:azsdk_package_detect_breaking_change
  3. Display detected breaking changes — If step 3 fails, display the ResponseError message and stop processing the current language. If step 3 detects breaking changes, display a ## Detected Breaking Changes title followed by a Markdown table. Include exactly one breaking change per row with these columns: Breaking Change, Category, and Resolution. Preserve the category and resolution returned by the detection tool; do not replace them with a summary. If no breaking changes are detected, report that result and stop processing the current language.
  4. Prompt the user to choose breaking changes to mitigate — If the user requested detection only, stop processing the current language after displaying the results. Otherwise, present the list from step 3 as a multiple-choice selection.
  5. Mitigate selected SDK breaking changes — If the user selects no changes in step 5, stop processing the current language. Otherwise, run azure-sdk-mcp:azsdk_customized_code_update for the selected changes with these parameters:
Show full SKILL.md (213 more words)Show less
  • packagePath: The SDK package path
  • customizationRequest: resolve the 'breakingChanges' chosen in step 5
  • tspProjectPath: the typespec project path
  • editScope: Set this based on the repository where the skill is running. When running in the target SDK language repository, use 'CustomCode'. When running in azure-rest-api-specs, use 'All' if the target SDK language repository is also available as a local clone; otherwise, use 'SpecInputs'.

After step 6, begin the next iteration. If the customization modified TypeSpec, first repeat step 2 to regenerate the SDK; otherwise, resume at step 3. Then repeat steps 3 through 6. Run at most three detection-and-mitigation iterations per language, stopping earlier if no breaking changes remain or the user declines further mitigation. After the third mitigation, run step 3 once more to identify and report any remaining breaking changes, then stop without offering a fourth mitigation.

Examples

  • "Detect and mitigate SDK breaking changes for the service"
  • "Detect SDK breaking changes for the service"
  • "Detect SDK breaking changes for Go SDK package"
  • "Detect and mitigate SDK breaking changes for Go SDK package"

Troubleshooting

  • Requires the azure-sdk-mcp server. If it is unavailable, direct the user to the quick-start guide to configure it before continuing.
  • Requires a local clone of the target SDK repository. If unavailable, prompt the user to clone it before continuing.

© 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 3 other files in .github/skills/azsdk-common-sdk-breaking-change of Azure/azure-sdk-tools.

  • SKILL.md
  • evals/eval.yaml
  • evals/trigger.eval.yaml
  • fixtures/detect-sdk-breaking-changes-for-service-001/models.tsp

Open the folder on GitHubat commit 942ef24

Compare with similar skills

Azsdk Common SDK Breaking Change 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.

Azsdk Common SDK Breaking Change compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azsdk Common SDK Breaking Change this skillAzure/azure-sdk-tools134—~1.2kAutomated safety check: PassMIT
Azsdk Common Pipeline TroubleshootingAzure/azure-sdk-for-android121—~496Automated safety check: PassMIT
Azure Resource Lookupmicrosoft/GitHub-Copilot-for-Azure2551 repos~1.4kAutomated safety check: PassMIT
Microsoft Docsmicrosoft/ai-agents-for-beginners77k—~1.5kAutomated safety check: PassMIT
Setupfcakyon/claude-codex-settings1.2k—~156Automated safety check: PassApache-2.0
Azure Connector NamespaceMicrosoftDocs/Agent-Skills776—~581Automated safety check: PassCC-BY-4.0

Similar skills

  • Azsdk Common Pipeline Troubleshooting

    Azure/azure-sdk-for-android

    Official

    Diagnose and resolve failures in Azure SDK CI and generation pipelines.

    121 GitHub stars~496 tokensUpdated 4 mo ago
    Agent WorkflowsAuto-check passed

  • Azure Resource Lookup

    microsoft/GitHub-Copilot-for-Azure

    Official

    List, find, and show Azure resources across subscriptions or resource groups.

    255 GitHub starsUsed in 1 repo~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Microsoft Docs

    microsoft/ai-agents-for-beginners

    Official

    Küsib ametlikku Microsofti dokumentatsiooni, et leida mõisteid, juhendeid ja koodinäiteid Azure'i, .NET-i, Agent Frameworki, Aspire'i, VS Code'i, GitHubi ja muu kohta.

    77k GitHub stars~1.5k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Setup

    fcakyon/claude-codex-settings

    This skill should be used when user encounters "Azure MCP error", "Azure authentication failed", "az login required", "Azure CLI not found", or needs help configuring Azure MCP integration.

    1.2k GitHub stars~156 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Azure Connector Namespace

    MicrosoftDocs/Agent-Skills

    Official

    Expert knowledge for Azure Connector Namespace development including configuration.

    776 GitHub stars~581 tokensUpdated 5 days ago
    Agent WorkflowsAuto-check passed

  • Azsdk Common Apiview Feedback Resolution

    Azure/azure-sdk-for-android

    Official

    Analyze and resolve APIView review feedback on Azure SDK PRs.

    121 GitHub stars~549 tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

More from Azure/azure-sdk-tools

All 35 skills in this repo

  • Apiview Feedback Resolution

    Azure/azure-sdk-tools

    Official

    Analyze and resolve APIView review feedback on Azure SDK PRs.

    134 GitHub stars~547 tokensUpdated yesterday
    Auto-check passed

  • Azsdk Common Live And Recorded Tests

    Azure/azure-sdk-tools

    Official

    Deploy test resources and run Azure SDK tests in live, record, or playback mode.

    134 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check: notes

  • Azsdk Common Pipeline Analysis

    Azure/azure-sdk-tools

    Official

    Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format.

    134 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Azsdk Common Prepare Release Plan

    Azure/azure-sdk-tools

    Official

    Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases.

    134 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Azure Typespec Assessment

    Azure/azure-sdk-tools

    Official

    Assess Azure TypeSpec Git diffs for semantic intent, REST and downstream SDK breaking changes, Azure Guidelines compliance, and documentation completeness.

    134 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Azsdk Common SDK Breaking Change

What does Azsdk Common SDK Breaking Change do?

Detect and mitigate SDK Breaking changes for an SDK package which is generated from TypeSpec. Azsdk Common SDK Breaking Change is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Detect and mitigate SDK Breaking changes for an SDK package which is generated from TypeSpec.

When should I use Azsdk Common SDK Breaking Change?

Azsdk Common SDK Breaking Change fits situations like: tasks that involve MCP servers.

How do I install Azsdk Common SDK Breaking Change in Claude Code?

Run `npx skills add Azure/azure-sdk-tools --skill azsdk-common-sdk-breaking-change -a claude-code`. Or copy the skill folder (.github/skills/azsdk-common-sdk-breaking-change in Azure/azure-sdk-tools) into .claude/skills/azsdk-common-sdk-breaking-change in your project. Claude Code loads it when a task matches its description.

How do I install Azsdk Common SDK Breaking Change in Codex?

Run `npx skills add Azure/azure-sdk-tools --skill azsdk-common-sdk-breaking-change -a codex`. Or copy the skill folder (.github/skills/azsdk-common-sdk-breaking-change in Azure/azure-sdk-tools) into .agents/skills/azsdk-common-sdk-breaking-change in your project. Codex loads it when a task matches its description.

Can I use Azsdk Common SDK Breaking Change 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-sdk-breaking-change -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-sdk-breaking-change, .gemini/skills/azsdk-common-sdk-breaking-change, .github/skills/azsdk-common-sdk-breaking-change and .opencode/skills/azsdk-common-sdk-breaking-change in your project.

What does Azsdk Common SDK Breaking Change need to run?

SKILL.md names no scripts, command-line tools or credentials: Azsdk Common SDK Breaking Change is instructions for the agent only. Compatibility (from SKILL.md): azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools.

Does Azsdk Common SDK Breaking Change 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 SDK Breaking Change 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 SDK Breaking Change use?

Azsdk Common SDK Breaking Change 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 SDK Breaking Change use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Azsdk Common SDK Breaking Change?

Skills that share tags, products or a category with Azsdk Common SDK Breaking Change: Azsdk Common Pipeline Troubleshooting (Azure/azure-sdk-for-android, 121 stars), Azure Resource Lookup (microsoft/GitHub-Copilot-for-Azure, 255 stars), Microsoft Docs (microsoft/ai-agents-for-beginners, 77k stars) and Setup (fcakyon/claude-codex-settings, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Azsdk Common SDK Breaking Change?

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.