Video Generator For Beginners

generate text or images into ready-to-share videos with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. first-time video creators use it for cre...

Security Scan

The skill's high-level purpose (cloud video creation) matches the network calls and token use, but there are inconsistencies and a few runtime behaviors (automatic anonymous-token creation, local path/config references, and unclear token storage) that merit caution before installing.

Purpose & Capability

The skill is a cloud video generator and only declares one credential (NEMO_TOKEN), which is consistent with contacting an external rendering backend. However the SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) for the backend while the registry metadata earlier reported no required config paths — this mismatch is inconsistent and should be clarified.

Instruction Scope

Runtime instructions instruct the agent to check for NEMO_TOKEN and, if missing, automatically POST to an anonymous-token endpoint to obtain a token which will be used for all API calls. The instructions also reference reading the SKILL.md frontmatter and detecting local install paths (~/.clawhub, ~/.cursor/skills) for attribution headers, and allow uploading files by supplying local filesystem paths (multipart '-F "files=@/path"'). These behaviors imply the skill may access local paths and create/handle tokens at runtime — acceptable for a cloud upload flow but also a potential avenue for unexpected local file access or token persistence. The SKILL.md says 'Don't expose tokens' but does not specify where/how tokens or session IDs are stored.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk by an installer step in the manifest (lowest install risk).

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv), which is proportionate for a cloud API. However the SKILL.md's frontmatter also lists a config path (~/.config/nemovideo/) that could be used to persist tokens/configs. The skill also instructs obtaining an anonymous token via API when NEMO_TOKEN is absent — users should verify whether that anonymous token or any resulting token/session is saved locally or transmitted elsewhere.

Persistence & Privilege

The skill is not forced-always and does not request elevated platform privileges. Autonomous invocation is enabled (default) but is not by itself a red flag. There is no explicit instruction to modify other skills or system-wide settings.

What to consider before installing

This skill appears to do what it says (upload user media to a cloud renderer), but proceed with caution. Before installing or using it: 1) Confirm you trust the backend domain (mega-api-prod.nemovideo.ai) because your uploads and any generated token/session will be sent there. 2) Ask the maintainer (or inspect runtime behavior) whether the anonymous token or session_id is stored on disk (e.g., ~/.config/nemovideo/) and where it is written. 3) Be careful uploading sensitive files — the skill uploads user-provided media to the cloud service. 4) Clarify the manifest inconsistency (registry metadata says no configPaths but the skill frontmatter lists one). 5) If you need stronger assurances, request the skill to explicitly state where/if it persists tokens, and whether uploads are encrypted and retained or deleted from the provider. If you cannot verify these, treat the skill as capable of accessing and transmitting any local files you point it to and only use it with non-sensitive media.

Getting Started

Share your text or images and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "generate my text or images"
• "export 1080p MP4"
• "create a 30-second intro video from"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Video Generator for Beginners — Create Videos from Text or Images

Drop your text or images in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short paragraph describing your topic, ask for create a 30-second intro video from my product description, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — start with a single clear sentence as your prompt — simple inputs produce the most predictable results.

Matching Input to Actions

User prompts referencing video generator for beginners, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...	Action	Skip 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-generator-for-beginners
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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.

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute export workflow

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Common Workflows

Quick edit: Upload → "create a 30-second intro video from my product description" → Download MP4. Takes 1-2 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 "create a 30-second intro video from my product description" — concrete instructions get better results.

Max file size is 200MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across social platforms and devices.