Ai Video Maker Sora

Get AI generated videos ready to post, without touching a single slider. Upload your text prompts (TXT, DOCX, PDF, PNG, up to 200MB), say something like "gen...

Security Scan

The skill's requirements and runtime instructions largely match a cloud video-generation service (it needs a single NEMO_TOKEN and makes API calls to nemovideo.ai); however there are small inconsistencies around declared config paths and where session/token data is stored that you should review before installing.

Purpose & Capability

Name/description (AI video generation) align with the only requested credential (NEMO_TOKEN) and the documented API endpoints on mega-api-prod.nemovideo.ai. No unrelated credentials or binaries are requested.

Instruction Scope

SKILL.md instructs the agent to auto-connect on first use, use an existing NEMO_TOKEN or obtain an anonymous token via the service's auth endpoint, create sessions, stream SSE, upload user files, and save session_id. These behaviors are consistent with a cloud render workflow, but the doc also references a config path in its frontmatter (~/.config/nemovideo/) and requires attribution headers that must match the frontmatter—the registry metadata earlier said no config paths. The instructions do not instruct reading unrelated system files or other credentials.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. That reduces installation risk (nothing is downloaded or written by an installer step).

Credentials

Only NEMO_TOKEN is declared as required (primary credential), which is proportionate for a cloud API. Caveat: the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) and the instructions say to 'save session_id' and token-derived credentials — it's unclear whether these will be persisted to disk and where. That persistence behavior is not declared consistently in the registry metadata.

Persistence & Privilege

always is false and the skill does not request system-wide privileges. Autonomous invocation (normal default) is allowed but not combined with broad or unrelated credential access. The potential for local persistence (session/token) exists but is not explicitly privileged.

Assessment

This skill appears to be what it says: a cloud-based AI video generator that needs a NEMO_TOKEN to call mega-api-prod.nemovideo.ai. Before installing, consider: 1) Verify you trust the domain (mega-api-prod.nemovideo.ai) and its privacy/terms, since user uploads and generated media are sent there. 2) Decide whether to supply a personal NEMO_TOKEN or let the skill request an anonymous token (the skill can request one on your behalf). Anonymous tokens may be safer but have limited lifetime/credits. 3) Ask or confirm where session_id and tokens are persisted — SKILL.md references ~/.config/nemovideo/ but the registry metadata did not declare config paths; if you prefer no disk persistence, clarify how the agent will store credentials. 4) Avoid uploading sensitive or private files (personal ID, private documents) to the service unless you have reviewed its data handling. 5) If you need higher assurance, request the skill author/source and a privacy/security policy or inspect network traffic to confirm endpoints and headers used.

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 a city skyline"
• "generating videos from text prompts using Sora-style AI for content creators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

AI Video Maker Sora — Generate Videos from Text Prompts

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

Here's a typical use: you send a a short text description of a scene, ask for generate a 10-second video of a sunset over a city skyline, and about 1-3 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

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

Matching Input to Actions

User prompts referencing ai video maker sora, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-video-maker-sora
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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 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 of a sunset over a city skyline" — concrete instructions get better results.

Max file size is 200MB. Stick to TXT, DOCX, PDF, PNG for the smoothest experience.

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "generate a 10-second video of a sunset over a city skyline" → 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.