Official agent skill

Macios CI Postmortem

by dotnet in dotnet/macios

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

OfficialCustom licenceAuto-check passedTesting & QA

Install Macios CI Postmortem

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

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

GitHub CLI
$ gh skill install dotnet/macios macios-ci-postmortem --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-postmortem .claude/skills/macios-ci-postmortem && 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-postmortem
GitHub stars
2.9k
Token cost
~7.8k tokens
SKILL.md length
2,441 words
Files
2 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
Custom licence

At a glance

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

  • Works in 4 steps: Discovery — Collect Recent Builds → Extraction — Get Failure Details → Classification → …
  • Asked to find flaky tests
  • SKILL.md covers References, Overview, Phase 1: Discovery — Collect… and Phase 2: Extraction — Get…, plus 2 more sections
  • Calls az, gh and python3; reaches devdiv.visualstudio.com

What it does

Macios CI Postmortem is an agent skill from dotnet/macios, published by the product's own GitHub organization. Post-mortem analysis of CI failures across recent PRs in dotnet/macios. Identifies flaky tests, infrastructure issues, and shared regressions by analyzing builds from the last week. Files or updates GitHub issues for failures unrelated to any specific PR. Use when asked to "find flaky tests", "CI post-mortem", "what's been failing in CI", or "file issues for flaky failures".

Its SKILL.md is about 7.8k 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 and Runbooks and postmortems. It works with .NET, GitHub and C#. 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

  • Asked to find flaky tests
  • Whats been failing in CI
  • File issues for flaky failures

Example prompts

  • “find flaky tests”
  • “CI post-mortem”
  • “s been failing in CI”
  • “/macios-ci-postmortem”

Requirements

  • Python 3

Workflow steps

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

  1. Discovery — Collect Recent Builds
  2. Extraction — Get Failure Details
  3. Classification
  4. Issue Actions

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
    • gh
    • python3

    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 Postmortem loads about 7.8k tokens when it runs, and up to ~8.7k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 2,441 words of instructions outside code blocks.

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

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 2,441 words (~7,782 tokens).

“Analyze CI failures across recent PRs to identify flaky tests, infrastructure issues, and shared regressions that are not caused by any specific PR. File or update GitHub issues for these.”

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

Read the full SKILL.md on GitHub

Files

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

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

Open the folder on GitHubat commit 354c2a6

Compare with similar skills

Macios CI Postmortem 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 Postmortem compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Macios CI Postmortem this skilldotnet/macios2.9k—~7.8kAutomated safety check: PassCustom licence
MAUI CI Investigatordotnet/maui23k—~2kAutomated safety check: PassMIT
MAUI UI Test Writerdotnet/maui23k—~3kAutomated safety check: PassMIT
GreptimeDB Fuzz CI Failure InvestigationGreptimeTeam/greptimedb6.7k—~4.4kAutomated safety check: PassApache-2.0
Code Reviewjonathanpeppers/dotnes780—~2.1kAutomated safety check: PassMIT
Release Roslynatordotnet/roslynator3.5k—~1kAutomated safety check: PassCustom licence

Similar skills

  • Official

    Adds dotnet/maui-specific context for investigating failing PR checks and broken nightly builds: pipelines, Helix logs, binlogs and merge-readiness verdicts.

    23k GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check passed
  • 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
  • Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.

    6.7k GitHub stars~4.4k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Code Review

    jonathanpeppers/dotnes

    Review dotnes pull requests against established repository rules.

    780 GitHub stars~2.1k tokensUpdated 13 days ago
    DevelopmentAuto-check passed
  • Release Roslynator

    dotnet/roslynator

    Official

    A skill your agent uses when shipping a roslynator release, rolling CHANGELOG.md [Unreleased], updating the VS Code extension changelog, creating a GitHub v release, or optionally tagging cli-v.

    3.5k GitHub stars~1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Babysit PR

    ZenUml/web-sequence

    Monitor and diagnose GitHub Actions checks on ZenUML web-sequence PRs, fixing code-caused CI failures when appropriate.

    150 GitHub stars~871 tokensUpdated 2 days ago
    Testing & QAAuto-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
  • Official

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

    2.9k GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • 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
  • 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 2 repos~10k tokens
    Auto-check passed
  • 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

Works with

Questions about Macios CI Postmortem

What does Macios CI Postmortem do?

Post-mortem analysis of CI failures across recent PRs in dotnet/macios. Macios CI Postmortem is an agent skill from dotnet/macios, published by the product's own GitHub organization. Post-mortem analysis of CI failures across recent PRs in dotnet/macios.

When should I use Macios CI Postmortem?

Macios CI Postmortem fits situations like: asked to find flaky tests; whats been failing in CI; file issues for flaky failures.

How do I install Macios CI Postmortem in Claude Code?

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

How do I install Macios CI Postmortem in Codex?

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

Can I use Macios CI Postmortem 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-postmortem -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-postmortem, .gemini/skills/macios-ci-postmortem, .github/skills/macios-ci-postmortem and .opencode/skills/macios-ci-postmortem in your project.

What does Macios CI Postmortem need to run?

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

Does Macios CI Postmortem 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 Postmortem 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 Postmortem use?

Macios CI Postmortem 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 Postmortem use?

About 7.8k tokens (SKILL.md is roughly 31k 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 Postmortem?

Skills that share tags, products or a category with Macios CI Postmortem: MAUI CI Investigator (dotnet/maui, 23k stars), MAUI UI Test Writer (dotnet/maui, 23k stars), GreptimeDB Fuzz CI Failure Investigation (GreptimeTeam/greptimedb, 6.7k stars) and Code Review (jonathanpeppers/dotnes, 780 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Macios CI Postmortem?

dotnet (a GitHub organization, an official publisher) maintains it in dotnet/macios, which has 2,906 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 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.