runner

Manage self-hosted GitHub Actions runners with rebuild, start, stop, and log commands.

7|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/frogdb/frogdb --skill runner-frogdb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runner
Source: https://github.com/frogdb/frogdb/tree/main/.claude/skills/runner
Command: npx skills add https://github.com/frogdb/frogdb --skill runner-frogdb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill unit solves the problem of managing self-hosted GitHub Actions runners by providing commands to rebuild, start, stop, and check logs, ensuring smooth CI operations.

Core Features & Use Cases

  • Rebuild and Start: Automates rebuilding the runner image and starting the container when configuration files change.
  • Stop and Logs: Provides commands to stop the runner and view logs, facilitating troubleshooting.
  • Proactive Rebuild Suggestions: Suggests rebuilding the runner image proactively when changes in configuration files are detected.
  • Use Case: When a CI job fails due to runner-related errors or when you need to ensure the runner is up-to-date with the latest configurations.

Quick Start

To rebuild and start the GitHub Actions runner, use the runner command.

Frequently Asked Questions about runner

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

FAQPage Schema
How do I manage self-hosted GitHub Actions runners when CI jobs fail?

To manage self-hosted GitHub Actions runners when CI jobs fail, you can use commands to stop the runner, view logs for troubleshooting, and rebuild the runner image to ensure it is up-to-date and operational.

How do I rebuild a self-hosted GitHub Actions runner after updating configuration files?

You can rebuild a self-hosted GitHub Actions runner after updating configuration files by executing a specific runner command that automates rebuilding the runner image and starting the container to apply the new configurations.

Does Docker Compose work with self-hosted GitHub Actions runner management?

Yes, Docker Compose is supported for self-hosted GitHub Actions runner management, allowing you to rebuild runner images, start containers, and ensure your CI operations run smoothly when configurations change.

Can I view logs for self-hosted GitHub Actions runners to troubleshoot errors?

Yes, you can view logs for self-hosted GitHub Actions runners to facilitate troubleshooting by using the provided logs command, helping you identify and resolve runner-related errors during CI operations.

When should I proactively rebuild my self-hosted GitHub Actions runner image?

You should proactively rebuild your self-hosted GitHub Actions runner image when changes in configuration files are detected, ensuring the runner remains up-to-date and preventing potential CI job failures.