How do I install the Gh Workflow skill?

Run npx skillmds@latest add tomevault-io/gh-workflow-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gh Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Workflow?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Workflow by tomevault-io — Agent Skill

Name: Gh Workflow
Author: tomevault-io

Gh Workflow

Trigger and monitor GitHub Actions workflows, CI/CD pipelines, and automated builds. Use when running workflows, triggering CI, deploying via GitHub Actions, downloading artifacts, or checking workflow status on github.com Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

gh-workflow

Run GitHub workflows on github.com

Workflow

When the user asks to run a workflow:

Verify git remotes and confirm commits are pushed (MANDATORY):
- Check remotes: git remote -v | grep github.com
- Get current commit: git rev-parse HEAD
- Verify commit exists on remote: git fetch github && git branch -r --contains $(git rev-parse HEAD) | grep -q github/
- If not found, push first: git push github HEAD:main (or appropriate branch name)
- Quick check: git fetch github && git branch -r --contains HEAD | grep -q github/ || echo "WARNING: HEAD not pushed to github"
Check the workflow file in .github/workflows/ to understand its trigger type and inputs
For workflow_dispatch workflows: trigger directly with gh workflow run
For push workflows: push to the remote first, then the workflow runs automatically
Use appropriate parameters based on the workflow's input definitions
For testing/iteration with matrix builds: prefer x64 over arm64 (faster provisioning)
Download workflow artifacts to verify outputs

Usage

# List workflows
GH_HOST=github.com gh workflow list

# Run a workflow
GH_HOST=github.com gh workflow run <workflow-name>

# Run with inputs
GH_HOST=github.com gh workflow run <workflow-name> -f key=value

# View recent runs
GH_HOST=github.com gh run list --workflow=<workflow-name>

# Watch a run
GH_HOST=github.com gh run watch <run-id>

# Download artifacts from a run
GH_HOST=github.com gh run download <run-id>

Testing matrix builds

For workflows with matrix builds, test with the fastest variant first:

Prefer x64 over arm64 (x64 runners provision faster)
Prefer ubuntu over macos (faster startup)
Use workflow inputs to target specific matrix cells if supported

Examples

# Run workflow_dispatch workflow with inputs
GH_HOST=github.com gh workflow run luajit.yml -f release_tag=2025.11.23 -f create_release=true

# Run workflow at specific commit (preferred - explicit and reproducible)
GH_HOST=github.com gh workflow run luajit.yml --ref $(git rev-parse HEAD)

# Or with explicit SHA
GH_HOST=github.com gh workflow run luajit.yml --ref abc1234

# Run without creating release (testing)
GH_HOST=github.com gh workflow run nvim.yml -f create_release=false

# Download artifacts from latest run
GH_HOST=github.com gh run list --workflow=luajit.yml --limit 1 --json databaseId --jq '.[0].databaseId' | xargs -I {} GH_HOST=github.com gh run download {}

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: gh-workflow-2description: Trigger and monitor GitHub Actions workflows, CI/CD pipelines, and automated builds. Use when running workflows, triggering CI, deploying via GitHub Actions, downloading artifacts, or checking workflow status on github.com Use when this capability is needed.---# gh-workflowRun GitHub workflows on github.com## WorkflowWhen the user asks to run a workflow:1. **Verify git remotes and confirm commits are pushed** (MANDATORY): - Check remotes: `git remote -v | grep github.com` - Get current commit: `git rev-parse HEAD` - Verify commit exists on remote: `git fetch github && git branch -r --contains $(git rev-parse HEAD) | grep -q github/` - If not found, push first: `git push github HEAD:main` (or appropriate branch name) - Quick check: `git fetch github && git branch -r --contains HEAD | grep -q github/ || echo "WARNING: HEAD not pushed to github"`2. Check the workflow file in `.github/workflows/` to understand its trigger type and inputs3. For `workflow_dispatch` workflows: trigger directly with `gh workflow run`4. For `push` workflows: push to the remote first, then the workflow runs automatically5. Use appropriate parameters based on the workflow's input definitions6. For testing/iteration with matrix builds: prefer x64 over arm64 (faster provisioning)7. Download workflow artifacts to verify outputs## Usage```bash# List workflowsGH_HOST=github.com gh workflow list# Run a workflowGH_HOST=github.com gh workflow run <workflow-name># Run with inputsGH_HOST=github.com gh workflow run <workflow-name> -f key=value# View recent runsGH_HOST=github.com gh run list --workflow=<workflow-name># Watch a runGH_HOST=github.com gh run watch <run-id># Download artifacts from a runGH_HOST=github.com gh run download <run-id>```## Testing matrix buildsFor workflows with matrix builds, test with the fastest variant first:- Prefer x64 over arm64 (x64 runners provision faster)- Prefer ubuntu over macos (faster startup)- Use workflow inputs to target specific matrix cells if supported## Examples```bash# Run workflow_dispatch workflow with inputsGH_HOST=github.com gh workflow run luajit.yml -f release_tag=2025.11.23 -f create_release=true# Run workflow at specific commit (preferred - explicit and reproducible)GH_HOST=github.com gh workflow run luajit.yml --ref $(git rev-parse HEAD)# Or with explicit SHAGH_HOST=github.com gh workflow run luajit.yml --ref abc1234# Run without creating release (testing)GH_HOST=github.com gh workflow run nvim.yml -f create_release=false# Download artifacts from latest runGH_HOST=github.com gh run list --workflow=luajit.yml --limit 1 --json databaseId --jq '.[0].databaseId' | xargs -I {} GH_HOST=github.com gh run download {}```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/whilp) — claim your Tome and manage your conversions.

Frequently asked questions