Azsdk Common Pipeline Troubleshooting
Azure/azure-sdk-for-android
Diagnose and resolve failures in Azure SDK CI and generation pipelines.
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format.
Install Azsdk Common Pipeline Analysis
$ npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/azure-sdk-tools azsdk-common-pipeline-analysis --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-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-analysis .claude/skills/azsdk-common-pipeline-analysis && 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-analysis" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-analysis into .claude/skills/azsdk-common-pipeline-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-analysis", 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-tools/tree/main/.github/skills/azsdk-common-pipeline-analysisType 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-tools --skill azsdk-common-pipeline-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/azure-sdk-tools azsdk-common-pipeline-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-analysis .agents/skills/azsdk-common-pipeline-analysis && 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-analysis" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-analysis into .agents/skills/azsdk-common-pipeline-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-analysis", 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-tools --skill azsdk-common-pipeline-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/azure-sdk-tools azsdk-common-pipeline-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-analysis .cursor/skills/azsdk-common-pipeline-analysis && 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-analysis" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-analysis into .cursor/skills/azsdk-common-pipeline-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-analysis", 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-tools.git --path .github/skills/azsdk-common-pipeline-analysis--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-tools --skill azsdk-common-pipeline-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/azure-sdk-tools azsdk-common-pipeline-analysis --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-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-analysis .gemini/skills/azsdk-common-pipeline-analysis && 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-analysis" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-analysis into .gemini/skills/azsdk-common-pipeline-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-analysis", 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-tools azsdk-common-pipeline-analysisInstalls 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-tools --skill azsdk-common-pipeline-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-analysis .github/skills/azsdk-common-pipeline-analysis && 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-analysis" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-analysis into .github/skills/azsdk-common-pipeline-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-analysis", 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-tools --skill azsdk-common-pipeline-analysis -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-tools azsdk-common-pipeline-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/azsdk-common-pipeline-analysis .opencode/skills/azsdk-common-pipeline-analysis && 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-analysis" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/.github/skills/azsdk-common-pipeline-analysis into .opencode/skills/azsdk-common-pipeline-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azsdk-common-pipeline-analysis", 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-analysis- GitHub stars
- 134
- Token cost
- ~1.2k tokens
- SKILL.md length
- 415 words
- Files
- 4 (incl. references)
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format.
- Works in 6 steps: Identify - Get the build ID, pipeline… → Analyze - Run azsdk_analyze_pipeline. It… → Fetch failure details - Fetch failure… → …
- : pipeline failed
- SKILL.md covers Rules, MCP Tools, Steps and Examples, plus 1 more section
- Calls az
What it does
Azsdk Common Pipeline Analysis is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in CI", "analyze pipeline", "debug SDK pipeline". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing, applying code fixes (instead use…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `evals/trigger.eval.yaml`, `references/failure-patterns.md` and `references/output-format.md`). Compatibility notes: azure-sdk-mcp server, Azure DevOps pipeline build ID or GitHub PR link
It sits in Testing & QA, covering Test generation, Failing and flaky tests and State management. It works with Microsoft Azure, Model Context Protocol and Azure DevOps. The repository describes itself as: Tools repository leveraged by the Azure SDK team. The licence is MIT.
When your agent uses it
- : pipeline failed
- CI check failing
- Tests failing in CI
- Analyze pipeline
Example prompts
- “pipeline failed”
- “build failure”
- “CI check failing”
- “/azsdk-common-pipeline-analysis”
Requirements
- Compatibility (from SKILL.md): azure-sdk-mcp server, Azure DevOps pipeline build ID or GitHub PR link
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Identify - Get the build ID, pipeline URL, or PR link (use the PR link when triggered from a PR comment).
- Analyze - Run azsdk_analyze_pipeline. It returns failed_pipeline_tasks (log errors from failed steps) and failed_pipeline_tests, a…
- Fetch failure details - Fetch failure details lazily so you don't overload context: call azsdk_get_failed_test_run_data with the parameter…
- Categorize each failure: test, build/compilation, validation/lint, or infrastructure.
- Diagnose - Give each failure's root cause and affected file(s)/line(s), and note if several share one root cause. See failure patterns.
- Report - Use the output format: root cause, affected files, per-failure fix + verify command, and fixable vs infrastructure. Recommend…
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:
az
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use az, 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, Azure DevOps pipeline build ID or GitHub PR link
From compatibility in the SKILL.md frontmatter.
Context cost
Azsdk Common Pipeline Analysis loads about 1.2k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 205 tokens; SKILL.md has 415 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-tools at commit 942ef24, republished under its MIT licence (© Azure). 415 words, ~1,183 tokens.
Download SKILL.mdSave it as
.claude/skills/azsdk-common-pipeline-analysis/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-analysis
- description
- Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdk_analyze_pipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in CI", "analyze pipeline", "debug SDK pipeline". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing, applying code fixes (instead use azsdk-common-pipeline-fixer). INVOKES: azure-sdk-mcp:azsdk_analyze_pipeline, azure-sdk-mcp:azsdk_get_pipeline_llm_artifacts, azure-sdk-mcp:azsdk_get_failed_test_run_data, azure-sdk-mcp:azsdk_get_failed_test_case_data, azure-sdk-mcp:azsdk_get_pr_checks, azure-sdk-mcp:azsdk_get_pipeline_status.
- compatibility
- azure-sdk-mcp server, Azure DevOps pipeline build ID or GitHub PR link
- license
- MIT
- metadata.version
- 1.0.0
- metadata.distribution
- shared
Pipeline Analysis
This skill analyzes Azure SDK CI/CD pipeline failures and provides a structured diagnosis including root cause, affected files, and concrete instructions for how to fix each issue. It does NOT apply fixes - it tells you exactly what's wrong and how to resolve it.
Rules
- Load this skill before running
azsdk_analyze_pipeline— the tool returns raw failure data that this skill interprets and formats per output format. - Requires the
azure-sdk-mcpserver; without it, inspect logs in the Azure DevOps UI. - Analysis-only: never edit files or apply fixes — use
azsdk-common-pipeline-fixerfor changes. - Run
azsdk_analyze_pipelinefirst, then categorize each failure and cite specific files/lines. - For infrastructure failures (network timeouts, agent crashes, throttling), recommend retry, not code changes.
MCP Tools
| Tool | Purpose |
|---|---|
azure-sdk-mcp:azsdk_analyze_pipeline | Analyze pipeline failure (logs + test results) |
azure-sdk-mcp:azsdk_get_pipeline_llm_artifacts | Download test result artifacts from pipeline |
azure-sdk-mcp:azsdk_get_failed_test_run_data | Full details for every failure in one artifact file |
azure-sdk-mcp:azsdk_get_failed_test_case_data | Full details for a single failing test in a file |
azure-sdk-mcp:azsdk_get_pr_checks | Get pipeline/check results linked to a PR |
azure-sdk-mcp:azsdk_get_pipeline_status | Get pipeline run status |
Steps
- Identify - Get the build ID, pipeline URL, or PR link (use the PR link when triggered from a PR comment).
- Analyze - Run
azsdk_analyze_pipeline. It returnsfailed_pipeline_tasks(log errors from failed steps) andfailed_pipeline_tests, a lightweight index of failed tests grouped by artifact file. Each entry hasartifact_file_path,platform, andfailed_test_titles— titles only, no error text, to keep the response small. - Fetch failure details - Fetch failure details lazily so you don't overload context: call
azsdk_get_failed_test_run_datawith the parameterfailedTestRunsPathset toartifact_file_pathonce per file to get every failure in it. Or callazsdk_get_failed_test_case_datawithfailedTestRunsPathset toartifact_file_pathandtestCaseTitleset to one exact title fromfailed_test_titles. Prefer the per-file call when triaging a whole file's failures. - Categorize each failure: test, build/compilation, validation/lint, or infrastructure.
- Diagnose - Give each failure's root cause and affected file(s)/line(s), and note if several share one root cause. See failure patterns.
- Report - Use the output format: root cause, affected files, per-failure fix + verify command, and fixable vs infrastructure. Recommend
azsdk-common-pipeline-fixerto apply fixes.
Show full SKILL.md (74 more words)Show less
Examples
- "My pipeline build 6447834 failed, what went wrong?"
- PR comment:
@copilot Analyze the failed pipeline on this PR - "Why is my CI red? Build ID is 6455939"
Troubleshooting
- If
azsdk_analyze_pipelinereturns no data, verify the build ID is correct and the run has completed. - If
failed_pipeline_testsis empty, rely onfailed_pipeline_taskslog analysis (test-artifact upload may not be configured). - For a private/internal pipeline, the user may need to
az login. See failure patterns.
© 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-analysis of Azure/azure-sdk-tools.
- SKILL.md
- evals/trigger.eval.yaml
- references/failure-patterns.md
- references/output-format.md
Open the folder on GitHubat commit 942ef24
Compare with similar skills
Azsdk Common Pipeline Analysis 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 Analysis this skillAzure/azure-sdk-tools | 134 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Azsdk Common Pipeline TroubleshootingAzure/azure-sdk-for-android | 121 | — | ~496 | Automated safety check: Pass | MIT | |
| Ue Test AuthoringJasonMa0012/MooaToon | 750 | — | ~2.1k | Automated safety check: Notes | Custom licence | |
| Opik Verifycomet-ml/opik-mcp | 220 | — | ~2.8k | Automated safety check: Notes | Apache-2.0 | |
| Azure App TestingMicrosoftDocs/Agent-Skills | 776 | — | ~3.6k | Automated safety check: Pass | CC-BY-4.0 | |
| Analyze Skill Issuesmicrosoft/GitHub-Copilot-for-Azure | 255 | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Ue Test Authoring
JasonMa0012/MooaToon
A skill your agent uses when writing or modifying UE automated tests (Automation, CQTest, Functional, Gauntlet, LowLevel) with Rider MCP available.
Opik Verify
comet-ml/opik-mcp
Decide ship or hold for a candidate from the compare skill's numbers, against an explicit release policy — regressions, pass rate, safety-tagged cases, subgroup consistency, latency and cost…
- Official
Azure App Testing
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure App Testing development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations…
- Official
Analyze Skill Issues
microsoft/GitHub-Copilot-for-Azure
Query the integration-test storage account to find why a specific skill's tests are failing.
Model Download Dev
open-edge-platform/edge-ai-libraries
Extend, test, debug, or integrate the Model Download microservice codebase.
More from Azure/azure-sdk-tools
All 35 skills in this repo- Official
Apiview Feedback Resolution
Azure/azure-sdk-tools
Analyze and resolve APIView review feedback on Azure SDK PRs.
- Official
Azsdk Common Apiview Feedback Resolution
Azure/azure-sdk-tools
Analyze and resolve APIView review feedback on Azure SDK PRs.
- Official
Azsdk Common Live And Recorded Tests
Azure/azure-sdk-tools
Deploy test resources and run Azure SDK tests in live, record, or playback mode.
- Official
Azsdk Common Prepare Release Plan
Azure/azure-sdk-tools
Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases.
- Official
Azure Typespec Assessment
Azure/azure-sdk-tools
Assess Azure TypeSpec Git diffs for semantic intent, REST and downstream SDK breaking changes, Azure Guidelines compliance, and documentation completeness.
- Official
Azure Typespec Author
Azure/azure-sdk-tools
Authors and modifies Azure TypeSpec (.tsp) API specifications.
Related
Categories
Questions about Azsdk Common Pipeline Analysis
What does Azsdk Common Pipeline Analysis do?
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Azsdk Common Pipeline Analysis is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format.
When should I use Azsdk Common Pipeline Analysis?
Azsdk Common Pipeline Analysis fits situations like: : pipeline failed; CI check failing; tests failing in CI; analyze pipeline.
How do I install Azsdk Common Pipeline Analysis in Claude Code?
Run `npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-analysis -a claude-code`. Or copy the skill folder (.github/skills/azsdk-common-pipeline-analysis in Azure/azure-sdk-tools) into .claude/skills/azsdk-common-pipeline-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Azsdk Common Pipeline Analysis in Codex?
Run `npx skills add Azure/azure-sdk-tools --skill azsdk-common-pipeline-analysis -a codex`. Or copy the skill folder (.github/skills/azsdk-common-pipeline-analysis in Azure/azure-sdk-tools) into .agents/skills/azsdk-common-pipeline-analysis in your project. Codex loads it when a task matches its description.
Can I use Azsdk Common Pipeline Analysis 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-pipeline-analysis -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-analysis, .gemini/skills/azsdk-common-pipeline-analysis, .github/skills/azsdk-common-pipeline-analysis and .opencode/skills/azsdk-common-pipeline-analysis in your project.
What does Azsdk Common Pipeline Analysis need to run?
Going by SKILL.md and its folder, Azsdk Common Pipeline Analysis needs the command-line tools its instructions call (az). Compatibility (from SKILL.md): azure-sdk-mcp server, Azure DevOps pipeline build ID or GitHub PR link.
Does Azsdk Common Pipeline Analysis 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 Analysis 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 Analysis use?
Azsdk Common Pipeline Analysis 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 Analysis use?
About 1.2k tokens (SKILL.md is roughly 4.7k 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 1.9k tokens, read only when the agent opens those files.
What are the alternatives to Azsdk Common Pipeline Analysis?
Skills that share tags, products or a category with Azsdk Common Pipeline Analysis: Azsdk Common Pipeline Troubleshooting (Azure/azure-sdk-for-android, 121 stars), Ue Test Authoring (JasonMa0012/MooaToon, 750 stars), Opik Verify (comet-ml/opik-mcp, 220 stars) and Azure App Testing (MicrosoftDocs/Agent-Skills, 776 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 Analysis?
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.