Nm Scry Vhs Recording

Generate terminal recordings using VHS tape files, produces GIF outputs

Security Scan

The skill's requirements and instructions are consistent with a tool that validates and runs VHS tape files to produce terminal-recording GIFs; it does not request unrelated credentials or install arbitrary code itself, but running tapes will execute whatever commands the tape contains so caution is required.

Purpose & Capability

Name/description (VHS terminal recordings → GIF outputs) align with the instructions: the SKILL.md describes validating a tape file, checking for the vhs binary, and invoking vhs to produce GIFs. The declared metadata requests no unrelated credentials or binaries.

Instruction Scope

The runtime instructions legitimately require reading and validating the tape file and invoking the vhs tool. However, vhs executes the commands embedded in tape files (including Set Env, cd, and arbitrary command lines), and the skill also documents publishing (--publish) to vhs.charm.sh. These behaviors are expected for a recorder but create a host-execution/data-leakage risk if tapes are untrusted or contain sensitive outputs.

Install Mechanism

This is an instruction-only skill with no install spec or bundled downloads. The SKILL.md recommends standard install commands (go install, brew, package managers) for external dependencies, which is proportionate and expected.

Credentials

The skill does not request environment variables, credentials, or config paths. The documentation references modifying environment inside tape files (Set Env) and PATH guidance, which is appropriate for a tool that spawns a terminal session but requires user attention since tapes can modify environment for the recorded session.

Persistence & Privilege

Skill flags are default (not always:true), no persistent installation or modification of other skills is indicated. Autonomous invocation is allowed by platform default but not otherwise privileged by this skill.

Assessment

This skill appears to do what it claims, but be careful: VHS tape files contain commands that vhs will execute on the host. Before running a tape, review its contents for dangerous commands (network calls like curl/nc/scp, git pushes, rm, sudo, data reads) and for directives that change PATH/HOME or write files. Avoid using --publish on tapes that include sensitive output (publishes to a public endpoint). Use vhs validate and dry runs, run untrusted tapes inside an isolated environment (container/VM) with limited filesystem permissions, and keep Go/bin paths and dependency installs under your control. The scanner found no code artifacts to analyze (instruction-only), which reduces static signals — inspect tape files themselves before execution.

Night Market Skill — ported from claude-night-market/scry. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

VHS Recording Skill

Generate professional terminal recordings from VHS tape files.

When To Use

• Recording terminal sessions with VHS tape scripts
• Creating terminal demo recordings for documentation

When NOT To Use

• Browser-based workflows - use scry:browser-recording instead
• Non-terminal demos or GUI applications

Overview

VHS converts declarative tape files into animated GIFs of terminal sessions. Tape files define commands, timing, and terminal appearance.

Required TodoWrite Items

- Locate and validate tape file
- Check VHS installation status
- Execute VHS recording
- Verify output GIF creation

Module Reference

• See modules/tape-syntax.md for VHS tape file directives
• See modules/execution.md for recording workflow details

Workflow

Phase 1: Validate Tape File

1. Confirm tape file exists at specified path
2. Read tape file contents
3. Verify required directives:
   • Output directive specifies GIF destination
   • At least one action command (Type, Enter, etc.)

Phase 2: Check VHS Installation

which vhs && vhs --version

If not installed:

# Linux/WSL
go install github.com/charmbracelet/vhs@latest

# macOS
brew install charmbracelet/tap/vhs

# Also requires ttyd and ffmpeg

Phase 3: Execute Recording

vhs <tape-file.tape>

VHS will:

1. Parse tape file directives
2. Launch virtual terminal (ttyd)
3. Execute commands with timing
4. Capture frames
5. Encode to GIF using ffmpeg

Phase 4: Verify Output

1. Check GIF file exists at Output path
2. Verify file size is non-zero
3. Report success with output location

Exit Criteria

• GIF file created at specified Output path
• File size indicates successful recording (typically >50KB)
• No error messages from VHS execution

Troubleshooting

Common Issues

If vhs is not found, verify that your Go bin directory is in your PATH (typically ~/go/bin). If the recording fails to start, ensure ttyd and ffmpeg are installed, as VHS depends on them for terminal emulation and video encoding. For "permission denied" errors when writing the GIF, check that the output directory exists and is writable.