Azsdk Common Pipeline Analysis Agent Skill

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_pr_checks, azure-sdk-mcp:azsdk_get_pipeline_status.

4k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

136

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Azure/azure-sdk-for-net --skill azsdk-common-pipeline-analysis

What comes with it

10 923 bytes besides the instruction

evals/trigger.eval.yaml

references/failure-patterns.md

references/output-format.md

The instruction itself

6 sections, as written by the author

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-mcp server; without it, inspect logs in the Azure DevOps UI.
Analysis-only: never edit files or apply fixes — use azsdk-common-pipeline-fixer for changes.
Run azsdk_analyze_pipeline first, 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_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 returns failed_tasks (log errors from failed steps) and failed_test_titles (failed tests grouped by file).
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-fixer to apply fixes.

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_pipeline returns no data, verify the build ID is correct and the run has completed.
If failed_test_titles is empty, rely on failed_tasks log analysis (test-artifact upload may not be configured).
For a private/internal pipeline, the user may need to az login. See failure patterns.

Other skills for the same job

different authors, same section of the catalogue

Azure Kubernetes Automatic Readiness

by microsoft

vendor ×3

Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.

Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.

Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).

Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).

Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).

This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.

Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.

Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.

17k tokens

How to use it

Copy the folder

Take azure/azsdk-common-pipeline-analysis from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.