ov-images/skills/valkey-test/SKILL.md
Test image with Valkey (Redis-compatible) key-value store. Currently disabled. Used for development testing. MUST be invoked before building or troubleshooting the valkey-test image.
npx skillsauth add overthinkos/overthink-plugins valkey-testInstall 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.
Development test image with Valkey in-memory data store.
| Property | Value |
|----------|-------|
| Base | fedora |
| Layers | agent-forwarding, supervisord, valkey |
| Platforms | linux/amd64, linux/arm64 |
| Ports | 6379 (Valkey) |
| Status | disabled (set enabled: true in image.yml) |
Used for testing the Valkey layer (Redis-compatible fork). Runs as a supervisord service on port 6379.
/ov-layers:valkey — Valkey data store/ov-layers:supervisord — Process manager/ov-images:fedora — parent base image/ov-images:fedora-test — sibling test image (also disabled)/ov:build — build the valkey-test image/ov:service — manage the supervised valkey serviceMUST be invoked when the task involves the valkey-test image or Valkey service testing.
/ov: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.