Skill flagged — suspicious patterns detected

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

Seedance + Waoo 短视频流水线

v1.1.4

自动化短视频工作流（story-to-video pipeline）：从剧本/分镜到生成、字幕 ASR、TTS、合并交付，支持 Seedance / Vidu / MiniMax 多厂商路由。

⭐ 1· 104·0 current·0 all-time

by@wusyu

MIT-0

Download zip

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

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

Name/description match the actual code and instructions: many scripts implement storyboard/prompt generation, first-image, video submit/poll/download, ASR/TTS checks and config guidance. Requiring vendor API keys in the pipeline config (not as environment variables) is expected for a multi-vendor media pipeline.

✓

Instruction Scope

SKILL.md and scripts instruct the agent to read pipeline config/state files, generate artifacts, run local node scripts, spawn helper binaries (ffmpeg/tsx) and call vendor APIs to submit/poll/download media — all within the stated pipeline scope. Checkpoints and user-approval steps are explicit and limit autonomous actions.

✓

Install Mechanism

No install spec; code is instruction-and-script-only. That keeps risk lower because nothing is fetched/installed by an installer step. The code may still download media from configured vendor URLs at runtime (expected behavior).

ℹ

Credentials

Registry metadata lists no required env vars, and the skill does not demand platform secrets, but it does expect APIKey values inside a JSON pipeline config (config/pipeline.config.json or user-provided path). This is reasonable but note the difference: secrets are stored in config files rather than declared env vars; the skill checks and uses those API keys to call vendor endpoints.

✓

Persistence & Privilege

always is false and the skill is user-invocable. It runs local scripts that read/write files under workspace and may spawn child processes (ffmpeg/node); this is expected for a media pipeline and does not request system-wide persistent privileges.

Assessment

This skill appears to do what it says, but before installing: - Review and supply pipeline config (config/pipeline.config.json). The skill expects vendor 'API Key' fields in that config; treat them as secrets. - Only put API keys for vendors you trust into the config; don't paste unrelated credentials. - The runtime will read/write files in the workspace and may call out to vendor endpoints to submit/poll/download media. If you want to limit exposure, run it in an isolated/test environment and use test/demo keys first. - The scripts spawn local binaries (ffmpeg/ffprobe/tsx/node). If you do not want local media processing, ensure those binaries are absent or disabled. - If you need stronger assurance, inspect any omitted files (remaining 47 files) for network endpoints or unusual code paths; consider running under restricted network or containerized environment. - Autonomous invocation is allowed by default but the skill's SKILL.md defines explicit checkpoints — still review triggers and only enable runtime autonomy if you are comfortable with that behavior.

✗

scripts/_shared.ts:294