infrastructure/skills/valkey/SKILL.md
Valkey 9.x key-value store (Redis-compatible) on port 6379 via Remi modular repo. Use when working with Valkey, Redis-compatible caching, or the valkey layer.
npx skillsauth add overthinkos/overthink-plugins valkeyInstall 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 | none |
| Ports | 6379 |
| Service | valkey (supervisord, priority 20) |
| Volume | valkey-data -> ~/.valkey |
| Install files | layer.yml only |
| Variable | Value |
|----------|-------|
| VALKEY_URL | redis://127.0.0.1:6379 |
| Variable | Template Value | Resolved Example |
|----------|---------------|-----------------|
| REDIS_URL | redis://{{.ContainerName}}:6379 | redis://ov-valkey:6379 |
Pod-aware: same-container consumers receive redis://localhost:6379, cross-container consumers receive redis://ov-valkey:6379. When ov config runs, REDIS_URL is automatically injected into the global deploy.yml env for service discovery (Redis-compatible protocol).
See /ov-image:layer for env_provides field docs.
valkey (RPM, from Remi modular repo, module valkey:remi-9.0)# image.yml
my-app:
layers:
- valkey
ports:
- "6379:6379"
/ov-infrastructure:redis -- Redis alternative (same port 6379)/ov-distros:valkey-test (disabled image)Use when the user asks about:
/ov-image:layer — layer authoring reference (tasks, vars, env_provides, tests block syntax)/ov-eval:eval — declarative testing framework for the eval: blockdevelopment
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.