magpie-ci-runner-audit

Audit GitHub Actions workflow runner labels and macOS architecture mismatches via GitHub API.

79|76|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/apache/magpie --skill magpie-ci-runner-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: magpie-ci-runner-audit
Source: https://github.com/apache/magpie/tree/main/skills/ci-runner-audit
Command: npx skills add https://github.com/apache/magpie --skill magpie-ci-runner-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the audit of GitHub Actions workflow runner compatibility, helping maintainers identify obsolete runners and macOS architecture mismatches.

Core Features & Use Cases

  • Audit GitHub Actions Runners: Detects incompatible or retired runner labels and architecture mismatches in GitHub Actions workflows.
  • TSV Evidence: Generates TSV files containing evidence for review.
  • Use Case: Before editing workflow files, run this Skill to get a detailed report of potential compatibility issues in your GitHub Actions workflows.

Quick Start

Run 'scan_ci_runners.py all --repo apache/polaris' to audit runners for the 'apache/polaris' repository.

Frequently Asked Questions about magpie-ci-runner-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit GitHub Actions runners for compatibility issues?

To audit GitHub Actions runners for compatibility issues, run the scan_ci_runners.py script against a target repository. The tool automates runner label discovery and generates TSV evidence for manual review.

What causes macOS architecture mismatches in GitHub Actions workflows?

macOS architecture mismatches in GitHub Actions workflows occur when runner labels specify incompatible or retired CPU architectures. This audit tool detects these mismatches using the GitHub API to ensure workflow reliability.

Can I check for retired or obsolete GitHub Actions runner labels automatically?

Yes, you can check for retired or obsolete GitHub Actions runner labels automatically by running the scan_ci_runners.py script. It queries the repository to identify incompatible labels and outputs a TSV file for review.

Do I need GitHub API credentials to scan my repository workflow files?

Scanning repository workflow files for runner compatibility requires GitHub API access to retrieve workflow configurations. The audit script uses this data to find obsolete runners and macOS architecture mismatches.

What format does the GitHub Actions runner audit report use?

The GitHub Actions runner audit report uses TSV format. This provides maintainers with structured evidence of incompatible workflow runner labels and architecture mismatches for manual review.

When should I run a GitHub Actions runner compatibility check?

Run a GitHub Actions runner compatibility check before editing workflow files. This ensures you identify obsolete runners and macOS architecture mismatches beforehand, maintaining repository health and workflow reliability.