Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →withastro/analyze-github-action-logs
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
Passed 8 of 14 test cases with the skill, and 4 of 14 without it.
and 5 more in the full report
8 fixed4 passed either way8 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
When downloading logs for run ID 12345678 in `withastro/astro` for analysis, where should the raw log data be saved and what CLI command format should be used to dump the full execution log?
| Checked | Without skill | With skill |
|---|---|---|
| Saves log output to `/tmp/actions-run-12345678.log` using `gh run view`. | Missed | Passed |
The instructions your model reads when the skill loads.
Fetch and analyze recent GitHub Actions runs for a given workflow. Review agent/step performance, identify wasted effort and mistakes, and produce a report with actionable improvements.
You need:
workflow (required) — The workflow file name or ID (e.g., issue-triage.yml, deploy.yml).repo (optional) — The GitHub repository in OWNER/REPO format. Defaults to withastro/astro.count (optional) — Number of recent completed runs to analyze. Defaults to 5.Fetch the most recent completed runs for the workflow. Filter by --status=completed:
gh run list --workflow=<workflow> -R <repo> --status=completed -L <count>
Present the list to orient yourself: run IDs, titles, status (success/failure), and duration. Pick the runs to analyze — prefer a mix of successes and failures if available, and prefer runs that exercised more steps (longer runs tend to go through more stages, while shorter runs may exit early).
For each run you want to analyze, save the full log to a temp file:
gh run view <run_id> -R <repo> --log > /tmp/actions-run-<run_id>.log
Search each log file for markers that indicate where each step or skill starts and ends. The markers depend on the workflow — look for patterns like:
[flue] skill("..."): starting / completedSTART/END or similar delimiters the workflow usesgrep -n "skill(\|step\|START\|END\|starting\|completed" /tmp/actions-run-<run_id>.log | head -50
test cases passed, vs 4 / 14 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.