Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Shell Image Video
v1.0.0RunningHub AI 工作流集成 — 图片换脸、Wan2.2 动作迁移、动作迁移升级版、150帧高清舞蹈视频。Use when asked about face swap, motion transfer, dance video generation, or RunningHub workflows.
⭐ 0· 275·1 current·1 all-time
by@lygjoey
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The description and SKILL.md target RunningHub face-swap and motion-transfer workflows, which legitimately require a RunningHub API key and media tools. However, the skill metadata declares no required environment variables or binaries while the SKILL.md explicitly lists RUNNINGHUB_API_KEY, ffmpeg, and ImageMagick. That mismatch is incoherent: a RunningHub integration should declare the API key requirement up front.
Instruction Scope
The runtime instructions tell the agent to run node scripts under ~/.openclaw/workspace/Shell-openclaw-image-video-skill and to call a Workflow API path. But there are no code files in the bundle and no install step to create those scripts or the workspace. The instructions also embed a literal API key value ('7192bd7ed2654d1dbfa24ef0c8576705'), which is a credential present in the docs rather than obtained from the user's environment. Together, missing scripts + embedded key + unspecified network host / endpoints are red flags.
Install Mechanism
There is no install spec (instruction-only), which keeps disk/write risk low. However, because the instructions depend on local node scripts that are not present and on third-party binaries, the skill as provided cannot function as-is. The absence of an install mechanism is inconsistent with the usage instructions.
Credentials
The SKILL.md asks for RUNNINGHUB_API_KEY and external binaries (ffmpeg, ImageMagick) — these are reasonable for this functionality — but the skill metadata did not declare these requirements. Additionally, an apparent API key is embedded in the document as '已预配置', which is poor practice and may expose a credential of unknown provenance; using that key blindly risks leakage, misuse, or unexpected billing. The skill should declare required env vars explicitly and not embed credentials in docs.
Persistence & Privilege
The skill does not request always:true or other elevated persistence. It is user-invocable and allows model invocation (default), which is normal. There is no evidence it modifies other skills or system settings.
What to consider before installing
Do not install or enable this skill as-is. The SKILL.md references node scripts and a workspace path that are not included in the bundle and lists required env vars/binaries that the registry metadata does not declare. Also note the hard-coded API key in the instructions — never trust or use embedded credentials of unknown origin. Ask the publisher to (1) provide the referenced code or a proper install spec, (2) remove the embedded API key and instead require the user to supply RUNNINGHUB_API_KEY explicitly, (3) declare required binaries and environment variables in metadata, and (4) document the RunningHub host/endpoints and privacy/billing implications. Until these are resolved, treating the skill as untrusted is safest; avoid uploading sensitive face data to unknown endpoints and rotate any leaked credentials immediately.Like a lobster shell, security has layers — review code before you run it.
latestvk97fxxyf0xbsdnext7rj304cbx83tb9m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.