ov-layers/skills/gnupg/SKILL.md
GnuPG encryption and signing tools for GPG agent forwarding. Use when working with GPG, encryption, signing, or the gnupg layer.
npx skillsauth add overthinkos/overthink-plugins gnupgInstall 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 |
|----------|-------|
| Install files | layer.yml (packages only) |
RPM: gnupg2 · PAC: gnupg · DEB: gnupg — full cross-distro parity. Note: gnupg is also in the debian distro's bootstrap package set (see /ov-images:debian) because downstream layers need gpg --dearmor at build time.
# image.yml
my-image:
layers:
- gnupg
Typically used as part of the agent-forwarding composition layer rather than directly.
Provides gpg, gpgconf, gpg-agent, gpg-connect-agent binaries inside the container. When combined with SSH/GPG agent forwarding (ov shell, ov start direct mode), the container's GPG uses the host's agent for private key operations (signing, decryption) via a forwarded socket.
The container has its own keyring (public keys must be imported separately with gpg --import). No host keyring is mounted — only the agent socket is forwarded.
Part of agent-forwarding composition layer, used in 27 application images including: arch-ov, fedora-ov, nvidia, jupyter, ollama, openclaw, immich, comfyui, selkies-desktop, and all other non-base images.
/ov-layers:agent-forwarding -- metalayer that includes gnupg + direnv + ssh-client/ov-layers:direnv -- environment variable loading from .envrc/.secrets/ov-layers:ssh-client -- OpenSSH client for SSH agent forwarding/ov:secrets -- ov secrets gpg commands: key management (import-key, export-key), GPG agent setup (setup), health check (doctor), and .secrets file management/ov:shell -- agent socket forwarding happens at ov shell invocation time/ov:service -- agent forwarding in ov start direct modeUse when the user asks about:
gnupg layer/ov:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov:test — declarative testing (tests: block, ov image test, ov test)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).