Free Video Generator High Quality

generate text or images into high quality MP4 with this skill. Works with MP4, JPG, PNG, WebM files up to 200MB. content creators and marketers use it for ge...

Security Scan

The skill's actions (calling a nemo video API, uploading media, creating sessions) match its description and requested NEMO_TOKEN credential, but there are a few minor inconsistencies you should review before installing.

Purpose & Capability

The name/description (generate/export 1080p videos) aligns with the runtime instructions which call a nemo video rendering API and require a NEMO_TOKEN. Requesting an API token for a video rendering backend is proportionate. Note: the SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) while the registry metadata earlier listed no required config paths — this mismatch should be clarified.

Instruction Scope

Instructions are focused on the video workflow: acquire (or use) a token, create a session, upload user media, stream SSE messages, start renders, poll state, and return download URLs. These actions are expected for this functionality. Two points to watch: (1) the skill instructs the agent to detect the install path to populate X-Skill-Platform (this requires reading the agent's installation path / runtime environment), and (2) it tells the agent to save session/token state (location unspecified). Neither is obviously malicious but they do involve reading or writing local state and headers that reveal environment metadata.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — lowest install risk. There is nothing being downloaded or written by an installer here as specified.

Credentials

Only one required environment variable (NEMO_TOKEN) is declared, which is appropriate for an API-backed video service. However, the frontmatter's mention of a config path (~/.config/nemovideo/) implies the skill might read or write local config (e.g., store anonymous tokens or session state). This is plausible but not documented in the registry metadata — ask the author where tokens/sessions are stored and whether any local files are created or read.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It will be able to run autonomously by default (normal for skills). It does instruct saving session state but does not explicitly require persistent system-wide changes.

Assessment

This skill appears to do what it says: it calls a nemo video backend, uploads your media, and returns rendered MP4s. Before installing or invoking it, consider: (1) trust the endpoint (https://mega-api-prod.nemovideo.ai) — your media and any generated anonymous token will be sent there; (2) provide your own NEMO_TOKEN if you have one, or be aware the skill will generate an anonymous token (100 free credits, 7-day expiry); (3) ask the skill author to clarify where session tokens and session_id are stored (in-memory vs written to ~/.config/nemovideo/), and whether any local files are read for platform detection; (4) the skill will add attribution headers that may reveal the agent's install path — if that is a concern, request an option to disable or anonymize those headers. If you need higher assurance, request the author to resolve the frontmatter/registry mismatch about config paths and to document exactly what local state is created or accessed.

Getting Started

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

Try saying:

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

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.

Free Video Generator High Quality — Generate and Export 1080p Videos

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

Say you have a short product description and three product photos and want to generate a 30-second promotional video from my text and images — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 60 words produce the fastest and cleanest results.

Matching Input to Actions

User prompts referencing free video generator high quality, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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: free-video-generator-high-quality
• 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.

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

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.

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 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)

Common Workflows

Quick edit: Upload → "generate a 30-second promotional video from my text and images" → 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 my text and images" — concrete instructions get better results.

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

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