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 Locally

by Azure in Azure/azure-sdk-tools

Generate and finalize Azure SDKs locally from TypeSpec, including build, checks, tests, changelog, metadata, and version updates by default.

OfficialMITAuto-check passedDevelopment

Install Azsdk Common Generate SDK Locally

skills CLI
$ npx skills add Azure/azure-sdk-tools --skill azsdk-common-generate-sdk-locally -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-locally --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-locally .claude/skills/azsdk-common-generate-sdk-locally && 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-locally
GitHub stars
134
Token cost
~2.5k tokens
SKILL.md length
1,010 words
Files
7 (incl. references)
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

Generate and finalize Azure SDKs locally from TypeSpec, including build, checks, tests, changelog, metadata, and version updates by default.

  • Works in 11 steps: Select language — Confirm target… → Verify repo — Ensure the user has a… → Identify config file — Determine the… → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Triggers, Boundaries, Rules and MCP Tools, plus 4 more sections
  • Calls npx and npm

What it does

Azsdk Common Generate SDK Locally is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Generate and finalize Azure SDKs locally from TypeSpec, including build, checks, tests, changelog, metadata, and version updates by default. WHEN: "generate SDK locally", "build SDK", "run SDK tests", "run CI checks", "validate package", "run checks", "update changelog", "fix SDK build errors", "resolve SDK generation errors", "customize TypeSpec", "rename SDK client", "rename SDK model", "hide operation from SDK", "fix analyzer errors", "resolve customization drift", "create subclient", "update metadata"…

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

It sits in Development, covering Changelog and release notes. It works with Microsoft Azure and Azure Web PubSub. 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 Changelog and release notes

Example prompts

  • “generate SDK locally”
  • “build SDK”
  • “run SDK tests”
  • “/azsdk-common-generate-sdk-locally”

Requirements

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

Workflow steps

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

  1. Select language — Confirm target language: .NET, Java, JavaScript, Python, Go, or Rust.
  2. Verify repo — Ensure the user has a local clone of the correct SDK repo. If not cloned, instruct user to clone it.
  3. Identify config file — Determine the path to the TypeSpec configuration file. See config file details.
  4. Verify setup — Run azure-sdk-mcp:azsdk_verify_setup to confirm environment.
  5. Generate — Run azure-sdk-mcp:azsdk_package_generate_code with the config file path.
  6. Build — Run azure-sdk-mcp:azsdk_package_build_code. For .NET, use the additionalArguments: "/p:RunApiCompat=false" to skip API…
  7. Customize — If build fails, or if user requests SDK modifications, run azure-sdk-mcp:azsdk_customized_code_update with the build errors or…
  8. Commit checkpoint — Prompt the user to commit generated changes before proceeding. See commit checkpoint details.
  9. Validate — Run azure-sdk-mcp:azsdk_package_run_check and azure-sdk-mcp:azsdk_package_run_tests.
  10. Metadata — Run azure-sdk-mcp:azsdk_package_update_changelog_content, azure-sdk-mcp:azsdk_package_update_metadata, and…
  11. Final commit — Prompt the user to commit final changes (changelog, metadata, version). See commit checkpoint details.

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

    Shell commands in SKILL.md call:

    • npx
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx and npm, which can reach the network depending on how they are called.

    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 Generate SDK Locally loads about 2.5k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 207 tokens; SKILL.md has 1,010 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~207
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.4k

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,010 words, ~2,517 tokens.

Download SKILL.mdSave it as .claude/skills/azsdk-common-generate-sdk-locally/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
azsdk-common-generate-sdk-locally
description
Generate and finalize Azure SDKs locally from TypeSpec, including build, checks, tests, changelog, metadata, and version updates by default. WHEN: "generate SDK locally", "build SDK", "run SDK tests", "run CI checks", "validate package", "run checks", "update changelog", "fix SDK build errors", "resolve SDK generation errors", "customize TypeSpec", "rename SDK client", "rename SDK model", "hide operation from SDK", "fix analyzer errors", "resolve customization drift", "create subclient", "update metadata", "update version". INVOKES: azsdk_verify_setup, azsdk_package_generate_code, azsdk_package_build_code, azsdk_package_run_check, azsdk_package_run_tests, azsdk_customized_code_update, azsdk_package_update_changelog_content, azsdk_package_update_metadata, azsdk_package_update_version.
compatibility
azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools
license
MIT
metadata.version
1.1.1
metadata.distribution
shared

Generate SDK Locally

This skill generates, builds, and tests Azure SDKs locally from TypeSpec with automatic customization support, covering the end-to-end workflow for fixing generation issues, applying SDK-specific updates, and refreshing package metadata when needed.

Triggers

USE FOR: generate, build, and test Azure SDKs locally from TypeSpec with automatic customization; update changelog; fix SDK build errors; resolve SDK generation errors; customize TypeSpec; rename SDK client or model; hide operation from SDK; fix analyzer errors; resolve customization drift; create subclient; update metadata; update version WHEN: "generate SDK locally", "build SDK", "run SDK tests", "update changelog", "fix SDK build errors", "resolve SDK generation errors", "customize TypeSpec", "rename SDK client", "rename SDK model", "hide operation from SDK", "fix analyzer errors", "resolve customization drift", "create subclient", "update metadata", "update version"

Boundaries

Do not use this skill for:

  • Publishing SDK packages to package registries
  • CI pipeline configuration
  • API design review

Rules

  • Interpret "generate SDK" and "generate SDK locally" as requests for the complete workflow: generate, build, validate, test, update changelog, update metadata, and update version. Do not treat the word "generate" by itself as a generate-only request.
  • Stop after generation and a successful build when the user explicitly says "generate only", "only generate", or otherwise explicitly asks to skip checks, tests, changelog, metadata, and version updates. Bind only to the generation action even when a target qualifier follows: "generate SDK only for Web PubSub" is a generate-only request scoped to Web PubSub. By contrast, "generate the SDK for only the Web PubSub service" scopes the complete workflow to one service. Once a request is classified as generate-only, do not prompt for a commit or run steps 8–11. If the user's intent is unclear, default to the complete workflow.
  • This skill generates an SDK locally from a local clone. Use it to generate an SDK only when the user indicates local generation — they say "local"/"locally", or are working from a local clone. If the user asks to "generate SDK for all languages", to generate for a release plan / release ID (even a single language), to generate without a local clone, or wants SDK pull requests created for them, do not generate locally — use the azsdk-common-generate-sdk-pipeline skill, which runs the SDK generation pipeline for each language and produces the SDK pull requests.
  • Never use azure-sdk-mcp:azsdk_get_sdk_pull_request_link or azure-sdk-mcp:azsdk_get_pull_request to generate an SDK; those only retrieve links for SDKs that were already generated.
  • Requires the azure-sdk-mcp server for the MCP workflow; without MCP, use npm exec --prefix eng/common/tsp-client -- tsp-client CLI.
  • Verify the target language repo and the correct TypeSpec configuration file before generation.
  • After generation or customization, run the check and test steps before updating metadata or finalizing changes.

MCP Tools

ToolPurpose
azure-sdk-mcp:azsdk_verify_setupVerify environment
azure-sdk-mcp:azsdk_package_generate_codeGenerate SDK
azure-sdk-mcp:azsdk_package_build_codeBuild package
azure-sdk-mcp:azsdk_package_run_checkValidate package
azure-sdk-mcp:azsdk_package_run_testsRun tests
azure-sdk-mcp:azsdk_customized_code_updateApply customizations (includes regeneration and build)
azure-sdk-mcp:azsdk_package_update_changelog_contentUpdate changelog
azure-sdk-mcp:azsdk_package_update_metadataUpdate metadata including ci.yml
azure-sdk-mcp:azsdk_package_update_versionUpdate version

Prerequisites: azure-sdk-mcp server must be running. Without MCP, use npx tsp-client CLI.

Show full SKILL.md (521 more words)Show less

Steps

  1. Select language — Confirm target language: .NET, Java, JavaScript, Python, Go, or Rust.
  2. Verify repo — Ensure the user has a local clone of the correct SDK repo. If not cloned, instruct user to clone it.
  3. Identify config file — Determine the path to the TypeSpec configuration file. See config file details.
    • From azure-rest-api-specs repo: use path to tspconfig.yaml.
    • From an SDK language repo: use path to tsp-location.yaml.
  4. Verify setup — Run azure-sdk-mcp:azsdk_verify_setup to confirm environment.
  5. Generate — Run azure-sdk-mcp:azsdk_package_generate_code with the config file path.
  6. Build — Run azure-sdk-mcp:azsdk_package_build_code. For .NET, use the additionalArguments: "/p:RunApiCompat=false" to skip API compatibility checks if user requests to skip API compatibility check.
  7. Customize — If build fails, or if user requests SDK modifications, run azure-sdk-mcp:azsdk_customized_code_update with the build errors or user request. The tool handles the full workflow internally: it classifies the issue, applies TypeSpec decorators and/or code patches, regenerates the SDK, and builds — all in one call. See customization workflow. (If the user requested "generate only", stop here — skip steps 8–11.)
  8. Commit checkpoint — Prompt the user to commit generated changes before proceeding. See commit checkpoint details.
  9. Validate — Run azure-sdk-mcp:azsdk_package_run_check and azure-sdk-mcp:azsdk_package_run_tests.
  10. Metadata — Run azure-sdk-mcp:azsdk_package_update_changelog_content, azure-sdk-mcp:azsdk_package_update_metadata, and azure-sdk-mcp:azsdk_package_update_version. (Note: For .NET data plane, skip this step — metadata, changelog, and version updates are per-commit tasks, not part of the generate/build/test workflow.)
  11. Final commit — Prompt the user to commit final changes (changelog, metadata, version). See commit checkpoint details.

SDK repos | Customization workflow | Detailed workflow

Guardrails

  • NEVER modify generated SDK code files directly for customizations. Always use azure-sdk-mcp:azsdk_customized_code_update. It handles classification, TypeSpec decorators, code patches, regeneration, and build as a single atomic workflow.
  • If azure-sdk-mcp:azsdk_customized_code_update fails or times out, report the error to the user and suggest retrying. Do not attempt to replicate its behavior by editing files manually.
  • Only the customization tool understands the correct layering of TypeSpec decorators vs code patches and ensures regenerated code stays consistent.

Examples

  • "Generate the SDK locally for my TypeSpec service"
  • "Build and test the Python SDK package"
  • "Run CI checks for my SDK package"
  • "Fix the SDK build errors on this PR"
  • "Rename FooClient to BarClient for .NET"
  • "Hide the internal polling operation from the Python SDK"
  • "Fix .NET analyzer errors AZC0030 and AZC0012"
  • "The build is failing because a customization references a renamed property"
  • "Create a subclient architecture for the Python SDK"
  • "Apply TypeSpec customizations to fix compilation errors"
  • "Update the changelog for this SDK package"
  • "Update the package version"
  • "Update the package metadata and ci.yml"

Troubleshooting

  • For "generate SDK for all languages", pipeline-based generation, or when no local SDK clone exists, call azure-sdk-mcp:azsdk_run_generate_sdk instead of the local generate flow, and never substitute azure-sdk-mcp:azsdk_get_sdk_pull_request_link / azure-sdk-mcp:azsdk_get_pull_request for generation.
  • Run azure-sdk-mcp:azsdk_verify_setup to confirm MCP and tools.
  • If build fails with type conflicts, breaking changes, analyzer errors, or customization drift, use azure-sdk-mcp:azsdk_customized_code_update to apply customizations.
  • The customization tool uses a two-phase approach: TypeSpec decorators first (Phase A), then code repairs if needed (Phase B).
  • If azure-sdk-mcp:azsdk_customized_code_update fails or times out, report the error and retry. Do not manually edit generated SDK code — manual edits will be overwritten on the next regeneration.
  • Without MCP, use npx tsp-client CLI.

© 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 6 other files (references) in .github/skills/azsdk-common-generate-sdk-locally of Azure/azure-sdk-tools.

  • SKILL.md
  • evals/eval.yaml
  • evals/trigger.eval.yaml
  • fixtures/tspconfig.yaml
  • references/customization-workflow.md
  • references/detailed-workflow.md
  • references/sdk-repos.md

Open the folder on GitHubat commit 942ef24

Compare with similar skills

Azsdk Common Generate SDK Locally 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 Locally compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azsdk Common Generate SDK Locally this skillAzure/azure-sdk-tools134—~2.5kAutomated safety check: PassMIT
Version ReleaseNG-ZORRO/ng-zorro-antd9.2k—~3.1kAutomated safety check: PassMIT
Code ReviewAzure/Azurite2.3k—~734Automated safety check: PassMIT
Add ModelPipelex/pipelex942—~2.8kAutomated safety check: PassCustom licence
Azure App Configuration Release NotesAzure/AppConfiguration263—~3.1kAutomated safety check: PassMIT
Release Noteslangchain-ai/langchain-azure147—~1.2kAutomated safety check: PassMIT

Similar skills

  • Version Release

    NG-ZORRO/ng-zorro-antd

    NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.

    9.2k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Code Review

    Azure/Azurite

    Official

    Review Azurite pull requests with service-aware checks for Blob, Queue, and Table behavior, API compatibility, tests, and release notes.

    2.3k GitHub stars~734 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Add Model

    Pipelex/pipelex

    Add a new AI model to Pipelex's own inference configuration: the backend TOMLs in .pipelex/inference/backends/ (OpenAI, Azure, Anthropic, Bedrock, Google, Vertex, Mistral and the rest), the kit…

    942 GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Azure App Configuration Release Notes

    Azure/AppConfiguration

    Official

    Writes customer-facing release notes for Azure App Configuration libraries and providers in a fixed file layout, version heading and category structure.

    263 GitHub stars~3.1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • Release Notes

    langchain-ai/langchain-azure

    Official

    Skill for compiling and writing release notes for langchain-azure packages.

    147 GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Release

    Azure/agent-app-orchestrator

    Official

    Prepare and reconcile Agent Landing Zone Orchestrator releases, including authoritative version discovery, semantic version selection, release branches, VERSION and CHANGELOG updates, release notes…

    103 GitHub stars~2.5k tokensUpdated 2 days 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 Locally

What does Azsdk Common Generate SDK Locally do?

Generate and finalize Azure SDKs locally from TypeSpec, including build, checks, tests, changelog, metadata, and version updates by default. Azsdk Common Generate SDK Locally is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Generate and finalize Azure SDKs locally from TypeSpec, including build, checks, tests, changelog, metadata, and version updates by default.

When should I use Azsdk Common Generate SDK Locally?

Azsdk Common Generate SDK Locally fits situations like: tasks that involve Changelog and release notes.

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

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

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

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

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

What does Azsdk Common Generate SDK Locally need to run?

Going by SKILL.md and its folder, Azsdk Common Generate SDK Locally needs the command-line tools its instructions call (npx and npm). Our summary lists: Python 3; Node.js. Compatibility (from SKILL.md): azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools.

Does Azsdk Common Generate SDK Locally access the network?

SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

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

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

About 2.5k tokens (SKILL.md is roughly 10k 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 2.9k tokens, read only when the agent opens those files.

What are the alternatives to Azsdk Common Generate SDK Locally?

Skills that share tags, products or a category with Azsdk Common Generate SDK Locally: Version Release (NG-ZORRO/ng-zorro-antd, 9.2k stars), Code Review (Azure/Azurite, 2.3k stars), Add Model (Pipelex/pipelex, 942 stars) and Azure App Configuration Release Notes (Azure/AppConfiguration, 263 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 Locally?

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.