popey/github-action-monitor
Automatically monitor GitHub Actions workflows after git push operations. Tracks workflow progress and reports pass/fail results.
93
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels at completeness and trigger term quality, with explicit 'Use when' guidance and natural user language. The main weakness is that the capability description could be more specific about the range of actions supported (e.g., retrieving logs, checking specific workflows, handling retries).
Suggestions
Expand the capabilities list to include more specific actions like 'retrieve workflow logs', 'check specific workflow status', or 'monitor multiple runs' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | 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. | 2 / 3 |
Completeness | 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. | 3 / 3 |
Trigger Term Quality | 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. | 3 / 3 |
Distinctiveness Conflict Risk | 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. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent actionability and workflow clarity. The step-by-step process is clear with proper validation checkpoints and failure handling. The only weakness is a vague reference to 'beads' in the Background Monitoring section without explanation or documentation link.
Suggestions
Either explain what 'beads' are in the Background Monitoring section or remove the reference if it's not essential to the skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | 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. | 3 / 3 |
Actionability | Provides fully executable bash commands with proper variable usage, jq queries, and clear command patterns. All code is copy-paste ready with appropriate placeholders. | 3 / 3 |
Workflow Clarity | 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. | 3 / 3 |
Progressive Disclosure | 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. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents