The skill is lean and efficient, providing only necessary commands and context. It assumes Claude knows git, bash, and the gh CLI without explaining basic concepts.

Provides fully executable bash commands with proper variable usage, jq queries, and clear command patterns. All code is copy-paste ready with appropriate placeholders.

Clear 5-step sequence with explicit validation points (check for workflows, retry if no runs found, handle failures). Includes feedback loop for polling and specific failure handling with log retrieval.

Well-organized with clear sections, but the Background Monitoring section mentions 'beads (if available)' without explanation or reference. The skill is appropriately sized for a single file but could benefit from linking to advanced async patterns.

Names the domain (GitHub Actions) and describes the core action (monitors workflow runs, reports pass/fail results), but doesn't list multiple specific concrete actions like checking specific workflow types, retrieving logs, or handling different failure scenarios.

Clearly answers both what ('Monitors GitHub Actions workflow runs and reports pass/fail results') and when ('Use when git push has been executed, code has been pushed to a remote, or when the user asks about CI status') with explicit trigger guidance.

Includes natural keywords users would say: 'git push', 'pushed to a remote', 'CI status'. These are terms users naturally use when wanting to check build results. Also includes 'GitHub Actions' and 'workflow runs' for more specific queries.

Has a clear niche focused specifically on GitHub Actions CI monitoring with distinct triggers (git push, CI status). Unlikely to conflict with general git skills or other document/code skills due to the specific CI/workflow focus.