Video Generator Free Trial

Turn a short product description and three product photos into 1080p ready-to-share videos just by typing what you need. Whether it's generating short videos...

Security Scan

The skill's declared purpose (cloud video generation) aligns with its runtime instructions and its single required credential (NEMO_TOKEN); it mainly sends user text/images to a third‑party API and does not ask for unrelated secrets or install software locally.

Purpose & Capability

Name/description describe cloud video generation and the skill only requests a single service token (NEMO_TOKEN) and calls nemovideo.ai endpoints — this is coherent. Note: the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata listed 'Required config paths: none' — an inconsistency worth double‑checking but not fatal to purpose alignment.

Instruction Scope

SKILL.md instructs the agent to upload user-provided images/text and to POST to nemovideo.ai endpoints (session creation, upload, SSE, export). This is expected for a cloud video generator, but it clearly transmits user content and session tokens off-device. The skill also tells the agent to read the YAML frontmatter and detect install path (to set attribution headers), which requires filesystem access; that's not strictly necessary for core functionality and is a scope expansion to be aware of.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest risk for unexpected code being written/executed locally.

Credentials

Only one environment variable is required (NEMO_TOKEN), which is proportional to calling an authenticated cloud API. The frontmatter's mention of a config path (~/.config/nemovideo/) contradicts the declared registry 'none' for config paths; confirm whether the agent will read that path before trusting it.

Persistence & Privilege

Skill does not request 'always: true' or other elevated persistence. It can be invoked autonomously (platform default), but it does not request system-wide configuration changes or extra privileges.

Assessment

This skill will upload whatever text and images you give it to mega-api-prod.nemovideo.ai and will use (or obtain) a service token (NEMO_TOKEN) to do so. That behaviour matches a cloud video service, but you should: 1) confirm you are comfortable with those files leaving your device and with the service's privacy/retention policy; 2) verify the nemovideo.ai domain is legitimate before sharing sensitive images or proprietary content; 3) note the SKILL.md mentions reading the skill frontmatter and detecting install paths (filesystem access) — if you want to avoid any local reads, ask how the agent obtains attribution headers; and 4) if you do not already have a NEMO_TOKEN, the skill will request an anonymous token from the remote API (giving 100 free credits, per the doc). The only clear inconsistency is the frontmatter's config path declaration versus the registry's 'none' — ask the publisher to clarify whether the skill will read ~/.config/nemovideo/.

Getting Started

Got text or images to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "generate a short product description and three product photos into a 1080p MP4"
• "generate a 30-second promo video from my product images and description"
• "generating short videos from text prompts or images without editing skills for marketers, small business owners, 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.

Video Generator Free Trial — Generate Videos from Text or Images

Drop your text or images 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 product description and three product photos, ask for generate a 30-second promo video from my product images and 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 scripts under 60 words produce faster and more focused video results.

Matching Input to Actions

User prompts referencing video generator free trial, 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: video-generator-free-trial
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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 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 30-second promo video from my product images and description" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and websites.

Common Workflows

Quick edit: Upload → "generate a 30-second promo video from my product images and 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.