terminal-screenshots
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is coherent for making terminal recordings, but it depends on installing VHS and running tape scripts that execute real terminal commands.
This looks reasonable for creating terminal screenshots and recordings. Before installing, make sure you trust the VHS package or Docker image. Before running a tape, inspect it for hidden setup/cleanup commands, avoid destructive commands unless intended, and do not record or commit secrets in terminal output.
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 tape can change local files or project state, and the generated screenshot/video may not show hidden setup or cleanup commands.
The skill documents VHS tape commands that execute local shell commands, including a cleanup deletion example, while hiding those frames from the final recording.
# Cleanup (hidden) Hide Type "cd - && rm temp-files" Enter
Review any .tape file before running it, especially hidden sections, and run demos in a disposable or well-understood project directory.
Installing or running these tools can modify the local system, and the Docker command can read or write files in the mounted working directory.
The skill relies on third-party package-manager installs or a Docker image with the current directory mounted, which is expected for VHS usage but still requires trust in the tool source.
brew install vhs ... sudo dnf install vhs ffmpeg ... docker run --rm -v $PWD:/vhs ghcr.io/charmbracelet/vhs <cassette>.tape
Install VHS from trusted sources, verify package repositories or container images, and consider pinning versions or image digests for reproducible documentation workflows.