A specialized tool to detect workflow performance degradation by comparing recent failure rates against historical baselines.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install github-actions-failure-spike-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-failure-spike-audit using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
The GitHub Actions Failure Spike Audit is a diagnostic utility designed for engineering teams who need to maintain CI/CD stability. By analyzing GitHub Actions run data, this skill identifies sudden increases in failure rates that often signal flaky tests, broken deployment gates, or infrastructure issues before they escalate into major outages. It is an essential component within the Openclaw Skills ecosystem for teams prioritizing automated quality assurance.
It works by grouping run data by repository, workflow name, branch, and event type. It then bifurcates these groups into a recent window and a baseline window, calculating the failure rate delta. This quantitative approach allows for automated scoring, categorizing workflow health into ok, warning, or critical statuses.
Ensure you have bash and python3 installed on your system. This skill is a standard part of the Openclaw Skills repository.
First, collect your workflow 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, run the audit script:
RUN_GLOB='artifacts/github-actions/*.json' \
RECENT_RUNS=8 \
WARN_SPIKE_PCT=12 \
bash skills/github-actions-failure-spike-audit/scripts/failure-spike-audit.sh
The skill processes specific GitHub Actions metadata and outputs structured results based on the following run attributes:
| Attribute | Description |
|---|---|
| databaseId | Unique identifier for the run |
| workflowName | The name of the GitHub Action workflow |
| conclusion | The final status (success, failure, etc.) |
| headBranch | The branch name where the run occurred |
| repository | The repository context |
The output generates a ranked list of failure-rate spikes, providing visibility into which specific workflow/branch combinations are degrading.
Loading
A diagnostic tool that categorizes GitHub Actions failures into phases like build, test, and deploy to rank hotspots by time impact.

Identify and attribute GitHub Actions failures to specific owners or workflows to optimize CI stability and reduce wasted minutes.

Summarize and rank GitHub Actions matrix job failures across multiple runs to quickly identify unstable OS or runtime combinations.

A diagnostic tool that analyzes GitHub Actions run history to identify specific days and hours when workflow failures cluster.

Audit GitHub Actions run history to identify and rank consecutive failure streaks that disrupt software delivery.

A specialized tool to cluster noisy GitHub Actions failure logs into structured incident windows for better CI reliability reporting.








































