How do I install the Github Actions Management skill?

Run npx skillmds@latest add ofershap-mcp-server-github-actions/github-actions-management 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 Github Actions Management safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Actions Management?

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 Github Actions Management free to use?

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

Who published Github Actions Management?

ofershap (@ofershap-mcp-server-github-actions) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Actions Management by ofershap-mcp-server-github-actions

Name: Github Actions Management
Rating: 4.2 (5 reviews)
Author: ofershap

Github Actions Management

Manage GitHub Actions workflows via MCP. Use when CI failed, the user asks why a workflow run failed, to re-run failed jobs, cancel a queued run, list workflow artifacts, trigger workflow_dispatch, or check deployment status for owner/repo.

ofershap Updated Sep 10, 2026

File contents

GitHub Actions Management via MCP

Use this skill when you need to check CI/CD status, read workflow logs, re-run failed jobs, or trigger deployments.

Available Tools

Tool	What it does
`list_workflows`	List all workflow files in a repository
`list_runs`	List workflow runs (filter by workflow or status)
`get_run`	Get details of a specific workflow run
`get_run_logs`	Get the logs URL for a run (zip download)
`rerun_workflow`	Re-run an entire workflow run
`rerun_failed_jobs`	Re-run only the failed jobs from a run
`cancel_run`	Cancel an in-progress or queued run
`list_artifacts`	List artifacts produced by a workflow run
`trigger_workflow`	Trigger a workflow via `workflow_dispatch`

Workflow

Use list_runs with owner and repo to see recent runs and their status
For failed runs: get_run for details, then decide whether to rerun_failed_jobs or investigate logs
trigger_workflow requires the workflow file name and a branch — the workflow must have a workflow_dispatch trigger

Key Patterns

All tools require owner and repo parameters (e.g., owner: "ofershap", repo: "my-project")
list_runs supports status filter: "completed", "in_progress", "queued", "failure", "success"
rerun_failed_jobs is preferred over rerun_workflow; it is faster and cheaper
trigger_workflow needs workflow_id (filename like "ci.yml") and ref (branch name)

Error Scenarios

401/403 from GitHub: GITHUB_TOKEN missing, expired, or lacks Actions scope on the repo
Run or workflow not found: double-check owner, repo, and numeric run id from list_runs
trigger_workflow rejected: workflow file lacks workflow_dispatch or branch ref is wrong
get_run_logs returns a zip URL only: download and unzip outside the tool to read full log text

Safety

Prefer rerun_failed_jobs over full rerun_workflow to avoid unnecessary compute
Confirm before cancel_run; the user may want the run to finish
trigger_workflow can trigger deployments; always confirm the target branch

---name: github-actions-managementdescription: Manage GitHub Actions workflows via MCP. Use when CI failed, the user asks why a workflow run failed, to re-run failed jobs, cancel a queued run, list workflow artifacts, trigger workflow_dispatch, or check deployment status for owner/repo.---# GitHub Actions Management via MCPUse this skill when you need to check CI/CD status, read workflow logs, re-run failed jobs, or trigger deployments.## Available Tools| Tool | What it does || ------------------- | ------------------------------------------------- || `list_workflows` | List all workflow files in a repository || `list_runs` | List workflow runs (filter by workflow or status) || `get_run` | Get details of a specific workflow run || `get_run_logs` | Get the logs URL for a run (zip download) || `rerun_workflow` | Re-run an entire workflow run || `rerun_failed_jobs` | Re-run only the failed jobs from a run || `cancel_run` | Cancel an in-progress or queued run || `list_artifacts` | List artifacts produced by a workflow run || `trigger_workflow` | Trigger a workflow via `workflow_dispatch` |## Workflow1. Use `list_runs` with `owner` and `repo` to see recent runs and their status2. For failed runs: `get_run` for details, then decide whether to `rerun_failed_jobs` or investigate logs3. `trigger_workflow` requires the workflow file name and a branch — the workflow must have a `workflow_dispatch` trigger## Key Patterns- All tools require `owner` and `repo` parameters (e.g., `owner: "ofershap"`, `repo: "my-project"`)- `list_runs` supports `status` filter: "completed", "in_progress", "queued", "failure", "success"- `rerun_failed_jobs` is preferred over `rerun_workflow`; it is faster and cheaper- `trigger_workflow` needs `workflow_id` (filename like "ci.yml") and `ref` (branch name)## Error Scenarios- 401/403 from GitHub: `GITHUB_TOKEN` missing, expired, or lacks Actions scope on the repo- Run or workflow not found: double-check `owner`, `repo`, and numeric run id from `list_runs`- `trigger_workflow` rejected: workflow file lacks `workflow_dispatch` or branch `ref` is wrong- `get_run_logs` returns a zip URL only: download and unzip outside the tool to read full log text## Safety- Prefer `rerun_failed_jobs` over full `rerun_workflow` to avoid unnecessary compute- Confirm before `cancel_run`; the user may want the run to finish- `trigger_workflow` can trigger deployments; always confirm the target branch

Frequently asked questions