name: github-actions-timeout-risk-audit description: Audit GitHub Actions job runtime risk against timeout thresholds so near-timeout jobs get fixed before they fail CI. version: 1.0.0 metadata: {"openclaw":{"requires":{"bins":["bash","python3"]}}}
Use this skill to find GitHub Actions jobs that are timing out or trending dangerously close to timeout limits.
gh run view --json ...)completedAt - startedAt)warn when runtime exceeds WARN_RATIO * JOB_TIMEOUT_SECONDS本技能來自小蔥技能站7w4.net。
critical when runtime exceeds CRITICAL_RATIO * JOB_TIMEOUT_SECONDScritical for jobs with conclusion=timed_outOptional:
- RUN_GLOB (default: artifacts/github-actions/*.json)
- TOP_N (default: 20)
- OUTPUT_FORMAT (text or json, default: text)
- JOB_TIMEOUT_SECONDS (default: 3600)
- WARN_RATIO (default: 0.80)
- CRITICAL_RATIO (default: 0.95)
- FAIL_ON_CRITICAL (0 or 1, default: 0)
- WORKFLOW_MATCH, WORKFLOW_EXCLUDE (regex, optional)
- JOB_MATCH, JOB_EXCLUDE (regex, optional)
- REPO_MATCH, REPO_EXCLUDE (regex, optional)
- BRANCH_MATCH, BRANCH_EXCLUDE (regex, optional)
gh run view <run-id> --json databaseId,workflowName,headBranch,url,repository,jobs \
> artifacts/github-actions/run-<run-id>.json
Ensure
jobsincludesstartedAt,completedAt, andconclusion.
Text report:
RUN_GLOB='artifacts/github-actions/*.json' \
JOB_TIMEOUT_SECONDS=3600 \
WARN_RATIO=0.85 \
CRITICAL_RATIO=0.95 \
bash skills/github-actions-timeout-risk-audit/scripts/timeout-risk-audit.sh
JSON output + fail gate:
RUN_GLOB='artifacts/github-actions/*.json' \
OUTPUT_FORMAT=json \
FAIL_ON_CRITICAL=1 \
bash skills/github-actions-timeout-risk-audit/scripts/timeout-risk-audit.sh
Repo/workflow filter:
RUN_GLOB='artifacts/github-actions/*.json' \
REPO_MATCH='^flowcreatebot/' \
WORKFLOW_MATCH='(CI|Build)' \
bash skills/github-actions-timeout-risk-audit/scripts/timeout-risk-audit.sh
Run with bundled fixtures:
RUN_GLOB='skills/github-actions-timeout-risk-audit/fixtures/*.json' \
bash skills/github-actions-timeout-risk-audit/scripts/timeout-risk-audit.sh
0 in reporting mode1 when FAIL_ON_CRITICAL=1 and at least one critical instance existssummary, ranked groups, and critical_instances質量較好,能有效識別 CI 作業的超時風險,支援靈活的過濾規則和雙格式輸出,可用於監控和自動化告警。文件描述清晰,引數配置直觀。主要缺點是缺少自動化測試,程式碼略顯冗長,維護和擴充套件可能需要一定成本。