Making Video Hd Free Online

create video clips into polished HD videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for creating HD videos...

Security Scan

The skill broadly matches a cloud video-rendering tool, but there are several inconsistencies and unexpected behaviors (metadata mismatches, filesystem checks, token handling, and external uploads) that warrant caution before installation.

Purpose & Capability

The skill claims to be a cloud-based video render/exporter and only needs a NEMO_TOKEN — that is plausible. However registry metadata (requirements listed outside the SKILL.md) says no config paths while the SKILL.md frontmatter declares a config path (~/.config/nemovideo/). Also the SKILL.md requires reading its own YAML frontmatter and detecting the agent's install path (~/.clawhub/, ~/.cursor/skills/) to populate X-Skill-Platform — reading these paths is not obviously required for video rendering and is an extra, surprising access pattern.

Instruction Scope

The runtime instructions instruct the agent to: check the environment for NEMO_TOKEN, otherwise call an anonymous-token endpoint to obtain one; read the SKILL.md frontmatter and detect install paths to set attribution headers; and upload user files to an external API (mega-api-prod.nemovideo.ai). These steps include filesystem checks and network calls beyond simple file upload. The token-acquisition flow and the requirement to read local install paths are scope-expanding and should be justified by the author.

Install Mechanism

Instruction-only skill with no install spec or code files — nothing is written to disk by an installer. This is the lowest-risk install mechanism.

Credentials

The skill only declares one required env var (NEMO_TOKEN), which is proportionate for a cloud API. However the SKILL.md describes an automatic anonymous-token acquisition flow if NEMO_TOKEN is absent, which contradicts the 'required' declaration. The skill will send videos (user content) and auth tokens to an external domain — consider privacy and token handling.

Persistence & Privilege

always:false and no install-time persistence or cross-skill config changes are requested. The skill can be invoked autonomously by the agent (normal platform default) but does not request elevated or permanent presence.

What to consider before installing

This skill appears to be a cloud video renderer, but exercise caution before installing. Specific points to consider: - Source and homepage are missing and the owner is unknown — no provenance to verify safety. - The SKILL.md asks the agent to read the skill's frontmatter and detect local install paths to set X-Skill-Platform; this requires filesystem access and is unusual for a simple video upload workflow. - The registry metadata and the SKILL.md disagree about config paths and token behavior (declares NEMO_TOKEN as required, yet the skill can obtain an anonymous token itself). Ask the author to clarify which is authoritative. - User videos will be uploaded to https://mega-api-prod.nemovideo.ai; consider confidentiality and whether you trust that endpoint. Uploaded files, and any generated tokens, will be sent off-platform. - If you need stronger assurance: request a homepage or repo, ask for an explanation of why filesystem detection is needed, verify the API domain belongs to the vendor, or run the skill in a restricted environment where it cannot read arbitrary local paths. If you cannot verify provenance, treat it as untrusted when handling sensitive video or private data.

Getting Started

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

Try saying:

• "create my video clips"
• "export 1080p MP4"
• "make this into an HD video"

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.

Making Video HD Free Online — Create and Export HD Videos

Drop your video clips in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute raw phone recording, ask for make this into an HD video with transitions and music, 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 clips under 3 minutes render noticeably faster and export in under a minute.

Matching Input to Actions

User prompts referencing making video hd free online, 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: making-video-hd-free-online
• 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 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 "make this into an HD video with transitions and music" — 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 size for 1080p output.

Common Workflows

Quick edit: Upload → "make this into an HD video with transitions and music" → 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.