New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Macios CI Failure Inspector

by dotnet in dotnet/macios

Investigate and triage CI failures for dotnet/macios from Azure DevOps build URLs.

OfficialCustom licenceAuto-check passedTesting & QA

Install Macios CI Failure Inspector

skills CLI
$ npx skills add dotnet/macios --skill macios-ci-failure-inspector -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dotnet/macios macios-ci-failure-inspector --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dotnet/macios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/macios-ci-failure-inspector .claude/skills/macios-ci-failure-inspector && rm -rf skills-src

Use ~/.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/

Facts

Skill name
macios-ci-failure-inspector
GitHub stars
2.9k
Token cost
~2.3k tokens
SKILL.md length
616 words
Files
2 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
Custom licence

At a glance

Investigate and triage CI failures for dotnet/macios from Azure DevOps build URLs.

  • Works in 6 steps: Build overview → Timeline — identify failing jobs and tasks → Download TestSummary artifacts (primary… → …
  • The user shares a DevOps build link
  • SKILL.md covers References, Inputs, Investigation workflow and Troubleshooting the…
  • Calls az; reaches devdiv.visualstudio.com

What it does

Macios CI Failure Inspector is an agent skill from dotnet/macios, published by the product's own GitHub organization. Investigate and triage CI failures for dotnet/macios from Azure DevOps build URLs. Use this skill whenever the user shares a DevOps build link, asks about CI failures, wants to understand why a build failed, or asks to investigate test failures on any platform (iOS, tvOS, macOS, Mac Catalyst). Also use when the user says things like "CI is red", "tests are failing", "build broke", or "what happened in CI".

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/azure-devops-cli.md`).

It sits in Testing & QA, covering Failing and flaky tests. It works with .NET, iOS, macOS and Azure DevOps. The repository describes itself as: .NET for iOS, Mac Catalyst, macOS, and tvOS provide open-source bindings of the Apple SDKs for use with .NET managed languages such as C.

When your agent uses it

  • The user shares a DevOps build link
  • Asks about CI failures
  • Wants to understand why a build failed
  • Asks to investigate test failures on any platform (iOS

Example prompts

  • “CI is red”
  • “tests are failing”
  • “build broke”
  • “/macios-ci-failure-inspector”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Build overview
  2. Timeline — identify failing jobs and tasks
  3. Download TestSummary artifacts (primary failure source)
  4. Get detailed test failure info from HtmlReport artifacts
  5. Extract build error details from raw logs (for BuildFailure cases)
  6. Categorize and report

What it can do on your machine

Read from SKILL.md and the folder at commit 354c2a6. 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

    Hosts in commands or code, which the agent is likely to contact:

    • devdiv.visualstudio.com

    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.

Context cost

Macios CI Failure Inspector loads about 2.3k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 109 tokens; SKILL.md has 616 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.2k

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 616 words (~2,279 tokens).

“Investigate Azure DevOps CI failures for the dotnet/macios repository, extract root causes, and report findings.”

— opening of SKILL.md by dotnet, Custom licence
name
macios-ci-failure-inspector

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file (references) in .agents/skills/macios-ci-failure-inspector of dotnet/macios.

  • SKILL.md
  • references/azure-devops-cli.md

Open the folder on GitHubat commit 354c2a6

Compare with similar skills

Macios CI Failure Inspector 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.

Macios CI Failure Inspector compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Macios CI Failure Inspector this skilldotnet/macios2.9k—~2.3kAutomated safety check: PassCustom licence
Analyze Azdo BuildDataDog/dd-trace-dotnet573—~3.5kAutomated safety check: PassApache-2.0
MAUI UI Test Writerdotnet/maui23k—~3kAutomated safety check: PassMIT
Try Fix Alternative Approachdotnet/maui23k—~8.4kAutomated safety check: PassMIT
Apple Crash Log .NET Symbolicationdotnet/skills5.6k1 repos~2.4kAutomated safety check: PassMIT
Run Maui Apptig/winprint101—~1.2kAutomated safety check: PassMIT

Similar skills

  • Analyze Azdo Build

    DataDog/dd-trace-dotnet

    Official

    Analyze Azure DevOps CI build failures in dd-trace-dotnet pipeline.

    573 GitHub stars~3.5k tokensUpdated today
    Testing & QAAuto-check passed

  • MAUI UI Test Writer

    dotnet/maui

    Official

    Writes UI tests that reproduce a GitHub issue in .NET MAUI and keeps iterating until the tests actually fail, proving they catch the bug.

    23k GitHub stars~3k tokensUpdated today
    Testing & QAAuto-check passed

  • Try Fix Alternative Approach

    dotnet/maui

    Official

    Attempts one alternative fix for a bug, runs the given test command against it and reports what happened, always differing from existing PR fixes.

    23k GitHub stars~8.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Apple Crash Log .NET Symbolication

    dotnet/skills

    Official

    Resolves .NET runtime frames in Apple .ips crash logs to function names, source files and line numbers using dSYM symbols, atos and the Microsoft symbol server.

    5.6k GitHub starsUsed in 1 repo~2.4k tokens
    MobileAuto-check passed

  • Run Maui App

    tig/winprint

    Build, launch, screenshot, and drive the WinPrint.Maui Windows app (winprint.exe) — including UIA automation of the File button and native Open dialog, and pixel capture that works for WinUI3 content.

    101 GitHub stars~1.2k tokensUpdated 1 mo ago
    MobileAuto-check passed

  • Maui AI Debugging

    Redth/Maui.Gtk

    End-to-end workflow for building, deploying, inspecting, and debugging .NET MAUI and MAUI Blazor Hybrid apps as an AI agent.

    101 GitHub stars~4.1k tokensUpdated 5 mo ago
    MobileAuto-check passed

More from dotnet/macios

All 9 skills in this repo

  • Code Review

    dotnet/macios

    Official

    Review dotnet/macios PRs against established rules. An agent skill from dotnet/macios.

    2.9k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Macios Xcode Beta Update

    dotnet/macios

    Official

    Update dotnet/macios to a new Xcode beta and validate it end-to-end.

    2.9k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Fix Random CI Test Failure

    dotnet/macios

    Official

    Investigate and fix flaky/random CI test failures in dotnet/macios.

    2.9k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Gh Stack

    dotnet/macios

    Official

    Manage stacked branches and pull requests with the gh-stack GitHub CLI extension.

    2.9k GitHub starsUsed in 3 repos~10k tokens
    Auto-check passed

  • Macios Binding Creator

    dotnet/macios

    Official

    Create C bindings for Apple frameworks in dotnet/macios. An agent skill from dotnet/macios.

    2.9k GitHub stars~7.3k tokensUpdated today
    Auto-check passed

  • Macios CI Postmortem

    dotnet/macios

    Official

    Post-mortem analysis of CI failures across recent PRs in dotnet/macios.

    2.9k GitHub stars~7.8k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Macios CI Failure Inspector

What does Macios CI Failure Inspector do?

Investigate and triage CI failures for dotnet/macios from Azure DevOps build URLs. Macios CI Failure Inspector is an agent skill from dotnet/macios, published by the product's own GitHub organization. Investigate and triage CI failures for dotnet/macios from Azure DevOps build URLs.

When should I use Macios CI Failure Inspector?

Macios CI Failure Inspector fits situations like: the user shares a DevOps build link; asks about CI failures; wants to understand why a build failed; asks to investigate test failures on any platform (iOS.

How do I install Macios CI Failure Inspector in Claude Code?

Run `npx skills add dotnet/macios --skill macios-ci-failure-inspector -a claude-code`. Or copy the skill folder (.agents/skills/macios-ci-failure-inspector in dotnet/macios) into .claude/skills/macios-ci-failure-inspector in your project. Claude Code loads it when a task matches its description.

How do I install Macios CI Failure Inspector in Codex?

Run `npx skills add dotnet/macios --skill macios-ci-failure-inspector -a codex`. Or copy the skill folder (.agents/skills/macios-ci-failure-inspector in dotnet/macios) into .agents/skills/macios-ci-failure-inspector in your project. Codex loads it when a task matches its description.

Can I use Macios CI Failure Inspector 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 dotnet/macios --skill macios-ci-failure-inspector -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/macios-ci-failure-inspector, .gemini/skills/macios-ci-failure-inspector, .github/skills/macios-ci-failure-inspector and .opencode/skills/macios-ci-failure-inspector in your project.

What does Macios CI Failure Inspector need to run?

Going by SKILL.md and its folder, Macios CI Failure Inspector needs the command-line tools its instructions call (az). Our summary lists: Python 3.

Does Macios CI Failure Inspector access the network?

SKILL.md names 1 domain. In commands or code: devdiv.visualstudio.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Macios CI Failure Inspector 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 Macios CI Failure Inspector use?

Macios CI Failure Inspector has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Macios CI Failure Inspector use?

About 2.3k tokens (SKILL.md is roughly 9.1k 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 876 tokens, read only when the agent opens those files.

What are the alternatives to Macios CI Failure Inspector?

Skills that share tags, products or a category with Macios CI Failure Inspector: Analyze Azdo Build (DataDog/dd-trace-dotnet, 573 stars), MAUI UI Test Writer (dotnet/maui, 23k stars), Try Fix Alternative Approach (dotnet/maui, 23k stars) and Apple Crash Log .NET Symbolication (dotnet/skills, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Macios CI Failure Inspector?

dotnet (a GitHub organization, an official publisher) maintains it in dotnet/macios, which has 2,912 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.

Source: dotnet/macios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.