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)tools
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).