ov-layers/skills/direnv/SKILL.md
direnv -- automatic environment variable loading from .envrc files. Use when working with direnv, .envrc, .secrets, or environment management.
npx skillsauth add overthinkos/overthink-plugins direnvInstall 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: direnv · PAC: direnv · DEB: direnv — full cross-distro parity.
# image.yml
my-image:
layers:
- direnv
Typically used as part of the agent-forwarding composition layer rather than directly. Also available in the heavyweight dev-tools layer (46 packages).
Provides the direnv binary for automatic environment variable loading from .envrc files. When entering a directory with .envrc, direnv evaluates it and exports environment variables.
The primary use case in Overthink is the .secrets workflow: .envrc calls eval "$(ov secrets gpg env)" which decrypts a GPG-encrypted .secrets file in memory and exports the variables — no plaintext on disk. No external direnvrc dependency needed.
Part of agent-forwarding composition layer, used in 27 application images.
Also available in dev-tools layer (used in bazzite-ai, fedora-remote).
/ov-layers:agent-forwarding -- metalayer that includes gnupg + direnv + ssh-client/ov-layers:gnupg -- GPG tools (needed for .secrets decryption)/ov-layers:dev-tools -- heavyweight layer that also includes direnv (46 packages)/ov:secrets -- ov secrets gpg commands for managing .secrets files, ov secrets gpg setup for GPG agent + KeePassXC configuration, ov secrets gpg doctor for health checksUse when the user asks about:
.envrc filesdirenv layer.secrets + direnv workflow/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).