Free Video Generation Without Login

generate text or images into ready-to-share videos with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. casual creators, marketers, students use...

Security Scan

The skill's declared purpose (server-side free video generation) mostly matches its actions, but there are inconsistent metadata and instruction details that could lead to unexpected local probing and automatic sharing of user files/URLs with an external API.

Purpose & Capability

The skill claims to generate and export videos and requires a single credential (NEMO_TOKEN), which fits the stated purpose. However the SKILL.md metadata and runtime instructions reference local install-path detection (~/.clawhub, ~/.cursor/skills/) and a config path (~/.config/nemovideo/) that were not listed in the registry's top-level requirements — that mismatch is unexplained and unnecessary for basic video upload/rendering.

Instruction Scope

Instructions explicitly call an external API (mega-api-prod.nemovideo.ai) and instruct the agent to: use NEMO_TOKEN if present or automatically obtain an anonymous token, upload files (multipart or URL), stream SSE, and derive headers from this file's YAML frontmatter and by inspecting install paths. The install-path probing could require checking the user's home directories, which is outside the minimal scope of 'generate video' and may reveal local environment details. The skill will also transmit user-provided files or URLs to a third-party service; that data flow is legitimate for this skill but may be unexpected for users if not made explicit.

Install Mechanism

No install spec and no code files (instruction-only). This reduces risk from arbitrary downloads or disk writes.

Credentials

Only NEMO_TOKEN is declared as required, which is proportionate. But the runtime instructions will fetch an anonymous token automatically if NEMO_TOKEN is absent, and derive attribution headers using local path detection. The anonymous-token flow and header derivation are reasonable for service access/attribution, but they involve contacting an external domain and (potentially) probing local paths that were not declared as required config paths.

Persistence & Privilege

The skill is not always-enabled and is user-invocable. It does not request elevated persistence or modify other skills/configurations in the provided instructions.

What to consider before installing

Before installing, consider: (1) The skill uploads files and/or fetches URLs you provide to a third-party domain (mega-api-prod.nemovideo.ai). Do not send sensitive/private media unless you trust that service and its privacy policy. (2) The skill will use NEMO_TOKEN from env or automatically obtain an anonymous token — understand what that token allows (access, credits, and what account it maps to). (3) The SKILL.md instructs the agent to probe install paths to set an attribution header — this could reveal whether you have certain tools/paths in your home directory; if you don't want that, ask the skill author to stop filesystem probing or remove those headers. (4) There is a metadata inconsistency: registry said no config paths but SKILL.md references ~/.config/nemovideo/ and install-path detection — ask the publisher for clarification and a privacy/security policy or source. (5) Test with non-sensitive sample files first. If you cannot verify the service or the publisher, treat the skill as untrusted and avoid uploading private content or providing environment tokens.

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"
• "generate a 30-second promo video from"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Free Video Generation Without Login — Create and Export Videos Instantly

Send me your text or images and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a short product description or three brand images, type "generate a 30-second promo video from my product photos", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter prompts and fewer images tend to produce faster, cleaner results.

Matching Input to Actions

User prompts referencing free video generation without login, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-video-generation-without-login, 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 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 Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Common Workflows

Quick edit: Upload → "generate a 30-second promo video from my product photos" → Download MP4. Takes 30-60 seconds 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 30-second promo video from my product photos" — 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.