Ai Video Generator Free Hd

Turn a short product description or three brand images into 1080p HD video clips just by typing what you need. Whether it's generating HD videos from text pr...

Security Scan

The skill's declared purpose (cloud video generation) matches the runtime instructions (upload, session, render APIs) and its single required credential (NEMO_TOKEN) is reasonable — but minor inconsistencies (declared config path not referenced in the instructions), required custom attribution headers, an unknown source/homepage, and the fact this skill will upload user media to a third-party endpoint warrant caution.

Purpose & Capability

Name/description, required env NEMO_TOKEN, and the API endpoints in SKILL.md are coherent for a cloud video-generation skill. Asking for a session token and upload/render endpoints is expected for this functionality.

Instruction Scope

Instructions are focused on connecting to mega-api-prod.nemovideo.ai, creating/using a NEMO_TOKEN (including anonymous-token flow), creating a session, streaming edits via SSE, uploading media, and exporting — all consistent with the stated purpose. Two things to note: the frontmatter declares a config path (~/.config/nemovideo/) but the SKILL.md text does not explain when/how that path is read or written (inconsistency); and the skill requires adding three attribution headers on every request (X-Skill-Source/Version/Platform), which is unusual but not inherently malicious. The skill will transmit user files and metadata to an external service — expected but privacy-relevant.

Install Mechanism

Instruction-only skill with no install spec and no code files reduces on-disk installation risk. No packages or remote archives are downloaded by the skill itself.

Credentials

Only NEMO_TOKEN is declared as required (primary credential), which is proportional to a service that requires bearer auth. However, the metadata also lists a config path (~/.config/nemovideo/), which implies potential local config access; SKILL.md does not describe reading that path. That mismatch should be clarified because reading config files could expose unrelated secrets.

Persistence & Privilege

always:false and normal autonomous invocation mean the skill does not force permanent inclusion. It does direct the agent to create/use session tokens and store session_id state for in-session operations — normal for a remote-rendering integration.

What to consider before installing

This skill appears to be what it claims (a cloud AI video generator) and requests only one credential (NEMO_TOKEN), but exercise caution before installing: 1) Source and homepage are missing — prefer skills from known publishers or with an official homepage. 2) The skill will upload your images/media to mega-api-prod.nemovideo.ai — review that service's privacy and terms before sending proprietary content. 3) Clarify the declared config path (~/.config/nemovideo/) — ask whether the skill will read or write that directory and inspect its contents if it does. 4) The skill mandates custom attribution headers on every request; that identifies requests as coming from this skill. Confirm you’re comfortable with that telemetry. 5) If you’re concerned about tokens, set NEMO_TOKEN yourself (rather than relying on anonymous-token creation) and avoid storing other sensitive credentials in the same environment. If you want higher assurance, ask the publisher for a homepage, source code, or an explanation of the configPath and header requirements before installing.

Getting Started

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

Try saying:

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

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 Generator Free HD — Generate HD Videos from Prompts

This tool takes your text or images 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 product description or three brand images and want to generate a 30-second HD promo video from my product photos — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 60 words generate faster and more accurate videos.

Matching Input to Actions

User prompts referencing ai video generator free hd, 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	ai-video-generator-free-hd
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

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

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 HD promo video from my product photos" → 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 HD promo video from my product photos" — 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 devices.