openclaw 网盘下载
OpenClaw

技能详情(站内镜像,无评论)

首页 > 技能库 > GitHub Actions Incident Timeline Audit

Cluster failed GitHub Actions runs into incident windows by repo to expose outage duration, impact scope, and escalation severity.

开发与 DevOps

作者:Daniel Lummis @daniellummis

许可证:MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本:v1.0.0

统计:⭐ 0 · 149 · 0 current installs · 0 all-time installs

0

安装量(当前) 0

🛡 VirusTotal :良性 · OpenClaw :良性

Package:daniellummis/github-actions-incident-timeline-audit

安全扫描(ClawHub)

  • VirusTotal :良性
  • OpenClaw :良性

OpenClaw 评估

The skill's code and instructions are consistent with its stated purpose (clustering GitHub Actions failure JSON into incident windows) and do not request unrelated credentials, network access, or elevated persistence.

目的

Name/description match the included script and SKILL.md: the script reads exported GitHub Actions run JSON files, groups failures into incidents, scores severity, and emits text/JSON. Required binaries (bash, python3) are appropriate. Minor note: SKILL.md shows an example using the 'gh' CLI to fetch run JSON, but 'gh' is not declared as a required binary — this is a documentation/example omission rather than a functional mismatch.

说明范围

Runtime instructions and the script operate on local JSON files matched by RUN_GLOB and on CLI-provided parameters. The script does not perform network calls, read system-wide config, or access unrelated environment variables. It only parses files, computes clusters, and prints output. There is no evidence of data exfiltration or contacting external endpoints.

安装机制

No install specification — instruction-only with a bundled script. Nothing is downloaded or written to system paths by an installer. Risk from installation is minimal.

证书

The skill requests no environment secrets or config paths. All behavioral controls are via optional environment variables (RUN_GLOB, thresholds, filters). No unexpected credentials or keys are required.

持久

Skill does not request always: true and has no special persistence or privileged actions. It is user-invocable and can be run manually; autonomous invocation is allowed by platform default but is not combined with other red flags.

综合结论

This skill appears to do what it says: parse local GitHub Actions run JSON files and produce incident windows. Before running, ensure the RUN_GLOB path points only to intended JSON exports (so you don't accidentally parse unrelated files), and review any JSON fixtures you feed it (don't run over untrusted files). If you plan to collect run JSON via the 'gh' CLI as shown in the SKILL.md, install/verify 'gh' yourself (it's only an example and no…

安装(复制给龙虾 AI)

将下方整段复制到龙虾中文库对话中,由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库(龙虾 AI)执行:为本机安装 OpenClaw 技能「GitHub Actions Incident Timeline Audit」。简介:Cluster failed GitHub Actions runs into incident windows by repo to expose outa…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装:https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/daniellummis/github-actions-incident-timeline-audit/SKILL.md
(来源:yingzhi8.cn 技能库)

SKILL.md

打开原始 SKILL.md(GitHub raw)

---
name: github-actions-incident-timeline-audit
description: Cluster failed GitHub Actions runs into incident windows by repo to expose outage duration, impact scope, and escalation severity.
version: 1.0.0
metadata: {"openclaw":{"requires":{"bins":["bash","python3"]}}}
---

# GitHub Actions Incident Timeline Audit

Use this skill to convert noisy failed run exports into incident windows you can triage quickly during CI reliability reviews.

## What this skill does
- Reads GitHub Actions run JSON exports
- Keeps only failed/cancelled/timed-out style outcomes
- Groups failures by repository into incident windows using a configurable gap threshold
- Scores each incident using failed-run and duration thresholds
- Emits text or JSON output for review docs, ops dashboards, and CI fail gates

## Inputs
Optional:
- `RUN_GLOB` (default: `artifacts/github-actions/*.json`)
- `TOP_N` (default: `20`)
- `OUTPUT_FORMAT` (`text` or `json`, default: `text`)
- `INCIDENT_GAP_MINUTES` (default: `45`)
- `WARN_FAILED_RUNS` (default: `2`)
- `CRITICAL_FAILED_RUNS` (default: `4`)
- `WARN_DURATION_MINUTES` (default: `20`)
- `CRITICAL_DURATION_MINUTES` (default: `60`)
- `WORKFLOW_MATCH` (regex, optional)
- `WORKFLOW_EXCLUDE` (regex, optional)
- `REPO_MATCH` (regex, optional)
- `REPO_EXCLUDE` (regex, optional)
- `FAIL_ON_CRITICAL` (`0` or `1`, default: `0`)

## Collect run JSON

```bash
gh run view <run-id> --json databaseId,workflowName,event,conclusion,headBranch,createdAt,updatedAt,startedAt,url,repository 
  > artifacts/github-actions/run-<run-id>.json
```

## Run

Text report:

```bash
RUN_GLOB='artifacts/github-actions/*.json' 
INCIDENT_GAP_MINUTES=45 
bash skills/github-actions-incident-timeline-audit/scripts/incident-timeline-audit.sh
```

JSON output with fail gate:

```bash
RUN_GLOB='artifacts/github-actions/*.json' 
OUTPUT_FORMAT=json 
FAIL_ON_CRITICAL=1 
bash skills/github-actions-incident-timeline-audit/scripts/incident-timeline-audit.sh
```

Run with bundled fixtures:

```bash
RUN_GLOB='skills/github-actions-incident-timeline-audit/fixtures/*.json' 
bash skills/github-actions-incident-timeline-audit/scripts/incident-timeline-audit.sh
```

## Output contract
- Exit `0` in report mode (default)
- Exit `1` when `FAIL_ON_CRITICAL=1` and one or more incidents are critical
- Text mode prints summary + ranked incident windows
- JSON mode prints summary + incidents + critical incident details