Ai Video Generator Browser

Skip the learning curve of professional editing software. Describe what you want — generate a 30-second promotional video from this script — and get ready-to...

Security Scan

The skill's requested token and API calls match its stated purpose (cloud video generation), but there are small inconsistencies around local config access and provenance you should verify before use.

Purpose & Capability

The skill is an instruction-only connector to a cloud video-rendering API and declares NEMO_TOKEN as its primary credential — this aligns with the stated purpose. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) and install-path-based attribution logic, while the registry metadata reported no required config paths. Reading a local config directory is not strictly necessary for basic upload/render/download flows and should be justified.

Instruction Scope

Runtime instructions stay on-topic: check NEMO_TOKEN, create/refresh anonymous token if missing via the service's auth endpoint, create a session, use SSE for chat, upload files, and trigger exports. The instructions also direct the agent to read the skill file frontmatter and detect its install path to build attribution headers — this requires access to the agent filesystem/environment. That file/system access is reasonable for attribution but is broader than the core render/upload workflow. The skill explicitly says not to expose tokens or raw API output.

Install Mechanism

No install spec or code files are present (instruction-only). Nothing is written to disk by an installer, so installation risk is low.

Credentials

Only one credential is declared (NEMO_TOKEN), which is proportionate for a cloud video service. However, the frontmatter's configPaths and the requirement to detect install path mean the agent may read local configuration or filesystem locations; that access is not strictly necessary for basic operation and should be considered before granting the skill access to sensitive directories or persistent tokens.

Persistence & Privilege

The skill does not request always:true and does not indicate modifying other skills or system-wide settings. It runs on-demand and uses transient session tokens for operations.

Assessment

This skill appears to do what it says — it talks to a remote nemo-video API and uses a single token (NEMO_TOKEN). Before installing: (1) Confirm the domain (mega-api-prod.nemovideo.ai) is legitimate for the service you expect. (2) Avoid supplying a long-lived or highly privileged NEMO_TOKEN unless you trust the service; prefer ephemeral/anonymous tokens or scoped tokens and rotate them after use. (3) Ask whether the skill will read ~/.config/nemovideo/ or other local files; if you prefer to keep local configs private, deny file access or run the skill in a sandbox. (4) Check the service's privacy/terms for uploaded media (you may be uploading videos up to 500MB). (5) If you need higher assurance, request the skill's source or a signed publisher and verify the API endpoints and attribution headers the skill will send. Overall it's coherent with its purpose but verify provenance and local-file access before granting tokens or filesystem permissions.

Getting Started

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

Try saying:

• "generate my text prompts or clips"
• "export 1080p MP4"
• "generate a 30-second promotional video from"

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.

AI Video Generator Browser — Generate and Export Videos Online

This tool takes your text prompts or clips and runs AI video generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a short text description of a product launch scene and want to generate a 30-second promotional video from this script — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter text prompts with clear scene descriptions produce more accurate results.

Matching Input to Actions

User prompts referencing ai video generator browser, 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.

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

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

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

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)

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

Common Workflows

Quick edit: Upload → "generate a 30-second promotional video from this script" → 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 30-second promotional video from this script" — 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 and websites.