terminal-screenshots

PassAudited by VirusTotal on May 12, 2026.

Overview

Type: OpenClaw Skill Name: terminal-screenshots Version: 1.0.0 The skill is designed to enable an AI agent to generate terminal screenshots and recordings using the legitimate `vhs` tool. The `SKILL.md` and `README.md` files provide clear instructions for installation and usage of `vhs`, including its domain-specific language for `.tape` files. There is no evidence of prompt injection attempts against the agent, data exfiltration, malicious execution, persistence mechanisms, or obfuscation. Installation steps involve standard package managers and official repositories for `vhs` and its dependencies, which are appropriate for the stated purpose.

Findings (0)

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.

What this means

A tape can change local files or project state, and the generated screenshot/video may not show hidden setup or cleanup commands.

Why it was flagged

The skill documents VHS tape commands that execute local shell commands, including a cleanup deletion example, while hiding those frames from the final recording.

Skill content
# Cleanup (hidden)
Hide
Type "cd - && rm temp-files"
Enter
Recommendation

Review any .tape file before running it, especially hidden sections, and run demos in a disposable or well-understood project directory.

What this means

Installing or running these tools can modify the local system, and the Docker command can read or write files in the mounted working directory.

Why it was flagged

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.

Skill content
brew install vhs ... sudo dnf install vhs ffmpeg ... docker run --rm -v $PWD:/vhs ghcr.io/charmbracelet/vhs <cassette>.tape
Recommendation

Install VHS from trusted sources, verify package repositories or container images, and consider pinning versions or image digests for reproducible documentation workflows.