技能详情(站内镜像,无评论)
作者:Daniel Lummis @daniellummis
许可证:MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本:v1.0.0
统计:⭐ 0 · 155 · 0 current installs · 0 all-time installs
⭐ 0
安装量(当前) 0
🛡 VirusTotal :良性 · OpenClaw :良性
Package:daniellummis/github-actions-failure-phase-audit
安全扫描(ClawHub)
- VirusTotal :良性
- OpenClaw :良性
OpenClaw 评估
The skill's code and instructions are consistent with its stated purpose (analyzing exported GitHub Actions run JSON files); there are a couple of small bookkeeping omissions but no signs of credential exfiltration or surprising behavior.
目的
The skill's name/description match what the script does: it scans GitHub Actions run JSON exports and groups failures by phase. Required binaries (bash, python3) are appropriate for the shipped script. One inconsistency: SKILL.md shows using the 'gh' CLI to export run JSONs, but 'gh' is not listed in the declared required binaries — the skill itself does not invoke 'gh' (it processes files), but users will typically run 'gh run view' to produc…
说明范围
The SKILL.md and script limit their actions to reading local JSON files (RUN_GLOB) and producing a text/JSON report and exit code. The instructions do tell the user how to call 'gh run view' to create input files; apart from that, the runtime logic only reads and aggregates data from those files and respects explicit environment filter variables. The only scope surprise is the implicit reliance on the user running 'gh' (which accesses GitHub) …
安装机制
This is an instruction-only skill with one included script and no install spec. Nothing is downloaded or written to system locations beyond the script present in the skill bundle. Risk from installation is low.
证书
The skill does not request any credentials or secret environment variables. It accepts a reasonable set of optional env inputs (RUN_GLOB, filters, thresholds). Note: producing the JSON inputs commonly involves using the 'gh' CLI, which uses the user's GitHub credentials outside of this skill — that credential use is not requested or managed by the skill itself.
持久
The skill does not request or modify agent/global config, does not require always:true, and does not persist credentials. It runs on demand and only processes files matched by the provided glob.
综合结论
This skill appears to do exactly what it says: aggregate failures from GitHub Actions run JSON files. Before installing/using it: 1) Be aware you (or an automation) must export run JSONs (the SKILL.md shows using 'gh run view'), and running 'gh' will use your local GitHub credentials — the skill itself does not request or transmit those. 2) The SKILL.md mentions the 'gh' CLI but the skill metadata does not list it as a required binary; ensure …
安装(复制给龙虾 AI)
将下方整段复制到龙虾中文库对话中,由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库(龙虾 AI)执行:为本机安装 OpenClaw 技能「GitHub Actions Failure Phase Audit」。简介:Group GitHub Actions failures by pipeline phase (setup/build/test/lint/deploy/s…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装:https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/daniellummis/github-actions-failure-phase-audit/SKILL.md
(来源:yingzhi8.cn 技能库)
SKILL.md
---
name: github-actions-failure-phase-audit
description: Group GitHub Actions failures by pipeline phase (setup/build/test/lint/deploy/security) with minute impact to prioritize fixes.
version: 1.0.0
metadata: {"openclaw":{"requires":{"bins":["bash","python3"]}}}
---
# GitHub Actions Failure Phase Audit
Use this skill to identify which CI/CD phase is burning the most minutes when jobs fail.
## What this skill does
- Reads one or more GitHub Actions run JSON exports (`gh run view --json ...`)
- Detects the first non-success step per failed/cancelled/timed-out job
- Maps failures to phases: `setup`, `build`, `test`, `lint`, `deploy`, `security`, `other`
- Aggregates failures by repo + workflow + phase + failed step
- Ranks hotspots by impacted minutes and failure count
## Inputs
Optional:
- `RUN_GLOB` (default: `artifacts/github-actions/*.json`)
- `TOP_N` (default: `20`)
- `OUTPUT_FORMAT` (`text` or `json`, default: `text`)
- `WARN_MINUTES` (default: `20`)
- `CRITICAL_MINUTES` (default: `45`)
- `FAIL_ON_CRITICAL` (`0` or `1`, default: `0`)
- `WORKFLOW_MATCH`, `WORKFLOW_EXCLUDE` (regex, optional)
- `REPO_MATCH`, `REPO_EXCLUDE` (regex, optional)
- `BRANCH_MATCH`, `BRANCH_EXCLUDE` (regex, optional)
- `PHASE_MATCH`, `PHASE_EXCLUDE` (regex, optional)
## Collect run JSON
```bash
gh run view <run-id> --json databaseId,workflowName,headBranch,headSha,url,repository,jobs
> artifacts/github-actions/run-<run-id>.json
```
## Run
Text report:
```bash
RUN_GLOB='artifacts/github-actions/*.json'
WARN_MINUTES=15
CRITICAL_MINUTES=35
bash skills/github-actions-failure-phase-audit/scripts/failure-phase-audit.sh
```
JSON output + fail gate:
```bash
RUN_GLOB='artifacts/github-actions/*.json'
OUTPUT_FORMAT=json
FAIL_ON_CRITICAL=1
bash skills/github-actions-failure-phase-audit/scripts/failure-phase-audit.sh
```
Phase filtered report:
```bash
RUN_GLOB='artifacts/github-actions/*.json'
PHASE_MATCH='^(test|deploy)$'
bash skills/github-actions-failure-phase-audit/scripts/failure-phase-audit.sh
```
Run with bundled fixtures:
```bash
RUN_GLOB='skills/github-actions-failure-phase-audit/fixtures/*.json'
bash skills/github-actions-failure-phase-audit/scripts/failure-phase-audit.sh
```
## Output contract
- Exit `0` in reporting mode
- Exit `1` when `FAIL_ON_CRITICAL=1` and critical hotspots exist
- Text output includes totals and ranked phase hotspots
- JSON output includes `summary`, `hotspots`, and `critical_hotspots`