Configure systemd services for self-hosted GitHub Actions runners.
npx skills add https://github.com/stars-end/agent-skills --skill github-runner-setup
Please help me install this Agent Skill. Skill: github-runner-setup Source: https://github.com/stars-end/agent-skills/tree/main/github-runner-setup Command: npx skills add https://github.com/stars-end/agent-skills --skill github-runner-setup
GitHub Actions self-hosted runner setup and maintenance. Use when setting up dedicated runner users, migrating runners from personal accounts, troubleshooting runner issues, or implementing runner isolation. Covers systemd services, environment isolation, and skills plane integration.
runner user, not dev user~/.agent/skills mountUse the github-runner-setup skill to configure and manage a self-hosted runner. Steps include creating a dedicated runner user, cloning agent-skills into the runner, and setting up the permanent skills mount; follow the full setup guide in docs/SELF_HOSTED_RUNNER_SETUP.md.
High-intent search queries and answers about installing and using this skill.
Self-hosted runner setup requires creating a dedicated runner user separate from your dev account, configuring systemd services for auto-restart capability, and mounting the skills plane at ~/.agent/skills. This isolates runner execution, ensures reliability across reboots, and maintains minimal permissions without sudo access by default.
Migration involves creating a new dedicated runner user, transferring runner registration to that user context, and reconfiguring systemd services to manage the runner lifecycle. This removes runner privileges from personal accounts and establishes proper environment isolation for production workloads.
Systemd services auto-start runners on reboot, handle graceful restarts, and provide centralized lifecycle management. This eliminates manual intervention after system maintenance and ensures your runners remain available without requiring persistent shell sessions.
Runner troubleshooting covers diagnosis of connectivity failures, execution errors, and environment misconfigurations. The skill guides isolation verification, systemd status inspection, and skills mount validation to resolve common operational issues.
No. Self-hosted runners operate with minimal permissions by default; the dedicated runner user runs without sudo access. Elevated permissions are not required for standard runner operation and job execution within the isolated environment.
The runner user receives a permanent ~/.agent/skills mount that persists across restarts. This integration allows runners to access shared skills resources while maintaining isolation boundaries and consistent environment state.
resonatehqDeploy the Resonate server on Linux with systemd and JWT authentication.
devrelaicomInspect readiness and job queue metrics for Midnight proof servers.
EdanStarfireManage processes by PID across Windows, Linux, and macOS.
magnus919Deploy and manage self-hosted GitHub Actions runners across systemd, Docker, and Kubernetes.