Skill flagged — suspicious patterns detected

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

Qwen Video Generation Is Free

v1.0.0

Get AI generated videos ready to post, without touching a single slider. Upload your text prompts (MP4, MOV, WebM, GIF, up to 500MB), say something like "gen...

0· 85·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for vynbosserman65/qwen-video-generation-is-free.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Qwen Video Generation Is Free" (vynbosserman65/qwen-video-generation-is-free) from ClawHub.
Skill page: https://clawhub.ai/vynbosserman65/qwen-video-generation-is-free
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install qwen-video-generation-is-free

ClawHub CLI

Package manager switcher

npx clawhub@latest install qwen-video-generation-is-free
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill claims to generate videos via a cloud rendering backend and all runtime instructions target an external video API (mega-api-prod.nemovideo.ai), which aligns with the described purpose. However, the registry metadata marks NEMO_TOKEN as a required env var while the SKILL.md also documents an automatic anonymous-token flow if NEMO_TOKEN is not present — that mismatch is inconsistent.
!
Instruction Scope
Instructions tell the agent to POST to external endpoints, upload user files, read an environment variable (NEMO_TOKEN) and detect install path to set an attribution header. They also say to 'store the returned session_id' but do not specify where (in-memory vs on-disk). The skill instructs not to show raw tokens to users. Uploading large files (up to 500MB) to an external service is core functionality but is a privacy surface the user should be aware of.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That minimizes install risk.
!
Credentials
The only declared credential is NEMO_TOKEN, which is appropriate for a video service. However, the SKILL.md both expects and auto-generates a token: registry metadata lists NEMO_TOKEN as required/primary, yet the documented flow obtains an anonymous token if none is present. Additionally, the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths—this inconsistency raises questions about where tokens/sessions are persisted and why a config path is needed.
Persistence & Privilege
The skill does not request always:true and does not include an install script, so it has no elevated platform persistence by default. That said, the SKILL.md references storing session_id and a config path in metadata; the location and permanence of stored tokens/session state is unspecified and should be clarified before trusting long-lived credentials on disk.
What to consider before installing
This skill appears to do what it says (upload prompts/files and call a cloud video API), but there are a few things to check before installing or using it: - Data privacy: the skill will upload your media (up to 500MB) to an external service (mega-api-prod.nemovideo.ai). Only proceed if you are comfortable with that provider handling your files. - Token behavior: the registry marks NEMO_TOKEN as required, but the skill can also auto-request an anonymous token if none is present. Decide whether you want the agent to obtain and store anonymous tokens automatically — ask where session_id and tokens will be stored (memory vs ~/.config/nemovideo/) and for how long. - Metadata mismatch: the SKILL.md frontmatter claims a config path (~/.config/nemovideo/) while the registry reported no config paths — verify whether the skill will write to disk and whether that is acceptable. - Attribution headers and path detection: the skill will inspect install paths to set an X-Skill-Platform header. This is low-risk but be aware it examines filesystem paths. - Verify the service: confirm the domain (nemovideo.ai) and the provider's privacy/security policy before sending sensitive content. If you care about privacy or audited provenance, ask the skill author to clarify where credentials/session data are stored and to correct the registry metadata (either require NEMO_TOKEN or document that anonymous token will be obtained). If you are not comfortable with an external service receiving your media, do not install or use this skill.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk974r72wzjxeqxyt2prp0ax1hd858fra
85downloads
0stars
1versions
Updated 6d ago
v1.0.0
MIT-0

Getting Started

Got text prompts to work with? Send it over and tell me what you need — I'll take care of the AI video generation.

Try saying:

  • "generate a short text description of a scene into a 1080p MP4"
  • "generate a 10-second video of a sunset over the ocean with calm music"
  • "generating videos from text prompts using Qwen AI for free for content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

  1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
  2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Qwen Video Generation Is Free — Generate Videos From Text Free

This tool takes your text prompts and runs AI video generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a short text description of a scene and want to generate a 10-second video of a sunset over the ocean with calm music — the backend processes it in about 1-3 minutes and hands you a 1080p MP4.

Tip: shorter and more specific prompts tend to produce more accurate video results.

Matching Input to Actions

User prompts referencing qwen video generation is free, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip SSE?
"export" / "导出" / "download" / "send me the video"→ §3.5 Export
"credits" / "积分" / "balance" / "余额"→ §3.3 Credits
"status" / "状态" / "show tracks"→ §3.4 State
"upload" / "上传" / user sends file→ §3.2 Upload
Everything else (generate, edit, add BGM…)→ §3.1 SSE

Cloud Render Pipeline Details

Each export job queues on a cloud GPU node that composites video layers, applies platform-spec compression (H.264, up to 1080x1920), and returns a download URL within 30-90 seconds. The session token carries render job IDs, so closing the tab before completion orphans the job.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is qwen-video-generation-is-free, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

  • "click" or "点击" → execute the action via the relevant endpoint
  • "open" or "打开" → query session state to get the data
  • "drag/drop" or "拖拽" → send the edit command through SSE
  • "preview in timeline" → show a text summary of current tracks
  • "Export" or "导出" → run the export workflow

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Error Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

Common Workflows

Quick edit: Upload → "generate a 10-second video of a sunset over the ocean with calm music" → Download MP4. Takes 1-3 minutes for a 30-second clip.

Batch style: Upload multiple files in one session. Process them one by one with different instructions. Each gets its own render.

Iterative: Start with a rough cut, preview the result, then refine. The session keeps your timeline state so you can keep tweaking.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 10-second video of a sunset over the ocean with calm music" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, WebM, GIF for the smoothest experience.

Export as MP4 for widest compatibility.

Comments

Loading comments...