Compile
apache/skywalking-nodejs
Compile / build / type-check the skywalking-nodejs agent. An agent skill from apache/skywalking-nodejs.
Watch and monitor GitHub Actions workflow runs using the gh CLI.
Install Watch GitHub Actions
$ npx skills add NVIDIA/OpenShell --skill watch-github-actions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/OpenShell watch-github-actions --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/watch-github-actions .claude/skills/watch-github-actions && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "watch-github-actions" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/watch-github-actions into .claude/skills/watch-github-actions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "watch-github-actions", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/watch-github-actionsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NVIDIA/OpenShell --skill watch-github-actions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/OpenShell watch-github-actions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/watch-github-actions .agents/skills/watch-github-actions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "watch-github-actions" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/watch-github-actions into .agents/skills/watch-github-actions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "watch-github-actions", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/OpenShell --skill watch-github-actions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/OpenShell watch-github-actions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/watch-github-actions .cursor/skills/watch-github-actions && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "watch-github-actions" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/watch-github-actions into .cursor/skills/watch-github-actions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "watch-github-actions", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NVIDIA/OpenShell.git --path .agents/skills/watch-github-actions--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/OpenShell --skill watch-github-actions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/OpenShell watch-github-actions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/watch-github-actions .gemini/skills/watch-github-actions && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "watch-github-actions" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/watch-github-actions into .gemini/skills/watch-github-actions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "watch-github-actions", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NVIDIA/OpenShell watch-github-actionsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NVIDIA/OpenShell --skill watch-github-actions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/watch-github-actions .github/skills/watch-github-actions && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "watch-github-actions" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/watch-github-actions into .github/skills/watch-github-actions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "watch-github-actions", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/OpenShell --skill watch-github-actions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/OpenShell watch-github-actions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/OpenShell.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/watch-github-actions .opencode/skills/watch-github-actions && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "watch-github-actions" agent skill from https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/watch-github-actions into .opencode/skills/watch-github-actions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "watch-github-actions", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
watch-github-actions- GitHub stars
- 15k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 682 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Watch and monitor GitHub Actions workflow runs using the gh CLI.
- Works in 4 steps: Push your changes and create/update a PR → Watch the workflow run → If a job fails, view the failed logs → …
- The user wants to check workflow status
- SKILL.md covers Prerequisites, Quick Status Check, Watch a Run in Real Time and View Run Details, plus 10 more sections
- Calls gh, git and trivy
What it does
Watch GitHub Actions is an agent skill from NVIDIA/OpenShell, published by the product's own GitHub organization. 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.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions and gRPC. The repository describes itself as: OpenShell is the safe, private runtime for autonomous AI agents. The licence is Apache-2.0.
When your agent uses it
- The user wants to check workflow status
- Watch a running workflow
- View CI/CD jobs
- Monitor build progress
Example prompts
- “/watch-github-actions”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Push your changes and create/update a PR
- Watch the workflow run
- If a job fails, view the failed logs
- Rerun the failed jobs if needed
What it can do on your machine
Read from SKILL.md and the folder at commit 834b79a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgittrivynix
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Watch GitHub Actions loads about 1.8k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 682 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from NVIDIA/OpenShell at commit 834b79a, republished under its Apache-2.0 licence (© NVIDIA). 682 words, ~1,809 tokens.
Download SKILL.mdSave it as
.claude/skills/watch-github-actions/SKILL.md (or your agent's skills folder).- name
- watch-github-actions
- description
- 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.
- metadata.internal
- true
Watch GitHub Actions
Monitor GitHub Actions workflow runs using the gh CLI.
Prerequisites
- The
ghCLI must be authenticated (gh auth status) - You must be in a git repository with a GitHub remote
Quick Status Check
List recent workflow runs for the current branch:
gh run list --branch "$(git branch --show-current)"List all recent runs:
gh run listWatch a Run in Real Time
Watch a workflow run until it completes:
gh run watchWatch a specific run:
gh run watch <run-id>This will continuously update the status until the run finishes (success, failure, or cancelled).
View Run Details
View a specific run with job details:
gh run view <run-id>View with full log output:
gh run view <run-id> --logView a failed job's log:
gh run view <run-id> --log-failedCheck Runs for a Specific Branch
Current branch:
gh run list --branch "$(git branch --show-current)"Specific branch:
gh run list --branch main
gh run list --branch feature-branchCheck Runs for a PR
List workflow runs associated with a PR:
# Get the head branch of the PR, then list runs
BRANCH=$(gh pr view <pr-number> --json headRefName --jq '.headRefName')
gh run list --branch "$BRANCH"Or view the checks directly on the PR:
gh pr checks <pr-number>List Recent Runs
List runs for the current project:
gh run listFilter by status:
gh run list --status failure
gh run list --status success
gh run list --status in_progressFilter by workflow:
gh run list --workflow "CI"JSON output for scripting:
gh run list --json databaseId,status,headBranch,url --jq '.[] | {id: .databaseId, status: .status, branch: .headBranch, url: .url}'View Job Logs
setup-nix retries development-shell preparation once when prepare-shell
is enabled. Inspect both attempts in the job log; setup-rust assumes the
shell has already been prepared. Cargo, lint, and test commands are not retried.
Direct Nix builds and app dependency preparation also retry once; apps run
once after preparation succeeds. Skipped dependent E2E suites indicate blocked
coverage.
For Trivy Changes, inspect the Resolve PR baseline step for the base and head
SHAs. PR runs compare the tested merge commit with its
first parent; change detection and scans must use the same pair. On reruns, do
not substitute the current main tip or the event's older PR base SHA. Merge
groups and manual runs use their explicit baseline. Findings are reported by
Reject new high or critical findings; distinguish those from scanner failures.
For Protobuf Compatibility, check the logged train and comparison baseline.
Branch Checks compares the prospective merge tree with its target; Release Tag
compares the tagged candidate with the previous stable release. Both use
the shared check-protobuf-compatibility action with nix run .#check-protobuf-compatibility -- <ref>.
During 0.x, a minor train permits compatibility findings
as warnings; a patch train or no active train rejects them. Compare the current
train's version with the latest stable release; commit messages are irrelevant.
Compilation, baseline, and tool errors remain fatal. The protobuf_compatibility suite participates in
the release-tag-v1 qualification profile. Both tagged pre-release and stable
publication require this profile to pass. Failed, cancelled, or skipped suites
block publication; build artifacts and qualification evidence remain in Actions
storage for diagnosis. Source-SHA images are staging inputs for qualification.
Snap builds run in parallel with qualification, but tagged stable Store uploads
consume those built artifacts only after qualification passes.
View logs for a specific run:
gh run view <run-id> --logView only failed job logs:
gh run view <run-id> --log-failedShow full SKILL.md (259 more words)Show less
Wait for Run Completion (Scripting)
Watch and wait for a run to complete:
RUN_ID=$(gh run list --branch "$(git branch --show-current)" --limit 1 --json databaseId --jq '.[0].databaseId')
gh run watch "$RUN_ID" --exit-status
echo "Run finished with exit code: $?"Open Run in Browser
Open the latest run in your default browser:
gh run view --webOpen a specific run:
gh run view <run-id> --webRerun Failed Jobs
Rerun all failed jobs in a run:
gh run rerun <run-id> --failedRerun an entire run:
gh run rerun <run-id>Useful Commands Reference
| Command | Description |
|---|---|
gh run list | List recent workflow runs |
gh run list --branch <branch> | List runs for a specific branch |
gh run list --status failure | List failed runs |
gh run watch | Watch latest run until completion |
gh run watch <run-id> | Watch a specific run until completion |
gh run view <run-id> | View run details and job list |
gh run view <run-id> --log | View full run logs |
gh run view <run-id> --log-failed | View only failed job logs |
gh run view --web | Open run in browser |
gh run rerun <run-id> | Rerun a workflow run |
gh run rerun <run-id> --failed | Rerun only failed jobs |
gh run cancel <run-id> | Cancel a running workflow |
gh pr checks <pr-number> | View PR check statuses |
Common Flags
| Flag | Description |
|---|---|
-b, --branch | Specify branch (default: current branch) |
--status | Filter by status (queued, in_progress, etc.) |
--workflow | Filter by workflow name |
-L, --limit | Maximum number of runs to list |
-w, --web | Open in browser |
--json | Output as JSON with specified fields |
--jq | Filter JSON output with jq expression |
Example Workflow
- Push your changes and create/update a PR
- Watch the workflow run:
bash gh run watch - If a job fails, view the failed logs:
bash gh run view <run-id> --log-failed - Rerun the failed jobs if needed:
bash gh run rerun <run-id> --failed
© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/watch-github-actions of NVIDIA/OpenShell.
Open the folder on GitHubat commit 834b79a
Compare with similar skills
Watch GitHub Actions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Watch GitHub Actions this skillNVIDIA/OpenShell | 15k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Compileapache/skywalking-nodejs | 180 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| GitHub Actions Templatesbartstc/vite-ts-react-template | 122 | 13 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Nushellccusage/ccusage | 19k | — | ~938 | Automated safety check: Pass | Custom licence | |
| Repo Hygiene Scan and FixQwenLM/qwen-code | 28k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
GitHub Actions Templates
bartstc/vite-ts-react-template
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications.
Nushell
ccusage/ccusage
Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
More from NVIDIA/OpenShell
All 23 skills in this repo- Official
Build Openshell Mxc Windows
NVIDIA/OpenShell
Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.
- Official
Create GitHub Issue
NVIDIA/OpenShell
Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.
- Official
Create GitHub PR
NVIDIA/OpenShell
Create GitHub pull requests using the gh CLI. An agent skill from NVIDIA/OpenShell.
- Official
Debug Inference
NVIDIA/OpenShell
Debug inference clients that use an attached provider and its native endpoint, including hosted APIs and host-local Ollama, vLLM, SGLang, TRT-LLM, LM Studio, or NIM.
- Official
Debug Openshell Cluster
NVIDIA/OpenShell
Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes.
- Official
Gator Gate
NVIDIA/OpenShell
Validate and monitor OpenShell GitHub issues and PRs using the gator: state machine.
Related
Works with
Categories
Questions about Watch GitHub Actions
What does Watch GitHub Actions do?
Watch and monitor GitHub Actions workflow runs using the gh CLI. Watch GitHub Actions is an agent skill from NVIDIA/OpenShell, published by the product's own GitHub organization. Watch and monitor GitHub Actions workflow runs using the gh CLI.
When should I use Watch GitHub Actions?
Watch GitHub Actions fits situations like: the user wants to check workflow status; watch a running workflow; view CI/CD jobs; monitor build progress.
How do I install Watch GitHub Actions in Claude Code?
Run `npx skills add NVIDIA/OpenShell --skill watch-github-actions -a claude-code`. Or copy the skill folder (.agents/skills/watch-github-actions in NVIDIA/OpenShell) into .claude/skills/watch-github-actions in your project. Claude Code loads it when a task matches its description.
How do I install Watch GitHub Actions in Codex?
Run `npx skills add NVIDIA/OpenShell --skill watch-github-actions -a codex`. Or copy the skill folder (.agents/skills/watch-github-actions in NVIDIA/OpenShell) into .agents/skills/watch-github-actions in your project. Codex loads it when a task matches its description.
Can I use Watch GitHub Actions in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/OpenShell --skill watch-github-actions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/watch-github-actions, .gemini/skills/watch-github-actions, .github/skills/watch-github-actions and .opencode/skills/watch-github-actions in your project.
What does Watch GitHub Actions need to run?
Going by SKILL.md and its folder, Watch GitHub Actions needs the command-line tools its instructions call (gh, git, trivy and nix).
Does Watch GitHub Actions access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Watch GitHub Actions safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Watch GitHub Actions use?
Watch GitHub Actions is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Watch GitHub Actions use?
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Watch GitHub Actions?
Skills that share tags, products or a category with Watch GitHub Actions: Compile (apache/skywalking-nodejs, 180 stars), Analyze GitHub Action Logs (withastro/astro, 63k stars), GitHub Actions Templates (bartstc/vite-ts-react-template, 122 stars) and Nushell (ccusage/ccusage, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Watch GitHub Actions?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/OpenShell, which has 15,188 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 7, 2026.
Source: NVIDIA/OpenShell on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.