A diagnostic tool for identifying flaky GitHub Actions workflows by analyzing failure rates across specific trigger events and repositories.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install github-actions-trigger-health-audit
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install github-actions-trigger-health-audit using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
This skill provides developers and DevOps teams with a systematic way to audit the reliability of their automation pipelines. By parsing GitHub Actions run data, it exposes which specific event triggers—such as push, pull_request, or schedule—are most prone to failure, allowing teams to prioritize fixes for noisy or unstable CI/CD workflows. It effectively bridges the gap between raw execution logs and actionable maintenance insights. Integrating Openclaw Skills like this into your workflow enables a data-driven approach to maintaining infrastructure health and reducing developer friction caused by false positives in CI.
First, ensure you have bash and python3 installed in your environment. Collect the necessary run data using the GitHub CLI:
gh run view <run-id> --json databaseId,workflowName,event,conclusion,headBranch,headSha,createdAt,updatedAt,startedAt,url,repository > artifacts/github-actions/run-<run-id>.json
Then, execute the audit using the Openclaw Skills scripts provided in the repository:
RUN_GLOB='artifacts/github-actions/*.json' \
MIN_RUNS=3 \
FAIL_WARN_PERCENT=25 \
FAIL_CRITICAL_PERCENT=50 \
bash skills/github-actions-trigger-health-audit/scripts/trigger-health-audit.sh
The skill processes JSON files exported from the GitHub API and organizes data into a structured format for analysis:
| Attribute | Description |
|---|---|
| repository | The source repository for the workflow run |
| event | The trigger event (e.g., push, pull_request, schedule) |
| workflowName | The name of the GitHub Action workflow |
| conclusion | The final state (success, failure, cancelled, timed_out) |
| metrics | Calculated failure, cancel, and timeout rates plus average runtime |
Loading
Proactively identify and fix near-timeout GitHub Actions jobs before they break your CI pipeline.

A monitoring skill designed to detect and alert on GitHub Actions workflows that remain in queued or in-progress states for excessive periods.

Identify and rank flaky GitHub Actions steps by analyzing success and failure outcomes across multiple workflow runs.

Audit GitHub Actions rerun debt to identify and eliminate commit-level CI inefficiencies.

A static analysis tool to identify security hardening gaps in GitHub Actions workflow files before they reach production.

Cluster noisy JUnit test failures into stable, repeatable fingerprints to streamline CI triage and identify root causes.








































