ov-foundation/skills/fedora-remote/SKILL.md
Fedora image using remote layer references from GitHub. Demonstrates the @github.com/org/repo/layers/name:version remote layer syntax. MUST be invoked before building, deploying, configuring, or troubleshooting the fedora-remote image.
npx skillsauth add overthinkos/overthink-plugins fedora-remoteInstall 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.
Fedora image built with remote layer references — layers fetched from GitHub at build time.
| Property | Value | |----------|-------| | Base | quay.io/fedora/fedora:43 | | Layers | (remote refs) | | Platforms | linux/amd64 | | Registry | ghcr.io/overthinkos |
layers:
- "@github.com/overthinkos/overthink/layers/dev-tools:main"
- "@github.com/overthinkos/overthink/layers/build-toolchain:v2026.64.1937"
- "@github.com/overthinkos/overthink/layers/nodejs"
dev-tools:main — pinned to main branchbuild-toolchain:v2026.64.1937 — pinned to specific version tagnodejs — default branch (no version specified)ov image build fedora-remote
ov shell fedora-remote
/ov-coder:dev-tools — bat, ripgrep, neovim, gh, direnv, etc./ov-coder:build-toolchain — gcc, cmake, autoconf, ninja, git/ov-coder:nodejs — Node.js + npmAfter ov image build:
ov image list — image appears in listov shell fedora-remote — interactive shell works/ov-foundation:fedora — local-layer parent base image/ov-foundation:fedora-builder — local-layer alternative bundling the same tooling/ov-build:build — fetch remote layer refs and build the image/ov-build:validate — validate remote layer references resolveMUST be invoked when the task involves the fedora-remote image, remote layer references, or the @github.com/... layer syntax. Invoke this skill BEFORE reading source code or launching Explore agents.
/ov-build:image — image family umbrella (image: entries in overthink.yml, build/validate/inspect/list)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.