watch-github-actions

Watch and monitor GitHub Actions workflow runs using the gh CLI. Use when the user wants to check workflow status, watch a running workflow, view CI/CD jobs, or monitor build progress. Trigger keywords - watch pipeline, pipeline status, CI status, check build, monitor CI, view pipeline, pipeline progress, workflow status, actions status.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable gh commands and a solid example workflow, but it suffers from meaningful redundancy — repeated commands and two summary tables that restate earlier snippets, plus an out-of-place verbose Trivy paragraph — which drags down token efficiency. Structure is good but could be leaner.

Suggestions

Consolidate the overlapping 'Quick Status Check', 'List Recent Runs', and 'Check Runs for a Specific Branch' sections into one, and remove the duplicate 'Useful Commands Reference'/'Common Flags' tables that restate commands already shown inline.

Move or trim the project-specific 'Trivy Changes / Resolve PR baseline' paragraph — it is unrelated to general GitHub Actions monitoring and reads as over-explanation Claude does not need here.

Add a brief validation/confirmation checkpoint to the 'Example Workflow' (e.g., confirm the run-id before rerunning failed jobs) to push workflow clarity toward the top anchor.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose with redundant sections — 'gh run view <run-id> --log' and 'gh run list --branch' recur across 'Quick Status Check', 'View Run Details', 'View Job Logs', and 'Check Runs for a Specific Branch', and the two summary tables rehash every command already shown; the dense Trivy/baseline-SHA paragraph inlines project-specific CI internals that pad rather than instruct.	2 / 5
Actionability	Fully executable, copy-paste-ready gh commands throughout, with clear placeholders (<run-id>, <pr-number>), jq scripting examples, and a consolidated command/flag reference covering the common cases.	5 / 5
Workflow Clarity	The 'Example Workflow' gives a clear 4-step sequence (push → watch → view failed logs → rerun) with only minor validation gaps; this is a low-risk monitoring skill so the absence of formal checkpoints is acceptable.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested references and no bundle files to navigate, but the ~220-line monolith with duplicated command tables could be tightened/consolidated rather than fully meeting the lean-overview ideal.	4 / 5
	Total	15 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, explicit what-and-when structure, and a rich set of natural trigger keywords with synonyms. The only minor weakness is mild redundancy among the listed actions, which keeps specificity just below the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain (GitHub Actions workflow runs via gh CLI) and several concrete actions — 'check workflow status, watch a running workflow, view CI/CD jobs, or monitor build progress' — but the actions overlap somewhat (watch/monitor, check status), leaving minor coverage gaps rather than comprehensive distinction.	4 / 5
Completeness	Explicitly answers both: 'what' ('Watch and monitor GitHub Actions workflow runs using the gh CLI') and 'when' ('Use when the user wants to check workflow status, watch a running workflow, view CI/CD jobs, or monitor build progress'), with concrete trigger phrases appended.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage with synonyms — 'watch pipeline, pipeline status, CI status, check build, monitor CI, view pipeline, pipeline progress, workflow status, actions status' — spanning the pipeline/CI/workflow/actions phrasings a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Clear niche (GitHub Actions via gh CLI) with distinct, targeted triggers; minimal overlap risk with other skills since the tooling and domain are narrowly scoped.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: NVIDIA/OpenShell
Path: .agents/skills/watch-github-actions/SKILL.md
Commit: 292559c

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.