Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

video-stt

v1.0.0

Extract audio from video URLs and transcribe using STT (Speech-to-Text). Supports local Whisper or cloud APIs. Use when: user provides a video URL and wants...

0· 272·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill's name/description match the included scripts (download audio + transcribe). However registry metadata declares no required binaries or env vars while SKILL.md and the scripts clearly require yt-dlp, ffmpeg, Python/uv, and optionally cloud API keys. SKILL.md advertises cloud APIs (OpenAI/Azure/Google) but the provided scripts implement only local Whisper; the shell script exits with 'Cloud API mode not implemented' if --api is used. This mismatch between description/documentation and actual code is an incoherence.
!
Instruction Scope
Runtime instructions tell the agent/user to run the bundled shell script which will download arbitrary URLs and run local transcription. The scripts will attempt to install missing tools (see check_dependencies -> brew install in stt.py, and uv pip install whisper in both scripts). The bash script builds and injects shell variables directly into a python -c one-liner (MODEL, FORMAT, OUTPUT_FILE, AUDIO_PATH) without escaping; that can lead to command/argument injection if untrusted values are passed. The scripts do not exfiltrate data to external endpoints, but they do download remote video content and may call out to PyPI/brew to install packages.
Install Mechanism
There is no formal install spec (instruction-only), which lowers systemic install risk. The code will, however, trigger package installs at runtime: the Python script may call 'brew install' for missing system binaries, and both scripts install Python packages via 'uv pip install whisper'. These are standard package installs (Homebrew/PyPI) — not downloads from arbitrary URLs — but invoking 'brew' without platform checks or consent is fragile and potentially disruptive on non-macOS systems.
!
Credentials
SKILL.md documents optional environment variables (OPENAI_API_KEY, SILICONFLOW_API_KEY) for cloud usage, but the included scripts do not implement cloud API flows (the shell script refuses --api). The registry metadata declares no required env vars; the docs requesting API keys are therefore inconsistent. Asking users to set API keys in docs without code that uses them is confusing and could lead to accidental credential exposure if users set secrets expecting cloud support.
Persistence & Privilege
The skill does not request persistent or platform-wide privileges (always:false). It creates local directories under the skill script directory (audio/ and output/) and may create a local virtualenv (.venv). It doesn't modify other skills or global agent settings.
What to consider before installing
This skill largely does what it claims (downloads video audio and runs local Whisper transcription), but there are several red flags you should consider before using it: - The skill advertises cloud API support and shows environment variable names (OPENAI_API_KEY, etc.) in the README, but the provided scripts do not implement cloud transcription — the shell script will exit on --api. Do not export API keys solely because the docs mention them unless you inspect and trust updated code. - The scripts will attempt to install dependencies at runtime: they call Homebrew ('brew install') and install Python packages via 'uv pip install'. On non-macOS systems 'brew' may not exist and automatic installation may fail or be undesirable. Review and run installs manually in a controlled environment. - The bash script builds a python -c one-liner embedding variables (MODEL, FORMAT, OUTPUT_FILE, AUDIO_PATH) without robust escaping. If you (or an agent) pass untrusted values into those CLI arguments, there's a risk of shell/command injection. Prefer running the Python code from a file with properly passed arguments or sanitize inputs. - The skill will download arbitrary URLs you give it (via yt-dlp) and write audio/transcript files to the skill folder; only run it on content and URLs you trust and in a sandbox if possible. Recommendations: - Inspect the scripts locally, remove or modify the inline python -c usage to a safer invocation, and remove automatic 'brew install' calls or gate them with an explicit prompt. - If you need cloud transcription, either implement the API flow securely (and only then provide API keys) or avoid setting API keys. - Run this skill in a controlled environment (container or VM) the first time so you can observe its behavior and confirm it doesn't attempt unexpected network access or installs. Because of the documentation/code mismatches and the unsafe variable embedding, treat this skill with caution — useful but not turnkey-safe without review.

Like a lobster shell, security has layers — review code before you run it.

latestvk976ymf6cj5g1a48dgpbmdvb9982grwa

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🎬 Clawdis

Comments