Sora Video Generator Is Free

Turn a short text description like 'a cat walking through a snowy forest' into 1080p AI-generated videos just by typing what you need. Whether it's generatin...

Security Scan

The skill's required credential (NEMO_TOKEN), API calls, and described behavior match its stated purpose (cloud video generation); nothing requested appears disproportionate, though the skill will obtain/use an anonymous token and can upload user files to the remote API.

Purpose & Capability

The skill is a text-to-video front-end and only requests a single service credential (NEMO_TOKEN) and a small config path related to the vendor (~/.config/nemovideo/). These requirements are consistent with calling a third-party video-rendering API.

Instruction Scope

Instructions are focused on authenticating, creating a session, sending SSE messages, uploading media, polling render status, and exporting results. It explicitly tells the agent to POST to the vendor API and (when the user supplies files) upload local files. That file-upload behavior is expected for a video tool but has privacy implications. The instructions also derive an X-Skill-Platform header by checking likely install paths, which requires reading a small set of filesystem locations — unnecessary for core functionality but not malicious.

Install Mechanism

No install script or remote downloads are present; this is instruction-only so nothing will be written to disk by an installer step.

Credentials

Only one environment variable (NEMO_TOKEN) is declared as required and is appropriate for an API-backed video service. A config path (~/.config/nemovideo/) is declared and matches the same vendor domain. No unrelated credentials are requested.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide persistence or modify other skills' configuration. It instructs storing session_id/token for the session (normal for API clients) but does not ask to enable permanent privileged presence.

Assessment

This skill appears internally coherent for a cloud text→video tool, but consider these points before installing: 1) The skill will use or create an anonymous NEMO_TOKEN (100 free credits, ~7 days). If you want control, set your own NEMO_TOKEN rather than letting the skill obtain one. 2) The skill can upload local files when you request an upload — avoid sending sensitive files. 3) It will contact the API host https://mega-api-prod.nemovideo.ai; verify you trust that domain and review its privacy policy and data retention practices. 4) Ask the developer (or documentation) where tokens/session data are stored and whether server-side logs keep uploaded media. If you are uncomfortable with automatic token creation or uploading files to this remote service, do not enable the skill or limit what you send to it.

Getting Started

Send me your text prompts and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "generate a short text description like 'a cat walking through a snowy forest' into a 1080p MP4"
• "generate a 10-second video clip from a text prompt at no cost"
• "generating short AI videos from text prompts 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.

Sora Video Generator Is Free — Generate AI Videos From Text

Drop your text prompts 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 text description like 'a cat walking through a snowy forest', ask for generate a 10-second video clip from a text prompt at no cost, and about 30-90 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter, specific prompts tend to produce more accurate and faster results.

Matching Input to Actions

User prompts referencing sora video generator is free, 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 sora-video-generator-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.

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.

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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 10-second video clip from a text prompt at no cost" — 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 across social platforms.

Common Workflows

Quick edit: Upload → "generate a 10-second video clip from a text prompt at no cost" → Download MP4. Takes 30-90 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.