Actions

GitHub Actions workflow management using GitHub CLI. Trigger when user wants to check CI status ("check CI", "is the build passing"), view workflow runs ("show recent runs", "view action logs"), watch running workflows ("watch CI"), or rerun failed workflows ("rerun the build").

42 stars 2 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add robbyt/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add robbyt/claude-skills --skill actions
Manual install
git clone --depth 1 https://github.com/robbyt/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/gh-cli/skills/actions ~/.claude/skills/actions

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# GitHub Actions

Monitor and manage GitHub Actions workflows with the `gh` CLI.

## Prerequisites

GitHub CLI must be installed and authenticated:
```bash
gh auth status
```

## Quick Reference

```bash
gh run list                         # List recent runs
gh run view 789                     # View run details
gh run view 789 --log               # View run logs
gh run watch 789                    # Watch running workflow
gh run rerun 789                    # Rerun workflow
```

## List Workflow Runs

```bash
gh run list
gh run list --limit 10
gh run list --workflow ci.yml
gh run list --status failure
gh run list --branch main
```

## View Run Details

```bash
gh run view 789
gh run view 789 --json status,conclusion,jobs
```

## View Run Logs

```bash
gh run view 789 --log
gh run view 789 --log-failed  # Only failed job logs
```

## Watch Running Workflow

```bash
gh run watch 789
gh run watch 789 --exit-status  # Exit with workflow status code
```

## Rerun Workflows

```bash
gh run rerun 789
gh run rerun 789 --failed  # Rerun only failed jobs
```

## List Workflows

```bash
gh workflow list
gh workflow view ci.yml
```
Read the full skill on GitHub

Details

Skill name
actions
Path
plugins/gh-cli/skills/actions/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Actions skill do?

GitHub Actions workflow management using GitHub CLI. Trigger when user wants to check CI status ("check CI", "is the build passing"), view workflow runs ("show recent runs", "view action logs"), watch running workflows ("watch CI"), or rerun failed workflows ("rerun the build").

How do I install the Actions skill?

Claude Code plugin: /plugin marketplace add robbyt/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Actions popular?

It lives in robbyt/claude-skills, which has 42 GitHub stars and 2 forks.

Related skills

Adversarial Review

42

robbyt/claude-skills

Have Codex try to break a change before it ships — a skeptical review that challenges the design, assumptions, and failure modes of a diff or branch and returns structured findings (verdict, severity, file:line, confidence). Trigger on "adversarial review", "challenge this change/design with Codex", "pressure-test this before I ship", "have Codex try to break this", "is this safe to merge", or a review focused on a risk area (auth, data loss, rollback, race conditions, retries). Do NOT use for a routine bug/style pass over a diff (that's diff-review), for critiquing a plan before code exists (

Software Development

API Review

42

robbyt/claude-skills

This skill should be used when reviewing API designs, auditing REST or gRPC endpoints, designing backend APIs, evaluating BFF architecture, or discussing API best practices. Also triggers on: "review this API", "API design review", "is this API correct", "REST API audit", "gRPC API review", "PATCH vs PUT", "etag", "idempotency", "pagination design", "API error handling", "backward compatibility", "BFF architecture", "resource-oriented design", "TOCTOU", "race condition", "optimistic concurrency", "field mask", "long-running operation", "custom method", "soft delete", "API naming conventions",

Software Development

Artifact Detect

42

robbyt/claude-skills

This skill should be used when the user asks "what's wrong with this video", "why does this video look bad", "detect video artifacts", "find quality issues", "video has artifacts", "identify compression artifacts", or wants to diagnose specific quality problems in a video file.

Images, Video & Audio

Calendar Helper

39

ShawhinT/non-coding-skills

Create, reschedule, and delete events on Shaw's Google Calendar — and keep the matching Notion page in sync when one exists. Use this skill whenever Shaw wants to put something on the calendar, move an existing event, or cancel one. Triggers include: "schedule X", "create an event for", "put X on my calendar", "book a call with Y next Tuesday", "set up a 1:1 with", "another session with X next Saturday", "follow-up call with X", "reschedule the X meeting", "move my X call to Friday", "cancel the X event", "delete that meeting", or any casual phrasing that implies adding/changing a calendar blo

Productivity & Notes

Task Observer

37

iamneilroberts/claude-skills

Monitors task execution for skill improvement opportunities. Use this skill during ANY multi-step task, agentic workflow, or substantive work session where Claude is using tools and producing deliverables. It captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable skills. Also triggers during post-task feedback discussions and when the user explicitly mentions skill observations, improvements, the observation log, skill taxonomy, or asks Claude to watch for skill opportunities. Also known as "One Skill to Rule Them All" — trigger on this phrase too.

Productivity & Notes

Call Follow Up

39

ShawhinT/non-coding-skills

Process the Follow-up sections Shaw jots on his ABA Calls and ABA Trainings pages after calls. Route each open bullet to where it belongs (the next call page, an ABA task, a CRM Next Contact date, or the email task), then cross off what's handled. Works over any window Shaw names, like yesterday's calls, last week's, a specific date range, or one named call. Use whenever Shaw says "do yesterday's call follow-up", "call follow-up for last week", "follow-up for the [Name] call", "what did I jot down after my calls", "carry this to next week's call", "what's still open from this week's calls", or

Productivity & Notes

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.