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/analyze-ci-failures/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/analyze-ci-failures)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/analyze-ci-failures"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/analyze-ci-failures/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/analyze-ci-failures"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/analyze-ci-failures.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.00049 | $0.01490 |
| Opus 5 | $0.00024 | $0.00745 |
| Sonnet 5 | $0.00010 | $0.00298 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
analyze-ci-failures scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- If that tool is unavailable, query the public Azure DevOps timeline API with `curl`: How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: analyze-ci-failures
Analyze CI failures on an Azure SDK for .NET pull request and post a GitHub comment with actionable fix instructions.
When Invoked
Trigger phrases: "analyze CI failures", "fix CI", "why is CI failing", "help with CI", "analyze PR checks", "CI is red", "failing checks".
Inputs
The user must provide a PR number, PR URL, or pipeline build ID. If not provided, ask the user.
Workflow
1. Gather information
- Fetch PR details, check statuses, changed files, and workflow runs using GitHub MCP tools.
- Extract service directory and package name from changed file paths (
sdk/<service>/<package>/). - Identify the CI provider from each failed check URL before fetching logs:
- For an Azure DevOps URL (
dev.azure.com), extract thebuildId. Useazure-sdk-mcp:azsdk_analyze_pipelinewhen available. - If that tool is unavailable, query the public Azure DevOps timeline API with
curl:https://dev.azure.com/<organization>/<project>/_apis/build/builds/<buildId>/timeline?api-version=7.1. Inspectissueson failed task records first. If the issues are insufficient, fetch the failed record'slog.url. - For a GitHub Actions URL, use
github-mcp-server-get_job_logswithreturn_content: true.
- For an Azure DevOps URL (
- Do not use GitHub Actions job-log tools for Azure DevOps checks; their job IDs and run IDs are unrelated.
2. Identify failures
Classify each failure using the CI check mapping and log symptom patterns below. Also inspect the PR's code directly (e.g., read generated files for compile errors, check for missing scaffolding files).
Diagnosis must be based on the failed task's actual error text:
- Quote the decisive error and name the affected file or project.
- Do not infer the root cause from the check name, because
Build/Packjobs also run changelog verification, package validation, and ApiCompat. - Do not call a failure transient or flaky unless the logs contain infrastructure evidence (for example, an agent disconnect, timeout, service outage, or network failure). A documentation-only last commit does not establish flakiness because packaging validates files such as
CHANGELOG.md. - If logs cannot be retrieved, state that the root cause is unconfirmed and provide the failed task link. Do not substitute a guessed compilation or ApiCompat diagnosis.
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.
- 11d ago First seen · 100 lines · 49 tokens per session scan A f8506fa5c862
analyze-ci-failures is a skill published in the GitHub repository Azure/azure-sdk-for-net (6,050 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 1,490 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.