CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/watch-github-actions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 gh CLI core of this skill is lean, executable, and well organized, but it is undermined by a massive inlined runbook about this specific repository's workflows (Codex Security, Trivy, release promotion) that is off-topic for a generic watch-GitHub-Actions skill, plus duplicated command sections and no reference files to offload detail to.

Suggestions

Move the repo-specific runbook material (Kubernetes E2E evidence, Codex Security diagnostics, Trivy/Cargo Deny/Protobuf/release workflow details) into dedicated reference files (e.g., references/ci-troubleshooting.md) and keep only a one-line pointer per topic in SKILL.md.

Remove duplicated content: 'gh run list --branch "$(git branch --show-current)"' and 'gh run list' appear multiple times, and 'gh run view <run-id> --log' / '--log-failed' are repeated both in the middle of the document and at the end of the 'View Job Logs' section.

Strip time-sensitive version specifics (e.g., 'Codex Security 0.8.3' exit-code behavior) from the always-loaded body, or isolate them in a clearly labeled version/deprecated section, and add a simple validation step in the example workflow (confirm the failed run ID before rerunning with --failed).

DimensionReasoningScore

Conciseness

Roughly 120 lines of repo-specific runbook prose (Kubernetes E2E diagnostics, Codex Security 0.8.3, Trivy baselines, release/promotion workflows) are inlined under 'View Job Logs', and several command sections (gh run list variants, --log/--log-failed) are duplicated verbatim. This is noticeably verbose with multiple padded sections; not 1 because it never explains concepts Claude already knows.

2 / 5

Actionability

The gh commands are concrete and copy-paste ready (e.g., the jq pipeline for run listing and the PR head-branch resolution snippet), and the tables give quick flag lookup. Not 5 because the large interleaved runbook section is descriptive prose naming artifacts rather than executable steps.

4 / 5

Workflow Clarity

The 'Example Workflow' provides a clear watch → view failed logs → rerun sequence, but there are no validation checkpoints (e.g., confirming the run ID or failure before rerunning) and the off-topic runbook block interrupts the monitoring procedure. Not 4 because the disruption and missing checkpoints are more than minor gaps.

3 / 5

Progressive Disclosure

No bundle files exist, yet ~120 lines of version-pinned, repo-specific reference material (Codex Security versions, release workflow semantics, compatibility trains) are inlined in the body — content that clearly belongs in separate reference files. Not 3 because there are no actual reference files or navigation to compensate; not 1 because section headers keep the document navigable.

2 / 5

Total

11

/

20

Passed

Description

83%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.

A strong description: third-person, concrete about capabilities, with an explicit 'Use when' clause and a dedicated trigger keyword list. Minor gaps in action coverage and a few missing natural synonyms keep it just below the top anchors.

DimensionReasoningScore

Specificity

Lists several concrete actions ("check workflow status, watch a running workflow, view CI/CD jobs, or monitor build progress") scoped to the gh CLI. Not 5 because capabilities like reruns, log viewing, and cancellation are not listed.

4 / 5

Completeness

Clearly answers both what ("Watch and monitor GitHub Actions workflow runs using the gh CLI") and when ("Use when the user wants to..." plus concrete trigger keywords). Matches the anchor for explicit what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Explicit keyword list ("watch pipeline, pipeline status, CI status, check build, monitor CI, view pipeline, pipeline progress, workflow status, actions status") covers natural phrasings well. Not 5 because common variants like "GitHub Actions", "build failed", or "CI results" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear GitHub Actions/CI-monitoring niche with mostly distinct triggers, but generic phrases like "check build" and "CI status" could overlap with other CI-related skills. Anchor 4 fits; not 5 due to that minor overlap risk.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

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.