minibox-ci

Diagnose and manage a self-hosted GitHub Actions runner on a remote VPS.

1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/89jobrien/dotfiles --skill minibox-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: minibox-ci
Source: https://github.com/89jobrien/dotfiles/tree/main/dot-claude/skills/minibox-ci
Command: npx skills add https://github.com/89jobrien/dotfiles --skill minibox-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Minibox CI & Runner Ops provides a structured approach to managing a self-hosted GitHub Actions runner on a remote VPS, helping teams diagnose CI failures and maintain runner health.

Core Features & Use Cases

  • Centralized references for runner setup and xtask usage with quick access to diagnostics and maintenance tasks
  • Commands and scripts to check runner status, view CI results, and diagnose issues (via runner-status.sh, ci-status.sh, and ssh-based tooling)
  • Practical workflows for SSH-based management, runner re-registration, and ongoing CI diagnostics

Quick Start

Run the minibox-ci quick diagnostics to check runner status and identify configuration issues.

Frequently Asked Questions about minibox-ci

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

FAQPage Schema
How do I check the status of a self-hosted GitHub Actions runner on a remote VPS?

To check GitHub Actions runner status on a remote VPS, use SSH-based tooling and reference scripts like runner-status.sh to diagnose runner health and identify configuration issues.

How do I diagnose CI failures for xtask-based gate operations on Linux hosts?

Diagnose CI failures for xtask-based gate operations by running quick CI diagnostics, using ci-status.sh to view recent CI results, and applying non-destructive read-only guidance to ensure reliability.

What is the process for runner re-registration in a Minibox CI environment?

Runner re-registration in a Minibox CI environment involves using practical SSH-based management workflows to reconfigure the self-hosted GitHub Actions runner and restore its connection to the repository.

Can I manage self-hosted GitHub Actions runners without causing destructive changes to my VPS?

Yes, you can manage self-hosted GitHub Actions runners safely because the diagnostics and maintenance processes apply non-destructive, read-only guidance to check runner health and view CI results without altering the system.

Why is my self-hosted GitHub Actions runner not picking up jobs from my repository?

Your self-hosted GitHub Actions runner may not be picking up jobs due to configuration issues or offline status, which you can identify by running quick diagnostics and checking runner status via SSH.