runner

Manage GitHub Actions self-hosted runner deployment, updates, and health monitoring.

3|1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill runner-omninode-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runner
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/runner
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill runner-omninode-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the deployment, updating, and monitoring of self-hosted GitHub Actions runners, ensuring your CI/CD infrastructure is always operational and efficient.

Core Features & Use Cases

  • Deploy & Update Runners: Easily deploy new runners or update existing ones on your CI host.
  • Monitor Runner Status: Get a clear overview of runner health, versions, and host metrics.
  • Dry-Run Mode: Preview changes before applying them to avoid unintended consequences.
  • Use Case: Ensure your CI/CD pipeline has sufficient capacity by deploying additional runners during peak times or updating them to the latest version to leverage new features.

Quick Start

Check the status and health of all GitHub Actions runners.

Frequently Asked Questions about runner

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

FAQPage Schema
How do I monitor GitHub Actions self-hosted runners and host metrics?

You can monitor GitHub Actions self-hosted runners by checking detailed status reports that include runner health, software versions, and host-level metrics like disk usage, along with alert conditions for offline runners.

Can I preview runner deployment changes before applying them to my CI/CD infrastructure?

Yes, you can preview runner deployment changes using a dry-run mode to avoid unintended consequences, allowing you to verify updates or new deployments on your CI host before execution.

How do I deploy and update self-hosted GitHub Actions runners?

You can deploy and update self-hosted GitHub Actions runners by integrating with the GitHub API and Docker to manage the runner lifecycle directly on a specified CI host.

Does this runner management approach work with Docker for lifecycle control?

Yes, runner management integrates with Docker and the GitHub API to provide complete lifecycle control, enabling deployment, updates, and health monitoring for self-hosted GitHub Actions runners.

What are the limitations when managing GitHub Actions runners with this method?

The primary limitation is that runner management requires a specified host and Docker integration, and while it provides health alerts for disk usage and offline states, it focuses solely on self-hosted GitHub Actions runner lifecycles.

Why does my GitHub Actions runner show an offline alert status?

Your GitHub Actions runner shows an offline alert because the monitoring system generates alert conditions when it detects runners that are currently offline or experiencing critical host-level issues like high disk usage.