ov-layers/skills/github-runner/SKILL.md
GitHub Actions self-hosted runner as a supervised container service. Use when working with GitHub Actions runners, CI/CD infrastructure, or runner registration.
npx skillsauth add overthinkos/overthink-plugins github-runnerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Dependencies | supervisord |
| Volumes | state -> /opt/actions-runner, storage -> /var/lib/containers/storage |
| Service | github-runner (supervisord) |
| Security | privileged: true |
| Install files | tasks: |
| Variable | Value |
|----------|-------|
| RUNNER_ALLOW_RUNASROOT | 1 |
| RUNNER_WORK_DIR | /opt/actions-runner/_work |
| RUNNER_GROUP | Default |
| OV_BUILD_ENGINE | podman |
| OV_RUN_ENGINE | podman |
skopeo, jq, libcap, podman, buildah, golang, git (RPM)openssh-clients, systemd-container, qemu-user-static-aarch64 (RPM)RUNNER_ORG and RUNNER_TOKENRUNNER_TOKEN)# image.yml
githubrunner:
layers:
- github-runner
ov config githubrunner -e RUNNER_ORG=myorg -e RUNNER_TOKEN=xxx
ov remove githubrunner -e RUNNER_TOKEN=xxx
/ov-images:githubrunner/ov-layers:supervisord -- process manager dependencyUse when the user asks about:
RUNNER_TOKEN or RUNNER_ORG configuration/ov:layer — layer authoring reference (tasks, vars, env_provides, tests block syntax)/ov:test — declarative testing framework for the tests: blocktools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).