ov-coder/skills/asciinema/SKILL.md
Terminal session recorder (asciinema). Use when working with the asciinema layer.
npx skillsauth add overthinkos/overthink-plugins asciinemaInstall 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) |
| Depends | none |
RPM: asciinema
Records terminal sessions as .cast files (asciicast v2 format). Recordings capture timing, input, and output — can be replayed with asciinema play, uploaded to asciinema.org, or converted to GIF/video.
RPM: asciinema · PAC: asciinema · DEB: asciinema — full parity.
# image.yml or layer.yml
layers:
- asciinema
Used by ov eval record start --mode terminal for terminal recording sessions. Also available standalone via asciinema rec.
ov eval record# Start recording a terminal session
ov eval record start <image> -n demo --mode terminal
# Send commands to the recorded terminal
ov eval record cmd <image> "echo hello" -n demo
# Stop and copy to host
ov eval record stop <image> -n demo -o demo.cast
# Play back
asciinema play demo.cast
Also available via the dev-tools layer (which includes asciinema among many other tools). This standalone layer is for images that need terminal recording without the full dev-tools bundle.
/ov-selkies:sway-browser-vnc (via sway-desktop metalayer)/ov-openclaw:openclaw-sway-browser (via sway-desktop metalayer)/ov-openclaw:openclaw-ollama-sway-browser (via sway-desktop metalayer)/ov-selkies:selkies-desktop (via selkies-desktop metalayer)/ov-selkies:selkies-desktop-nvidia (via selkies-desktop metalayer)/ov-advanced:record — Terminal recording via asciinema (start, stop, cmd)/ov-advanced:record — ov eval record start --mode terminal uses asciinema/ov-coder:dev-tools — Also includes asciinema (larger layer)Use when the user asks about:
asciinema layer/ov-build:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov-build:eval — declarative testing (eval: block, ov eval image, ov eval live)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).