4k Free Video

Get free 4K videos ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "export my...

Security Scan

The skill mostly matches a cloud video-export integration (NEMO_TOKEN + API calls), but it advertises '4K' output while its own pipeline description limits output to 1080x1920 and there are small metadata inconsistencies — these mismatches warrant caution.

Purpose & Capability

Name/description promise: 'Export Videos in 4K'. SKILL.md's own cloud-render section states the renderer applies H.264 compression 'up to 1080x1920' (i.e., 1080p), which is inconsistent with a 4K claim. Additionally, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata summary listed no required config paths — a mismatch in declared requirements. Otherwise, requiring NEMO_TOKEN to call nemovideo.ai is expected for this purpose.

Instruction Scope

Instructions are typical for an API-backed video-upload/export tool: create or use a token, create a session, upload files, poll export status, and handle SSE. It instructs the agent to obtain an anonymous token if NEMO_TOKEN is absent (POST to the service) and to include attribution headers. It also suggests detecting install path to set an X-Skill-Platform header (this implies reading or inferring agent install location), which is ambiguous but not inherently malicious. The guidance to 'keep technical details out of the chat' is operationally reasonable but reduces transparency.

Install Mechanism

No install spec and no code files — instruction-only skill. Lowest-risk install profile: nothing is written to disk by the skill itself.

Credentials

Only one declared credential (NEMO_TOKEN), which is proportionate for a cloud video service. However, the SKILL.md frontmatter also mentions a config path (~/.config/nemovideo/) which would allow local config access; the registry listing contradicted that. The skill's behavior to mint an anonymous token if no token exists is expected but means the skill will contact the remote API automatically.

Persistence & Privilege

always:false (no forced inclusion) and normal model invocation behavior. The skill does not request elevated system privileges or permanent presence beyond using a runtime token and session for API calls.

What to consider before installing

This skill behaves like a straightforward API client for nemovideo.ai and legitimately needs a NEMO_TOKEN to operate, but there are two red flags you should weigh: (1) the description promises '4K' output while the skill text says the backend caps outputs at 'up to 1080x1920' — ask the author to clarify or test with a small sample to verify actual resolution; (2) the SKILL.md frontmatter mentions a local config path (~/.config/nemovideo/) even though the registry summary did not—confirm whether the skill will read local files. Before installing or uploading private videos: verify the service domain (mega-api-prod.nemovideo.ai), review the provider's privacy/storage policy, test with non-sensitive clips, and prefer supplying your own NEMO_TOKEN rather than relying on an anonymous token if you need access control or auditing. If the author corrects the 4K claim or explains the 1080p note, and confirms no unexpected local file reads, this assessment could move to benign.

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

• "export a 2-minute travel video recorded on a smartphone into a 4K MP4"
• "export my video in 4K resolution for free without a watermark"
• "exporting videos in 4K resolution at no cost for YouTubers"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

4K Free Video — Export Videos in 4K Free

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

Say you have a 2-minute travel video recorded on a smartphone and want to export my video in 4K resolution for free without a watermark — the backend processes it in about 1-2 minutes and hands you a 4K MP4.

Tip: shorter clips render faster and are less likely to hit free-tier limits.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is 4k-free-video, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise 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.

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

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 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 "export my video in 4K resolution for free without a watermark" — concrete instructions get better results.

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

H.264 codec gives the best balance of quality and file size for 4K exports.

Common Workflows

Quick edit: Upload → "export my video in 4K resolution for free without a watermark" → 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.