terminal-screenshots
v1.0.0Create terminal screenshots, animated GIFs, or videos using VHS scripts for documentation, demos, and reproducible CLI visuals.
⭐ 1· 1.8k·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and content describe generating terminal screenshots/recordings using VHS. The SKILL.md only references VHS, ttyd, ffmpeg, package managers, and Docker — all directly related to producing terminal captures.
Instruction Scope
Runtime instructions are limited to installing/running VHS, creating and editing .tape files, and producing outputs (GIF/MP4/PNG). There are no instructions to read unrelated system files, exfiltrate data, or contact unknown external endpoints. The tape syntax does include an Env directive, but that's for setting environment variables inside a recorded session and is consistent with VHS usage.
Install Mechanism
This is an instruction-only skill with no install spec. It recommends standard package managers (Homebrew, dnf, pacman), Docker with an official ghcr.io container, and distro repos — all normal, traceable install methods. Nothing is downloaded from obscure/personal URLs by the skill itself.
Credentials
The skill declares no required env vars or credentials. The only environment interactions are within example tape files (Env PS1 ...) which are appropriate for shaping recorded output. There are no requests for unrelated secrets or config paths.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent privileges or to modify other skills or global agent settings.
Assessment
This skill is a documentation-style guide for using VHS and appears coherent. Before installing or running anything: 1) Only install VHS from official package sources (Homebrew, your distro repos, or the official ghcr.io image). 2) Be careful when recording: VHS captures terminal output — don't run recordings while secrets, API keys, passwords, SSH agent output, or other sensitive content are visible. 3) If using the Docker example (docker run -v $PWD:/vhs ...), remember that mounting your working directory into the container exposes local files to that container; avoid mounting directories with secrets. 4) Review any .tape files you run (they can execute arbitrary shell commands in the recorded session) to ensure they don’t run destructive or sensitive commands. 5) The absence of code files means the skill itself does not install code, but the tool it instructs you to use will run on your machine — treat it like any third-party CLI and audit/install from trusted sources.Like a lobster shell, security has layers — review code before you run it.
latestvk97fx4px6ejtjvbvxmp2gv4kbd80hcay
License
MIT-0
Free to use, modify, and redistribute. No attribution required.