Sora Video Generator Free

Turn a short text description of a scene into 1080p AI generated videos just by typing what you need. Whether it's generating short AI videos from text promp...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based text→video generator: it needs a single service token and makes API calls and uploads as expected; no unrelated credentials, installers, or hidden code are present.

Purpose & Capability

Name/description (text→video) lines up with the declared requirement (NEMO_TOKEN) and the SKILL.md which documents a remote rendering API. There are no unrelated env vars or unexpected binaries required.

Instruction Scope

The instructions direct the agent to call the nemovideo API (session creation, SSE, upload, render) and to upload local files when the user provides them. They also describe obtaining an anonymous token automatically if NEMO_TOKEN is absent and reading install/config paths to form headers. This is coherent with the skill purpose, but it does mean user prompts and any uploaded files will be transmitted to an external service and the agent may probe common install paths (~/.clawhub, ~/.cursor, ~/.config/nemovideo) to set headers.

Install Mechanism

Instruction-only skill with no install spec or code files. Lowest install risk — nothing is downloaded or written by an installer as part of the skill bundle.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv). The SKILL.md adds logic to acquire an anonymous token from the nemovideo API if the env var is missing. Requesting a single service token is proportional; however the skill will (if implemented) store/use a token that grants access to the remote rendering service, so users should be aware of the token's privileges and lifetime.

Persistence & Privilege

always is false and the skill does not request elevated platform-wide privileges or modify other skills. It instructs keeping a session_id for operations which is normal for a remote API client.

Assessment

This skill appears internally consistent for a cloud text→video service, but before installing you should: (1) confirm you trust the external API domain (mega-api-prod.nemovideo.ai) and review its privacy/terms, because prompts and any uploaded media will be sent to that service; (2) be aware the skill can obtain an anonymous NEMO_TOKEN for you and use it for up to 7 days—if you prefer, provide your own token or revoke it later; (3) avoid uploading sensitive/private files you don't want transmitted to a third party; (4) note the skill may check common install/config paths to populate headers — if you have sensitive files in those locations, consider that behavior; and (5) if you need stronger guarantees, ask the skill author for a formal privacy policy or for details on whether tokens are persisted beyond the agent session.

Getting Started

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

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 cinematic camera movement"
• "generating short AI videos from text prompts for content creators"

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.

Sora Video Generator Free — Generate Videos from Text Prompts

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

A quick example: upload a short text description of a scene, type "generate a 10-second video of a sunset over the ocean with cinematic camera movement", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter, more specific prompts produce more accurate and consistent results.

Matching Input to Actions

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

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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

• X-Skill-Source: sora-video-generator-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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

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

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.

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)

Common Workflows

Quick edit: Upload → "generate a 10-second video of a sunset over the ocean with cinematic camera movement" → 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 "generate a 10-second video of a sunset over the ocean with cinematic camera movement" — 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.