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 Generate SDK Pipeline

by Azure in 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.

OfficialMITAuto-check passedDevelopment

Install Azsdk Common Generate SDK Pipeline

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

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

GitHub CLI
$ gh skill install Azure/azure-sdk-tools azsdk-common-generate-sdk-pipeline --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-generate-sdk-pipeline .claude/skills/azsdk-common-generate-sdk-pipeline && 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-generate-sdk-pipeline
GitHub stars
134
Token cost
~1.5k tokens
SKILL.md length
613 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

Run the Azure SDK generation pipeline for a release plan and create the generated SDK pull requests, for one language or for all languages.

  • Works in 4 steps: Collect release plan — Get the release… → Determine languages — If the user asked… → Generate per language — For each target… → …
  • : run SDK generation for all languages
  • SKILL.md covers Triggers, Rules, MCP Tools and Steps, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Azsdk Common Generate SDK Pipeline is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Run the Azure SDK generation pipeline for a release plan and create the generated SDK pull requests, for one language or for all languages. UTILITY SKILL. USE FOR: "run SDK generation for all languages", "generate SDK for release plan <id", "generate SDK for release <id", "pipeline SDK generation", "generate SDK without a local clone", "create SDK pull requests". DO NOT USE FOR: generating a single SDK locally from a local clone (use azsdk-common-generate-sdk-locally), releasing/publishing an already-generated…

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: azure-sdk-mcp server, existing release plan work item. Supports .NET, Java, JavaScript, Python, Go

It sits in Development, covering Pull requests, Feature launches and release readiness and API design. 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

  • : run SDK generation for all languages
  • Generate SDK for release plan <id
  • Generate SDK for release <id
  • Pipeline SDK generation

Example prompts

  • “run SDK generation for all languages”
  • “generate SDK for release plan <id”
  • “generate SDK for release <id”
  • “/azsdk-common-generate-sdk-pipeline”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): azure-sdk-mcp server, existing release plan work item. Supports .NET, Java, JavaScript, Python, Go

Workflow steps

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

  1. Collect release plan — Get the release plan work item ID (or release plan ID) from the user, then call…
  2. Determine languages — If the user asked for "all languages", determine the languages the release plan targets (e.g. via…
  3. Generate per language — For each target language, run azure-sdk-mcp:azsdk_run_generate_sdk passing the TypeSpec project path, the SDK…
  4. Report pull requests — After each run completes, retrieve and show the generated SDK pull request link with…

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, existing release plan work item. Supports .NET, Java, JavaScript, Python, Go

    From compatibility in the SKILL.md frontmatter.

Context cost

Azsdk Common Generate SDK Pipeline loads about 1.5k tokens when it runs. Until then it costs about 187 tokens; SKILL.md has 613 words of instructions outside code blocks.

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

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). 613 words, ~1,460 tokens.

Download SKILL.mdSave it as .claude/skills/azsdk-common-generate-sdk-pipeline/SKILL.md (or your agent's skills folder).
name
azsdk-common-generate-sdk-pipeline
description
Run the Azure SDK generation pipeline for a release plan and create the generated SDK pull requests, for one language or for all languages. **UTILITY SKILL**. USE FOR: "run SDK generation for all languages", "generate SDK for release plan <id>", "generate SDK for release <id>", "pipeline SDK generation", "generate SDK without a local clone", "create SDK pull requests". DO NOT USE FOR: generating a single SDK locally from a local clone (use azsdk-common-generate-sdk-locally), releasing/publishing an already-generated package (use azsdk-common-sdk-release), API design review. INVOKES: azure-sdk-mcp:azsdk_get_release_plan, azure-sdk-mcp:azsdk_run_generate_sdk, azure-sdk-mcp:azsdk_get_sdk_pull_request_link.
compatibility
azure-sdk-mcp server, existing release plan work item. Supports .NET, Java, JavaScript, Python, Go
license
MIT
metadata.version
1.0.0
metadata.distribution
shared

Generate SDK via Pipeline

This skill runs the Azure SDK generation pipeline for a release plan and produces the generated SDK pull request(s). It is the correct workflow when the user asks to generate SDKs for all languages, to generate for a release plan / release ID, or to generate without a local clone — none of which the local-generation workflow handles.

Triggers

USE FOR: run SDK generation for all languages, generate SDK for a release plan, generate SDK for a release ID, pipeline SDK generation, generate SDK without a local clone, create SDK pull requests WHEN: "run SDK generation, run SDK generation for all languages for release plan <id>", "generate SDK for release plan <id>", "generate SDK for release <id>", "pipeline SDK generation", "generate SDK without a local clone" DO NOT USE FOR: generating a single SDK locally from a local clone (use azsdk-common-generate-sdk-locally); releasing or publishing an already-generated package (use azsdk-common-sdk-release); API design review

Rules

  • Always call azure-sdk-mcp:azsdk_run_generate_sdk to generate. Do not use azure-sdk-mcp:azsdk_release_sdk (that publishes an already-generated package, it does not generate) or azure-sdk-mcp:azsdk_get_sdk_pull_request_link / azure-sdk-mcp:azsdk_get_pull_request (those only retrieve links) to generate an SDK.
  • azure-sdk-mcp:azsdk_run_generate_sdk generates one language per call. To generate for all languages, call it once per language the release plan targets.
  • A release plan work item ID (or release plan ID) is required. azsdk_run_generate_sdk also requires the TypeSpec project path and the SDK release type (beta or stable) as explicit inputs, and it validates them — it does not read them from the release plan. First call azure-sdk-mcp:azsdk_get_release_plan to obtain the TypeSpec project path, SDK release type, and target languages, then pass those into each generation call along with the work item ID.
  • Generation uses the release plan’s saved spec commit when present. Plans without a saved commit keep the existing branch/PR behavior.
  • Requires the azure-sdk-mcp server; there is no CLI fallback for the pipeline generation workflow.
  • Private Preview release plans cannot generate SDKs via the pipeline — only the API spec PR needs to merge. If needed for validation, direct the user to generate locally via azsdk-common-generate-sdk-locally.

MCP Tools

ToolPurpose
azure-sdk-mcp:azsdk_get_release_planFetch the release plan to determine target languages / details
azure-sdk-mcp:azsdk_run_generate_sdkRun the generation pipeline (once per language)
azure-sdk-mcp:azsdk_get_sdk_pull_request_linkRetrieve the generated SDK pull request link after generation
Show full SKILL.md (242 more words)Show less

Steps

  1. Collect release plan — Get the release plan work item ID (or release plan ID) from the user, then call azure-sdk-mcp:azsdk_get_release_plan to fetch it.
  2. Determine languages — If the user asked for "all languages", determine the languages the release plan targets (e.g. via azure-sdk-mcp:azsdk_get_release_plan). Otherwise use the single language requested.
  3. Generate per language — For each target language, run azure-sdk-mcp:azsdk_run_generate_sdk passing the TypeSpec project path, the SDK release type (beta or stable), and the language taken from the release plan, plus the release plan work item ID. These inputs are required and validated — an invalid TypeSpec project path, or a release type other than beta/stable, fails the run.
  4. Report pull requests — After each run completes, retrieve and show the generated SDK pull request link with azure-sdk-mcp:azsdk_get_sdk_pull_request_link.

Examples

  • "Run SDK generation for all languages for release 12345"
  • "Generate the SDK for release plan 12345"
  • "Generate the Python and .NET SDKs for release 12345 using the pipeline"

Troubleshooting

  • If the agent tries azsdk_release_sdk, get-artifact, or get-service-details tools instead of generating, redirect it to azure-sdk-mcp:azsdk_run_generate_sdk — that is the only tool that runs the generation pipeline.
  • If the correct tool is not yet available in the session, activate/load the azure-sdk-mcp TypeSpec SDK toolset first, then call azure-sdk-mcp:azsdk_run_generate_sdk.
  • If generation fails with a missing SDK details error, ensure the release plan has SDK details populated for the language before re-running.
  • Requires the azure-sdk-mcp server. No CLI fallback — prompt the user to configure MCP if unavailable.

© 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

Just SKILL.md in .github/skills/azsdk-common-generate-sdk-pipeline of Azure/azure-sdk-tools.

Open the folder on GitHubat commit 942ef24

Compare with similar skills

Azsdk Common Generate SDK Pipeline 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 Generate SDK Pipeline compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azsdk Common Generate SDK Pipeline this skillAzure/azure-sdk-tools134—~1.5kAutomated safety check: PassMIT
Review PRPrefectHQ/fastmcp28k—~3.1kAutomated safety check: PassApache-2.0
ObservalObserval/Observal4.3k—~2.2kAutomated safety check: PassApache-2.0
Ue Live DebuggingJasonMa0012/MooaToon750—~2.9kAutomated safety check: NotesCustom licence
Code Reviewimbenrabi/Financial-Modeling-Prep-MCP-Server150—~2.6kAutomated safety check: PassApache-2.0
PR Reviewconfluentinc/mcp-confluent167—~4.6kAutomated safety check: NotesMIT

Similar skills

  • Review PR

    PrefectHQ/fastmcp

    Assess a FastMCP pull request for justified behavior, compatibility, and correctness, then follow CI and review feedback to a revision-specific verdict.

    28k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Observal

    Observal/Observal

    A skill your agent uses when starting any task the organization may already have an approved skill, prompt, MCP server, or Agent for: reviewing code, a commit, a diff, or a pull request; writing…

    4.3k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Ue Live Debugging

    JasonMa0012/MooaToon

    A skill your agent uses when debugging UE C++ crashes, runtime bugs, or unexpected behavior with Rider MCP available.

    750 GitHub stars~2.9k tokensUpdated 23 days ago
    DevelopmentAuto-check: notes

  • Code Review

    imbenrabi/Financial-Modeling-Prep-MCP-Server

    Review a PR or working diff against this repo's intent layer (the AGENTS.md hierarchy), toolception pitfalls, and core invariants.

    150 GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • PR Review

    confluentinc/mcp-confluent

    Reviews pull requests for the Confluent MCP server. An agent skill from confluentinc/mcp-confluent.

    167 GitHub stars~4.6k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • 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 Generate SDK Pipeline

What does Azsdk Common Generate SDK Pipeline do?

Run the Azure SDK generation pipeline for a release plan and create the generated SDK pull requests, for one language or for all languages. Azsdk Common Generate SDK Pipeline is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Run the Azure SDK generation pipeline for a release plan and create the generated SDK pull requests, for one language or for all languages.

When should I use Azsdk Common Generate SDK Pipeline?

Azsdk Common Generate SDK Pipeline fits situations like: : run SDK generation for all languages; generate SDK for release plan <id; generate SDK for release <id; pipeline SDK generation.

How do I install Azsdk Common Generate SDK Pipeline in Claude Code?

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

How do I install Azsdk Common Generate SDK Pipeline in Codex?

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

Can I use Azsdk Common Generate SDK Pipeline 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-generate-sdk-pipeline -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-generate-sdk-pipeline, .gemini/skills/azsdk-common-generate-sdk-pipeline, .github/skills/azsdk-common-generate-sdk-pipeline and .opencode/skills/azsdk-common-generate-sdk-pipeline in your project.

What does Azsdk Common Generate SDK Pipeline need to run?

SKILL.md names no scripts, command-line tools or credentials: Azsdk Common Generate SDK Pipeline is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): azure-sdk-mcp server, existing release plan work item. Supports .NET, Java, JavaScript, Python, Go.

Does Azsdk Common Generate SDK Pipeline 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 Generate SDK Pipeline 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 Generate SDK Pipeline use?

Azsdk Common Generate SDK Pipeline 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 Generate SDK Pipeline use?

About 1.5k tokens (SKILL.md is roughly 5.8k 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 Generate SDK Pipeline?

Skills that share tags, products or a category with Azsdk Common Generate SDK Pipeline: Review PR (PrefectHQ/fastmcp, 28k stars), Observal (Observal/Observal, 4.3k stars), Ue Live Debugging (JasonMa0012/MooaToon, 750 stars) and Code Review (imbenrabi/Financial-Modeling-Prep-MCP-Server, 150 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Azsdk Common Generate SDK Pipeline?

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.