GitHub Actions Stuck Run Audit for Openclaw

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

daniellummis
v1.0.0
Mar 8, 2026
0
840
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install github-actions-stuck-run-audit

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install github-actions-stuck-run-audit using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is GitHub Actions Stuck Run Audit?

The GitHub Actions Stuck Run Audit is a technical utility integrated into the Openclaw Skills ecosystem to provide visibility into workflow execution health. It analyzes exported GitHub Actions run metadata to identify "stale" runs—those that have not reached a terminal state within expected timeframes. By quantifying stuck-run volume and stuck-rate percentages, it allows teams to identify resource contention, runner availability issues, or configuration errors before they quietly halt the delivery pipeline.

GitHub Actions Stuck Run Audit Use Cases

  • Monitoring high-concurrency CI environments for workflow queuing bottlenecks.
  • Auditing repository health to ensure runners are picking up jobs as expected.
  • Implementing automated CI/CD quality gates that fail when too many critical workflows are stuck.
  • Identifying long-running jobs that consume excess minutes without progressing.

How GitHub Actions Stuck Run Audit Works

  1. Run data is exported from the GitHub CLI in JSON format for the targeted workflows.
  2. The skill processes these JSON files using a configurable glob pattern to aggregate run metadata.
  3. It filters for non-terminal statuses such as queued, in_progress, pending, or waiting.
  4. It calculates the age and risk score of each group based on user-defined minute and volume thresholds.
  5. It outputs a ranked severity report (ok, warn, or critical) and optionally triggers a non-zero exit code for automation.

GitHub Actions Stuck Run Audit Setup

Ensure you have the GitHub CLI, bash, and python3 installed on your system.

First, export your run data:

gh run view <run-id> \
  --json databaseId,workflowName,event,headBranch,status,conclusion,createdAt,runStartedAt,updatedAt,url,repository \
  > artifacts/github-actions/run-<run-id>.json

Then, execute the audit using Openclaw Skills scripts:

RUN_GLOB='artifacts/github-actions/*.json' \
bash skills/github-actions-stuck-run-audit/scripts/stuck-run-audit.sh

GitHub Actions Stuck Run Audit Data Schema & Taxonomy

The skill consumes JSON metadata produced by the GitHub CLI. It organizes results into a hierarchy based on the chosen grouping strategy.

Input Parameter Default Value Description
GROUP_BY repo-workflow Aggregation level (repo, repo-workflow, or repo-workflow-branch)
STUCK_STATUSES queued,in_progress... List of non-terminal statuses to monitor
WARN_STUCK_MINUTES 45 Minutes before a run is flagged as a warning
CRITICAL_STUCK_MINUTES 120 Minutes before a run is flagged as critical

GitHub Actions Stuck Run Audit Advanced Features

  • Support for regex-based filtering (match or exclude) for repositories, branches, events, and specific workflows.
  • Deterministic replay capabilities using NOW_ISO timestamp overrides for historical auditing.
  • Highly configurable risk scoring based on both raw volume and percentage-based stuck rates.
  • Dual output modes providing either human-readable text summaries or structured JSON for downstream automation.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Requires
Bins bashpython3
Github Stars: 0
forks: 0

Featured*