Generator Online Free

Skip the learning curve of professional editing software. Describe what you want — generate a 60-second video from my product description — and get ready-to-...

Security Scan

The skill's network behavior and credential use mostly match a cloud video-generation service, but a few inconsistencies (declared vs. in-file metadata and an unnecessary required env var) and the fact that it will upload user media to an external API warrant caution.

Purpose & Capability

Name/description align with code-free cloud video generation and the SKILL.md instructs calls to a nemo-video backend for upload, render, and export — that is coherent. However, the registry metadata shown to you lists no config paths while the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/), an inconsistency that could indicate sloppy packaging or hidden local-file access.

Instruction Scope

Instructions are focused on network calls to mega-api-prod.nemovideo.ai (session, SSE chat, upload, export) and on uploading user media — this matches the stated purpose. The skill does not instruct broad local file system reads beyond the single config path in the frontmatter. It also instructs automatic anonymous-token acquisition if NEMO_TOKEN is absent, so it can operate without pre-provided credentials.

Install Mechanism

No install spec and no code files (instruction-only) — lowest risk from installation. All runtime behavior is via HTTP calls described in SKILL.md.

Credentials

The skill declares NEMO_TOKEN as a required/primary env var, which is reasonable for a paid API token. But the SKILL.md also describes an anonymous-token flow that obtains a token without any secret, making the 'required' designation questionable. Additionally, the presence of configPaths in SKILL.md (but not in registry requirements) is inconsistent and could enable reading local config if implemented, so the credential/config access scope is unclear.

Persistence & Privilege

always:false and no requests to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but is not combined with elevated persistent privileges.

What to consider before installing

This skill appears to do what it says (upload media, create a session, render on nemovideo.ai), but there are a few things to consider before installing: - Privacy: uploads (videos/images/audio) will be sent to https://mega-api-prod.nemovideo.ai; do not send sensitive or regulated content unless you trust their service and reviewed its privacy policy. - Credentials: it lists NEMO_TOKEN as required but will also obtain an anonymous token if none is present — avoid storing long-lived or high-privilege tokens here unless necessary. Prefer using a limited/ephemeral token if possible. - Inconsistency: SKILL.md frontmatter references a local config path (~/.config/nemovideo/) while registry metadata did not — confirm whether the skill actually reads local files. That could expose local data. - Origin: there is no homepage and the source is unknown; consider verifying the publisher or testing in an isolated environment first. - If you plan to allow autonomous runs, remember the agent may upload files without prompting; restrict what the agent can access or keep autonomous invocation off if you want tighter control.

Getting Started

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

Try saying:

• "generate my text or media"
• "export 1080p MP4"
• "generate a 60-second video from my"

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.

Generator Online Free — Create and Export Videos Online

Drop your text or media 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 prompt or a 30-second clip, ask for generate a 60-second 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 — shorter prompts with clear details produce more accurate results faster.

Matching Input to Actions

User prompts referencing generator online 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 calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

Header	Value
X-Skill-Source	generator-online-free
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.

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)

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 60-second video from my product description" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "generate a 60-second 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.