manage-gh-runners

Provision, list, update, and deregister GitHub Actions self-hosted runners via Docker.

1.9k|352|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/radixark/miles --skill manage-gh-runners
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-gh-runners
Source: https://github.com/radixark/miles/tree/main/.claude/skills/manage-gh-runners
Command: npx skills add https://github.com/radixark/miles --skill manage-gh-runners

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill simplifies provisioning, listing, removing, and swapping GitHub Actions self-hosted runners on a CI host that uses the gh-runner image (raw docker run). It clarifies how to distinguish this flow from the docker-compose based actions-runner approach and guides setup when /data/miles_ci is not yet provisioned.

Core Features & Use Cases

  • Add, remove, list, or swap gh-runner containers on the CI host using consistent labeling and state management.
  • Deregister and cleanup gracefully to keep GitHub runner UI in sync and avoid offline zombies.
  • Guidance for flow selection between gh-runner and actions-runner/docker-compose, with explicit steps for host provisioning.

Quick Start

Use the manage-gh-runners skill to add, remove, or list GitHub Actions runners on your CI host.

Frequently Asked Questions about manage-gh-runners

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision a new GitHub Actions self-hosted runner using Docker?

To provision a self-hosted runner, use the manage-gh-runners skill to execute raw docker run commands with the gh-runner image. You must provide a GitHub repository URL via REPO_URL, a registration token, and ensure Docker access on the CI host.

What is the best way to deregister GitHub Actions runners and avoid offline zombies?

Deregistering GitHub Actions runners requires graceful cleanup to keep the runner UI in sync and avoid offline zombies. The manage-gh-runners skill automates this deregistration and state cleanup process on your CI host.

How do I list, update, or swap existing gh-runner containers on a CI host?

You can list, update, or swap gh-runner containers using the manage-gh-runners skill. It applies consistent labeling and state management to track and modify runner instances deployed via raw docker run.

Does this approach work with docker-compose based actions-runner setups?

The manage-gh-runners skill specifically targets raw docker run deployments using the gh-runner image. It provides guidance for flow selection to distinguish this approach from docker-compose based actions-runner configurations.

Why do I need a GitHub repo URL and registration token to set up gh-runners?

A GitHub repo URL via REPO_URL and a registration token are required to authenticate and link the self-hosted runner to your repository. The manage-gh-runners skill uses these credentials to provision and register the container.

What should I do if /data/miles_ci is not yet provisioned on my CI host?

If /data/miles_ci is not yet provisioned, the manage-gh-runners skill provides explicit setup steps and environment checks for host provisioning. This ensures the directory structure is ready before deploying runners.