vhs-recorder
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only guide for making VHS terminal recordings, with the main caution that generated tape files can run real local commands when the user executes them.
Before installing or using this skill, make sure you trust the external VHS/ttyd/ffmpeg installation sources. Before running any generated `.tape` file, read the commands it will type, avoid broad cleanup commands, and use a disposable workspace for demos that install packages, run Docker, delete files, or push to git.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A generated or copied tape could disrupt local services or mutate the user's environment if its shell commands are run without review.
This is a user-directed VHS example, but if copied and run it can start a container and then stop every running Docker container on the host, which is broader than the demo container itself.
Type "docker run -d -p 8080:8080 app" → Enter → Wait → Sleep 1s ... Hide Type "docker stop $(docker ps -q)" → Enter
Inspect tape files before running them, prefer scoped cleanup such as stopping a named container, and run demos in a disposable directory or isolated environment.
Installing tools from changing upstream sources can introduce unexpected behavior if the source or latest release changes.
The skill depends on externally installed CLI tools, including an unpinned `@latest` Go install command. This is expected for a VHS recording guide but still affects installation provenance.
- `vhs` installed (`brew install vhs` / `go install github.com/charmbracelet/vhs@latest`) - `ttyd` and `ffmpeg` on PATH
Install VHS, ttyd, and ffmpeg from trusted package sources, and consider pinning versions for repeatable recording workflows.