4k Best Generator Free

Skip the learning curve of professional editing software. Describe what you want — generate a 4K video from my script about ocean scenery — and get 4K MP4 vi...

Security Scan

The skill's declared purpose (cloud 4K video generation) aligns with its runtime instructions and requested token, but there are small mismatches in the metadata and a few privacy/operation details you should review before installing.

Purpose & Capability

The skill's name/description (generate 4K videos) matches the API endpoints and workflows spelled out in SKILL.md. Requesting a single service credential (NEMO_TOKEN) is appropriate for a cloud video service. However the skill metadata lists a required config path (~/.config/nemovideo/) while the runtime instructions do not actually reference reading that config; also the metadata declares NEMO_TOKEN as required even though the instructions include an anonymous-token fallback flow if NEMO_TOKEN is absent. These are minor inconsistencies.

Instruction Scope

The instructions tell the agent to: check env for NEMO_TOKEN, create an anonymous token via a network POST if absent, create and use a session, upload user files (up to 500MB) via multipart or URLs, poll SSE endpoints, and detect local install paths (~/.clawhub/, ~/.cursor/skills/) and read the skill's own frontmatter. Uploading user files to the remote service is central to the skill, but it means user files (including anything the user supplies) will be transmitted off-host. Detecting/install-path presence requires checking specific directories in the user's home — broader filesystem probing than strictly necessary for video generation and worthy of explicit user consent.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written by an installer in the package metadata.

Credentials

Only one credential (NEMO_TOKEN) is declared as required, which is proportional for a cloud API. However the instructions include an anonymous-token generation step so the skill can operate without a pre-set NEMO_TOKEN; the metadata's insistence that NEMO_TOKEN is required is therefore inconsistent. No unrelated secrets or many environment variables are requested.

Persistence & Privilege

always:false and default autonomous invocation are normal. The skill does not request persistent system-wide privileges or modify other skills. It will, however, keep and use a session_id for job polling as part of normal operation.

What to consider before installing

This skill appears to do what it says — send your prompts/clips to a cloud service to generate 4K video — but review these points before installing: - Confirm the API domain (mega-api-prod.nemovideo.ai) is one you trust. The skill will send any uploaded files to that external service. - Be cautious about uploading sensitive files (private videos, confidential audio). Uploaded content is transmitted and stored off your machine by the service. - The skill uses or creates a NEMO_TOKEN (it can POST anonymously to obtain a short-lived token). If you prefer using your own account, set NEMO_TOKEN in your environment; otherwise anonymous tokens (100 free credits, 7-day expiry per the instructions) will be generated. - The metadata and instructions have small inconsistencies (metadata lists a config path and a required env var even though the instructions can generate a token). These are likely sloppy but worth noting — ask the publisher to clarify if you need strict guarantees about how tokens and config are handled. - The skill will check for presence of local install paths (~/.clawhub/, ~/.cursor/skills/) to report platform attribution; this requires probing those directories in your home. If you want to avoid any filesystem checks, don't install or run the skill. If you plan to use it, test with non-sensitive sample media first and verify retention/privacy policies of the remote service before uploading real content.

Getting Started

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

Try saying:

• "generate my text prompts or clips"
• "export 4K MP4"
• "generate a 4K video from my"

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.

4K Best Generator Free — Generate Free 4K Videos

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

Say you have a short text description or a 30-second video clip and want to generate a 4K video from my script about ocean scenery — the backend processes it in about 1-3 minutes and hands you a 4K MP4.

Tip: shorter input clips generate faster and maintain sharper 4K upscaling.

Matching Input to Actions

User prompts referencing 4k best generator free, 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.

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

• X-Skill-Source: 4k-best-generator-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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.

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

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)

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 4K video from my script about ocean scenery" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best balance of 4K quality and file size.

Common Workflows

Quick edit: Upload → "generate a 4K video from my script about ocean scenery" → Download MP4. Takes 1-3 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.