CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 content is highly actionable with executable gh commands and clear organization, but it is weakened by significant command repetition and a workflow that lacks explicit validation checkpoints around batch rerun operations.

Suggestions

Consolidate the repeated 'gh run list' / 'gh run view --log' / '--log-failed' blocks into a single reference plus the table to cut redundancy.

Add an explicit validation step to the Example Workflow (e.g. confirm failure with 'gh run view --log-failed' before rerunning, and verify the rerun with 'gh run watch --exit-status').

Consider moving the 'Useful Commands Reference' and 'Common Flags' tables into a separate reference file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Prose is lean with no concept over-explanation, but commands repeat heavily across sections (e.g. 'gh run list' appears ~5 times, 'gh run view --log' / '--log-failed' each duplicated) and 'Check Runs for a Specific Branch' reprints the Quick Status block, which could be consolidated.

3 / 5

Actionability

Commands are fully executable and copy-paste ready, covering the common cases (list, watch, view, rerun, cancel, PR checks, JSON/jq scripting) with concrete flag usage, matching the 5 anchor.

5 / 5

Workflow Clarity

The 'Example Workflow' gives a watch -> diagnose -> rerun sequence but has no explicit validation/feedback checkpoint, and 'gh run rerun' is a batch operation; per the rubric, missing validation for batch/destructive operations caps this at 3.

3 / 5

Progressive Disclosure

No bundle files exist, but the body is well organized with clear section headers and two reference tables and has no nested references; minor organization gaps from the inlined, repetitive reference material keep it just below 5.

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: it names the tool and concrete actions, provides an explicit 'Use when' clause, and lists numerous natural trigger keywords. It is distinct and unlikely to collide with other skills.

DimensionReasoningScore

Specificity

Concrete actions tied to a named tool ('Watch and monitor GitHub Actions workflow runs using the gh CLI', 'check workflow status, watch a running workflow, view CI/CD jobs') list several specific capabilities with only minor gaps, matching the 4 anchor.

4 / 5

Completeness

It clearly states what the skill does (watch/monitor GHA runs via gh CLI) and when to use it ('Use when the user wants to check workflow status, watch a running workflow, view CI/CD jobs...') with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

An explicit 'Trigger keywords' list provides nine natural phrases users would say (watch pipeline, CI status, check build, monitor CI, workflow status, actions status), giving comprehensive coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

The niche is clearly scoped to GitHub Actions monitoring via the gh CLI with distinct pipeline/CI/workflow triggers, minimizing overlap with unrelated skills.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NVIDIA/OpenShell
Reviewed

Table of Contents

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.