Hd Free Video Generation

Turn a short text description of a beach sunset scene into 1080p HD video clips just by typing what you need. Whether it's generating HD videos from text pro...

Security Scan

The skill's declared purpose (cloud video generation) aligns with its runtime instructions and requested credential (NEMO_TOKEN); there are no high-risk install steps, but a couple of small inconsistencies and privacy considerations you should review before installing.

Purpose & Capability

The skill claims to generate HD videos via a cloud API and its instructions exclusively call endpoints on mega-api-prod.nemovideo.ai and require a NEMO_TOKEN bearer token — this is coherent with the stated purpose.

Instruction Scope

Instructions confine actions to the remote video service (session creation, SSE chat, upload, export, polling). They instruct saving a session_id and not to print tokens. One inconsistency: the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this suggests the skill might read or write a local config directory (reasonable for a client), but the registry should have declared it.

Install Mechanism

No install spec or code files — instruction-only skill. This is low-risk because nothing is downloaded or written by an installer step.

Credentials

Only one credential is required (NEMO_TOKEN), which is appropriate for an API-backed video service. The skill also supports obtaining an anonymous token via an API call if NEMO_TOKEN isn't set, so the env var may be optional in practice. Ensure you understand that providing NEMO_TOKEN grants this skill access to your account and billing/credits.

Persistence & Privilege

always:false and normal autonomous invocation. The skill asks to save a session_id (expected for long-running render jobs) but does not request elevated platform privileges or to modify other skills.

Assessment

This skill appears to do what it says: it sends prompts and uploaded media to nemovideo's cloud API and returns download links. Before installing: 1) Confirm you trust the endpoint (mega-api-prod.nemovideo.ai) and understand its privacy/billing policies — everything you send (prompts, uploaded files) will go to that service. 2) Know that supplying NEMO_TOKEN gives the skill access to your account/credits; if you prefer, use the anonymous-token flow (limited credits, 7-day expiry). 3) Ask the publisher for a homepage/source or privacy policy — the registry entry lacks a homepage and the owner is unknown. 4) Clarify the config path behavior (~/.config/nemovideo/) since the registry metadata didn’t declare it; if the skill will read/write local config, make sure you’re comfortable with that. If those points are acceptable, the skill is internally consistent with its stated purpose.

Getting Started

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

Try saying:

• "generate a short text description of a beach sunset scene into a 1080p MP4"
• "generate a 30-second HD video of a city timelapse at night"
• "generating HD videos from text prompts at no cost for content creators"

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.

HD Free Video Generation — Generate HD Videos From Text

Drop your text prompts 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 description of a beach sunset scene, ask for generate a 30-second HD video of a city timelapse at night, 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 scene details produce more accurate results faster.

Matching Input to Actions

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

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 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)

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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 30-second HD video of a city timelapse at night" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.

Common Workflows

Quick edit: Upload → "generate a 30-second HD video of a city timelapse at night" → 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.