Azure SDK for .NET is a repository containing the actively developed C# libraries that applications use to work with Azure services. It is for .NET developers building software that connects to Azure storage, management, and other cloud services.
Borrowing it
Nothing to install: this file belongs to Azure/azure-sdk-for-net. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Azure/azure-sdk-for-net/main/.github/skills/azsdk-common-pipeline-analysis/SKILL.mdgit clone --depth 1 https://github.com/Azure/azure-sdk-for-netWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/azure/azure-sdk-for-net/azsdk-common-pipeline-analysis)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/azsdk-common-pipeline-analysis"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/azsdk-common-pipeline-analysis/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/azsdk-common-pipeline-analysis"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/azsdk-common-pipeline-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00192 | $0.01071 |
| Opus 5 | $0.00096 | $0.00535 |
| Sonnet 5 | $0.00038 | $0.00214 |
| Haiku 4.5 | $0.00019 | $0.00107 |
Grade A, and why
azsdk-common-pipeline-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- azsdk-common-pipeline-analysis — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 55 lines · 192 tokens per session scan A 24952d56961d
azsdk-common-pipeline-analysis is a skill published in the GitHub repository Azure/azure-sdk-for-net (6,050 stars, last pushed today), licensed MIT. It adds 192 tokens to every session and 1,071 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cosmos-design-struct
Enforce consistent struct design conventions across sdk/cosmos crates. Validates visibility modifiers, field privacy, #[nonexhaustive] usage, and construction API patterns (Default/new with with setters, or optional separate builders with builder()/build()), and construction correctness on public structs. Can auto-fix…
cosmos-pre-commit-validation
Run pre-commit checks for a specific set of crates. Use this when validating changes under sdk/cosmos before committing or during code review.
oss-debug-ci
Debug CI failures in unfamiliar repo pipelines. Reads CI configs, fetches failure logs, classifies the failure type, and guides the user through diagnosing and fixing the issue. Use when CI fails on your PR in an OSS repo, when you don't understand a CI error, or when debugging GitHub Actions/CircleCI/other CI…
diagnosing-azure-deployment-failures
Matches Azure deploy / CI / runtime failures against 37+ documented gotchas with verified fixes (BCP258, AADSTS70021, sqlcmd-not-found, FC1-CLI-silent-fallback, ACS dataLocation quirks, SSE timeouts, and more). Delegates to Microsoft's azure-diagnostics for live log/metric queries. Use when a deploy fails, a deployed…
oh-my-posh
Install, configure, or troubleshoot Oh My Posh/ohmyposh: shell init, themes, segments, Nerd Font icons, and prompt setup on PowerShell, zsh, bash, or fish.
cu-sdk-setup
Guide SDK users through setting up their Java environment for Azure AI Content Understanding. Use this skill when users need help installing the SDK, configuring Azure resources, deploying required models, setting environment variables, or running samples.