Azsdk Common Pipeline Fixer
Azure/azure-sdk-tools
Automatically fix Azure SDK CI/CD pipeline failures by applying code changes and verifying locally.
Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization.
Install Azsdk Common Generate SDK Locally
$ npx skills add Azure/azure-sdk-for-android --skill azsdk-common-generate-sdk-locally -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-generate-sdk-locally --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-for-android.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-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-generate-sdk-locally" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-generate-sdk-locally into .claude/skills/azsdk-common-generate-sdk-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-generate-sdk-locally", 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-for-android/tree/main/.github/skills/azsdk-common-generate-sdk-locallyType 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-for-android --skill azsdk-common-generate-sdk-locally -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-generate-sdk-locally --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-for-android.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/azsdk-common-generate-sdk-locally .agents/skills/azsdk-common-generate-sdk-locally && 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-generate-sdk-locally" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-generate-sdk-locally into .agents/skills/azsdk-common-generate-sdk-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-generate-sdk-locally", 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-for-android --skill azsdk-common-generate-sdk-locally -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-generate-sdk-locally --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-for-android.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/azsdk-common-generate-sdk-locally .cursor/skills/azsdk-common-generate-sdk-locally && 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-generate-sdk-locally" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-generate-sdk-locally into .cursor/skills/azsdk-common-generate-sdk-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-generate-sdk-locally", 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-for-android.git --path .github/skills/azsdk-common-generate-sdk-locally--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-for-android --skill azsdk-common-generate-sdk-locally -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-generate-sdk-locally --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-for-android.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/azsdk-common-generate-sdk-locally .gemini/skills/azsdk-common-generate-sdk-locally && 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-generate-sdk-locally" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-generate-sdk-locally into .gemini/skills/azsdk-common-generate-sdk-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-generate-sdk-locally", 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-for-android azsdk-common-generate-sdk-locallyInstalls 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-for-android --skill azsdk-common-generate-sdk-locally -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-for-android.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/azsdk-common-generate-sdk-locally .github/skills/azsdk-common-generate-sdk-locally && 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-generate-sdk-locally" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-generate-sdk-locally into .github/skills/azsdk-common-generate-sdk-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-generate-sdk-locally", 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-for-android --skill azsdk-common-generate-sdk-locally -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-for-android azsdk-common-generate-sdk-locally --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-for-android.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/azsdk-common-generate-sdk-locally .opencode/skills/azsdk-common-generate-sdk-locally && 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-generate-sdk-locally" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-generate-sdk-locally into .opencode/skills/azsdk-common-generate-sdk-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-generate-sdk-locally", 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-generate-sdk-locally- GitHub stars
- 121
- Token cost
- ~1.5k tokens
- SKILL.md length
- 528 words
- Files
- 6 (incl. references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization.
- Works in 11 steps: Select language — Confirm target… → Verify repo — Ensure the user has a… → Identify config file — Determine the… → …
- : publishing to package registries
- SKILL.md covers MCP Tools, Steps, Guardrails and Examples, plus 1 more section
- Calls npx
What it does
Azsdk Common Generate SDK Locally is an agent skill from Azure/azure-sdk-for-android, published by the product's own GitHub organization. Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization. WHEN: "generate SDK locally", "build SDK", "run SDK tests", "run CI checks", "validate package", "run checks", "update changelog", "fix SDK build errors", "fix breaking changes", "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". DO NOT USE FOR…
Its SKILL.md is about 1.5k 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`, `fixtures/tspconfig.yaml` and `references/customization-workflow.md`). Compatibility notes: azure-sdk-mcp server, local azure-sdk-for-{language} clone, language build tools
It sits in Backend & APIs, covering Changelog and release notes, API design and CI/CD. It works with Microsoft Azure, Model Context Protocol and Java. The repository describes itself as: Android client SDKs for Microsoft Azure. The licence is MIT.
When your agent uses it
- : publishing to package registries
- CI pipeline configuration
- API design review
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.
- Select language — Confirm target language: .NET, Java, JavaScript, Python, Go, or Rust.
- Verify repo — Ensure the user has a local clone of the correct SDK repo. If not cloned, instruct user to clone it.
- Identify config file — Determine the path to the TypeSpec configuration file. See config file details.
- Verify setup — Run azure-sdk-mcp:azsdk_verify_setup to confirm environment.
- Generate — Run azure-sdk-mcp:azsdk_package_generate_code with the config file path.
- Build — Run azure-sdk-mcp:azsdk_package_build_code. If build succeeds, proceed to step 8.
- Customize — If build fails, or if user requests SDK modifications, run azure-sdk-mcp:azsdk_customized_code_update with the build errors or…
- Commit checkpoint — Prompt the user to commit generated changes before proceeding. See commit checkpoint details.
- Validate — Run azure-sdk-mcp:azsdk_package_run_check and azure-sdk-mcp:azsdk_package_run_tests.
- Metadata — Run azure-sdk-mcp:azsdk_package_update_changelog_content, azure-sdk-mcp:azsdk_package_update_metadata, and…
- 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 0ff8a7b. 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
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, 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 1.5k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 224 tokens; SKILL.md has 528 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-for-android at commit 0ff8a7b, republished under its MIT licence (© Azure). 528 words, ~1,501 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 5 other files; get the full folder from GitHub.- name
- azsdk-common-generate-sdk-locally
- description
- Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization. WHEN: "generate SDK locally", "build SDK", "run SDK tests", "run CI checks", "validate package", "run checks", "update changelog", "fix SDK build errors", "fix breaking changes", "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". DO NOT USE FOR: publishing to package registries, CI pipeline configuration, API design review. 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.0
- metadata.distribution
- shared
Generate SDK Locally
MCP Tools
| Tool | Purpose |
|---|---|
azure-sdk-mcp:azsdk_verify_setup | Verify environment |
azure-sdk-mcp:azsdk_package_generate_code | Generate SDK |
azure-sdk-mcp:azsdk_package_build_code | Build package |
azure-sdk-mcp:azsdk_package_run_check | Validate package |
azure-sdk-mcp:azsdk_package_run_tests | Run tests |
azure-sdk-mcp:azsdk_customized_code_update | Apply customizations (includes regeneration and build) |
azure-sdk-mcp:azsdk_package_update_changelog_content | Update changelog |
azure-sdk-mcp:azsdk_package_update_metadata | Update metadata including ci.yml |
azure-sdk-mcp:azsdk_package_update_version | Update version |
Prerequisites: azure-sdk-mcp server must be running. Without MCP, use npx tsp-client CLI.
Steps
- Select language — Confirm target language: .NET, Java, JavaScript, Python, Go, or Rust.
- Verify repo — Ensure the user has a local clone of the correct SDK repo. If not cloned, instruct user to clone it.
- Identify config file — Determine the path to the TypeSpec configuration file. See config file details.
- From
azure-rest-api-specsrepo: use path totspconfig.yaml. - From an SDK language repo: use path to
tsp-location.yaml.
- From
- Verify setup — Run
azure-sdk-mcp:azsdk_verify_setupto confirm environment. - Generate — Run
azure-sdk-mcp:azsdk_package_generate_codewith the config file path. - Build — Run
azure-sdk-mcp:azsdk_package_build_code. If build succeeds, proceed to step 8. - Customize — If build fails, or if user requests SDK modifications, run
azure-sdk-mcp:azsdk_customized_code_updatewith 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. - Commit checkpoint — Prompt the user to commit generated changes before proceeding. See commit checkpoint details.
- Validate — Run
azure-sdk-mcp:azsdk_package_run_checkandazure-sdk-mcp:azsdk_package_run_tests. - Metadata — Run
azure-sdk-mcp:azsdk_package_update_changelog_content,azure-sdk-mcp:azsdk_package_update_metadata, andazure-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.) - 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_updatefails 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.
Show full SKILL.md (182 more words)Show less
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"
- "The SDK generation has breaking changes, resolve them"
- "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
- Run
azure-sdk-mcp:azsdk_verify_setupto confirm MCP and tools. - If build fails with type conflicts, breaking changes, analyzer errors, or customization drift, use
azure-sdk-mcp:azsdk_customized_code_updateto 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_updatefails 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-clientCLI.
© 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-generate-sdk-locally of Azure/azure-sdk-for-android.
- SKILL.md
- evals/eval.yaml
- fixtures/tspconfig.yaml
- references/customization-workflow.md
- references/detailed-workflow.md
- references/sdk-repos.md
Open the folder on GitHubat commit 0ff8a7b
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in Azure/azure-sdk-for-android, which our catalogue first saw on October 7, 2026.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Azsdk Common Generate SDK Locally this skillAzure/azure-sdk-for-android | 121 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Azsdk Common Pipeline FixerAzure/azure-sdk-tools | 134 | — | ~831 | Automated safety check: Pass | MIT | |
| Goinference-gateway/inference-gateway | 214 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Releasing Blancbnfy/blanc | 115 | — | ~2.9k | Automated safety check: Notes | MIT | |
| Engineering Advanced Skillsalirezarezvani/claude-skills | 28k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Release Coherencemacalbert/envilder | 138 | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Go
inference-gateway/inference-gateway
Idiomatic Go - package and interface design, error wrapping, table-driven tests, generics, the modern standard library (slices/maps/cmp/errors.Join), current syntax, and logging discipline.
Releasing Blanc
bnfy/blanc
Full runbook for cutting a Blanc desktop release — scripts/release.sh mechanics and its required BLANCRELEASE env vars, macOS notarization via 1Password, the Touch ID provisioning profile and…
Engineering Advanced Skills
alirezarezvani/claude-skills
Index of 37 advanced engineering agent skills for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw.
Release Coherence
macalbert/envilder
Unified release coherence workflow for any component (CLI, GHA, or SDK).
Agentbro Release
shirenchuang/agentbro
A skill your agent uses when releasing AgentBro from this repository: merging dev/main, bumping versions, updating release notes, tagging, pushing, monitoring GitHub Actions, Homebrew cask…
More from Azure/azure-sdk-for-android
- Official
Azsdk Common Apiview Feedback Resolution
Azure/azure-sdk-for-android
Analyze and resolve APIView review feedback on Azure SDK PRs.
- Official
Azsdk Common Prepare Release Plan
Azure/azure-sdk-for-android
Create and manage release plan work items for Azure SDK releases across languages.
- Official
Azsdk Common Pipeline Troubleshooting
Azure/azure-sdk-for-android
Diagnose and resolve failures in Azure SDK CI and generation pipelines.
- Official
Azsdk Common SDK Release
Azure/azure-sdk-for-android
Check release readiness and trigger the release pipeline for Azure SDK packages.
Related
Categories
Questions about Azsdk Common Generate SDK Locally
What does Azsdk Common Generate SDK Locally do?
Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization. Azsdk Common Generate SDK Locally is an agent skill from Azure/azure-sdk-for-android, published by the product's own GitHub organization. Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization.
When should I use Azsdk Common Generate SDK Locally?
Azsdk Common Generate SDK Locally fits situations like: : publishing to package registries; CI pipeline configuration; API design review.
How do I install Azsdk Common Generate SDK Locally in Claude Code?
Run `npx skills add Azure/azure-sdk-for-android --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-for-android) 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-for-android --skill azsdk-common-generate-sdk-locally -a codex`. Or copy the skill folder (.github/skills/azsdk-common-generate-sdk-locally in Azure/azure-sdk-for-android) 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-for-android --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). 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, 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 1.5k tokens (SKILL.md is roughly 6k 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.2k 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: Azsdk Common Pipeline Fixer (Azure/azure-sdk-tools, 134 stars), Go (inference-gateway/inference-gateway, 214 stars), Releasing Blanc (bnfy/blanc, 115 stars) and Engineering Advanced Skills (alirezarezvani/claude-skills, 28k 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-for-android, which has 121 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on June 7, 2026.
Source: Azure/azure-sdk-for-android on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.