Azsdk Common Pipeline Troubleshooting

azure/azsdk-common-pipeline-troubleshooting

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.

2k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

122

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-c --skill azsdk-common-pipeline-troubleshooting

What comes with it

6 922 bytes besides the instruction

evals/eval.yaml

evals/trigger.eval.yaml

references/failure-patterns.md

The instruction itself

5 sections, as written by the author

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_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.

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.

How to use it

Copy the folder

Take azure/azsdk-common-pipeline-troubleshooting 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.