Azsdk Common Pipeline Analysis
Azure/azure-sdk-tools
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format.
Diagnose and resolve failures in Azure SDK CI and generation pipelines.
Install Azsdk Common Pipeline Troubleshooting
$ npx skills add Azure/azure-sdk-for-android --skill azsdk-common-pipeline-troubleshooting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-pipeline-troubleshooting --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-pipeline-troubleshooting .claude/skills/azsdk-common-pipeline-troubleshooting && 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-pipeline-troubleshooting" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-pipeline-troubleshooting into .claude/skills/azsdk-common-pipeline-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-troubleshooting", 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-pipeline-troubleshootingType 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-pipeline-troubleshooting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-pipeline-troubleshooting --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-pipeline-troubleshooting .agents/skills/azsdk-common-pipeline-troubleshooting && 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-pipeline-troubleshooting" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-pipeline-troubleshooting into .agents/skills/azsdk-common-pipeline-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-troubleshooting", 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-pipeline-troubleshooting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-pipeline-troubleshooting --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-pipeline-troubleshooting .cursor/skills/azsdk-common-pipeline-troubleshooting && 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-pipeline-troubleshooting" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-pipeline-troubleshooting into .cursor/skills/azsdk-common-pipeline-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-troubleshooting", 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-pipeline-troubleshooting--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-pipeline-troubleshooting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/azure-sdk-for-android azsdk-common-pipeline-troubleshooting --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-pipeline-troubleshooting .gemini/skills/azsdk-common-pipeline-troubleshooting && 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-pipeline-troubleshooting" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-pipeline-troubleshooting into .gemini/skills/azsdk-common-pipeline-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-troubleshooting", 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-pipeline-troubleshootingInstalls 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-pipeline-troubleshooting -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-pipeline-troubleshooting .github/skills/azsdk-common-pipeline-troubleshooting && 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-pipeline-troubleshooting" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-pipeline-troubleshooting into .github/skills/azsdk-common-pipeline-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-troubleshooting", 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-pipeline-troubleshooting -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-pipeline-troubleshooting --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-pipeline-troubleshooting .opencode/skills/azsdk-common-pipeline-troubleshooting && 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-pipeline-troubleshooting" agent skill from https://github.com/Azure/azure-sdk-for-android/tree/main/.github/skills/azsdk-common-pipeline-troubleshooting into .opencode/skills/azsdk-common-pipeline-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-troubleshooting", 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-pipeline-troubleshooting- GitHub stars
- 121
- Token cost
- ~496 tokens
- SKILL.md length
- 116 words
- Files
- 4 (incl. references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnose and resolve failures in Azure SDK CI and generation pipelines.
- Works in 5 steps: Identify — Get build ID, run… → Analyze — See failure patterns for… → Reproduce — Verify setup, then run… → …
- : pipeline failed
- 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 Pipeline Troubleshooting is an agent skill from Azure/azure-sdk-for-android, published by the product's own GitHub organization. Diagnose and resolve failures in Azure SDK CI and generation pipelines. UTILITY SKILL. USE FOR: "pipeline failed", "build failure", "CI check failing", "SDK generation error", "reproduce pipeline locally", "debug SDK pipeline". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing. INVOKES: azure-sdk-mcp:azsdkanalyzepipeline, azure-sdk-mcp:azsdkpackagebuildcode, azure-sdk-mcp:azsdkpackageruncheck.
Its SKILL.md is about 500 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `evals/eval.yaml`, `evals/trigger.eval.yaml` and `references/failure-patterns.md`). Compatibility notes: azure-sdk-mcp server, Azure DevOps pipeline build ID
It sits in Agent Workflows, covering MCP servers, State management and Design review and critique. It works with Microsoft Azure, Model Context Protocol and Azure DevOps. The repository describes itself as: Android client SDKs for Microsoft Azure. The licence is MIT.
When your agent uses it
- : pipeline failed
- CI check failing
- SDK generation error
- Reproduce pipeline locally
Example prompts
- “pipeline failed”
- “build failure”
- “CI check failing”
- “/azsdk-common-pipeline-troubleshooting”
Requirements
- Compatibility (from SKILL.md): azure-sdk-mcp server, Azure DevOps pipeline build ID
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Identify — Get build ID, run azure-sdk-mcp:azsdk_analyze_pipeline. Categorize failure.
- Analyze — See failure patterns for common causes.
- Reproduce — Verify setup, then run azure-sdk-mcp:azsdk_package_build_code or azure-sdk-mcp:azsdk_package_run_check.
- Fix — Apply fixes for code or TypeSpec issues.
- Verify — Confirm fix locally, push, monitor re-run.
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
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, Azure DevOps pipeline build ID
From compatibility in the SKILL.md frontmatter.
Context cost
Azsdk Common Pipeline Troubleshooting loads about 496 tokens when it runs, and up to ~913 if it reads all its reference files. Until then it costs about 123 tokens; SKILL.md has 116 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). 116 words, ~496 tokens.
Download SKILL.mdSave it as
.claude/skills/azsdk-common-pipeline-troubleshooting/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- azsdk-common-pipeline-troubleshooting
- description
- Diagnose and resolve failures in Azure SDK CI and generation pipelines. **UTILITY SKILL**. USE FOR: "pipeline failed", "build failure", "CI check failing", "SDK generation error", "reproduce pipeline locally", "debug SDK pipeline". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing. INVOKES: azure-sdk-mcp:azsdk_analyze_pipeline, azure-sdk-mcp:azsdk_package_build_code, azure-sdk-mcp:azsdk_package_run_check.
- compatibility
- azure-sdk-mcp server, Azure DevOps pipeline build ID
- license
- MIT
- metadata.version
- 1.0.0
- metadata.distribution
- shared
Pipeline Troubleshooting
MCP Tools
| Tool | Purpose |
|---|---|
azure-sdk-mcp:azsdk_analyze_pipeline | Analyze pipeline failure |
azure-sdk-mcp:azsdk_verify_setup | Verify local environment |
azure-sdk-mcp:azsdk_package_build_code | Reproduce build locally |
azure-sdk-mcp:azsdk_package_run_check | Run validation checks |
azure-sdk-mcp:azsdk_package_pack | Create SDK packages |
Prerequisites: azure-sdk-mcp server required. Without MCP, view pipeline logs in Azure DevOps UI.
Steps
- Identify — Get build ID, run
azure-sdk-mcp:azsdk_analyze_pipeline. Categorize failure. - Analyze — See failure patterns for common causes.
- Reproduce — Verify setup, then run
azure-sdk-mcp:azsdk_package_build_codeorazure-sdk-mcp:azsdk_package_run_check. - Fix — Apply fixes for code or TypeSpec issues.
- Verify — Confirm fix locally, push, monitor re-run.
Examples
- "My pipeline build 12345 failed, help debug it"
- "Reproduce CI failure locally"
Troubleshooting
If azure-sdk-mcp:azsdk_analyze_pipeline returns no data, verify build ID and MCP. Without MCP, check pipeline logs in Azure DevOps UI.
© 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 (references) in .github/skills/azsdk-common-pipeline-troubleshooting of Azure/azure-sdk-for-android.
- SKILL.md
- evals/eval.yaml
- evals/trigger.eval.yaml
- references/failure-patterns.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 Pipeline Troubleshooting 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 Pipeline Troubleshooting this skillAzure/azure-sdk-for-android | 121 | — | ~496 | Automated safety check: Pass | MIT | |
| Azsdk Common Pipeline AnalysisAzure/azure-sdk-tools | 134 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Autodesignsalitronic/eda-agent | 244 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Building Python MCP Serverskajisho5/ffmpeg-skill | 1.9k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Azure Resource Lookupmicrosoft/GitHub-Copilot-for-Azure | 255 | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Azure Typespec AuthorAzure/azure-sdk-tools | 134 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Autodesign
salitronic/eda-agent
Drive an autonomous spec-to-board PCB design with the eda-agent MCP server (Altium Designer or EasyEDA Pro).
Building Python MCP Servers
kajisho5/ffmpeg-skill
Builds robust Python MCP (Model Context Protocol) servers with FastMCP — tool design, error contracts, event-loop-safe blocking work, subprocess/CLI wrapping, single-file vs packaged distribution…
- Official
Azure Resource Lookup
microsoft/GitHub-Copilot-for-Azure
List, find, and show Azure resources across subscriptions or resource groups.
- Official
Azure Typespec Author
Azure/azure-sdk-tools
Authors and modifies Azure TypeSpec (.tsp) API specifications.
- Official
Azure Typespec Author
Azure/azure-sdk-tools
Authors and modifies Azure TypeSpec (.tsp) API specifications.
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 Generate SDK Locally
Azure/azure-sdk-for-android
Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization.
- 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 SDK Release
Azure/azure-sdk-for-android
Check release readiness and trigger the release pipeline for Azure SDK packages.
Related
Questions about Azsdk Common Pipeline Troubleshooting
What does Azsdk Common Pipeline Troubleshooting do?
Diagnose and resolve failures in Azure SDK CI and generation pipelines. Azsdk Common Pipeline Troubleshooting is an agent skill from Azure/azure-sdk-for-android, published by the product's own GitHub organization. Diagnose and resolve failures in Azure SDK CI and generation pipelines.
When should I use Azsdk Common Pipeline Troubleshooting?
Azsdk Common Pipeline Troubleshooting fits situations like: : pipeline failed; CI check failing; SDK generation error; reproduce pipeline locally.
How do I install Azsdk Common Pipeline Troubleshooting in Claude Code?
Run `npx skills add Azure/azure-sdk-for-android --skill azsdk-common-pipeline-troubleshooting -a claude-code`. Or copy the skill folder (.github/skills/azsdk-common-pipeline-troubleshooting in Azure/azure-sdk-for-android) into .claude/skills/azsdk-common-pipeline-troubleshooting in your project. Claude Code loads it when a task matches its description.
How do I install Azsdk Common Pipeline Troubleshooting in Codex?
Run `npx skills add Azure/azure-sdk-for-android --skill azsdk-common-pipeline-troubleshooting -a codex`. Or copy the skill folder (.github/skills/azsdk-common-pipeline-troubleshooting in Azure/azure-sdk-for-android) into .agents/skills/azsdk-common-pipeline-troubleshooting in your project. Codex loads it when a task matches its description.
Can I use Azsdk Common Pipeline Troubleshooting 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-pipeline-troubleshooting -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-pipeline-troubleshooting, .gemini/skills/azsdk-common-pipeline-troubleshooting, .github/skills/azsdk-common-pipeline-troubleshooting and .opencode/skills/azsdk-common-pipeline-troubleshooting in your project.
What does Azsdk Common Pipeline Troubleshooting need to run?
SKILL.md names no scripts, command-line tools or credentials: Azsdk Common Pipeline Troubleshooting is instructions for the agent only. Compatibility (from SKILL.md): azure-sdk-mcp server, Azure DevOps pipeline build ID.
Does Azsdk Common Pipeline Troubleshooting 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 Pipeline Troubleshooting 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 Pipeline Troubleshooting use?
Azsdk Common Pipeline Troubleshooting 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 Pipeline Troubleshooting use?
About 496 tokens (SKILL.md is roughly 2k 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 417 tokens, read only when the agent opens those files.
What are the alternatives to Azsdk Common Pipeline Troubleshooting?
Skills that share tags, products or a category with Azsdk Common Pipeline Troubleshooting: Azsdk Common Pipeline Analysis (Azure/azure-sdk-tools, 134 stars), Autodesign (salitronic/eda-agent, 244 stars), Building Python MCP Servers (kajisho5/ffmpeg-skill, 1.9k stars) and Azure Resource Lookup (microsoft/GitHub-Copilot-for-Azure, 255 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Azsdk Common Pipeline Troubleshooting?
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.