Video Hd

Turn a 2-minute 480p phone recording into 1080p HD quality videos just by typing what you need. Whether it's upscaling low-resolution videos to HD quality or...

Security Scan

The skill's described purpose (cloud video upscaling) matches the runtime instructions, but there are small but meaningful inconsistencies around credential handling and metadata that warrant caution before installing.

Purpose & Capability

The skill's name/description (AI video upscaling) aligns with the API endpoints and upload/export behavior described in SKILL.md. Requesting a single service token (NEMO_TOKEN) is proportionate. However, the frontmatter metadata references a config path (~/.config/nemovideo/) that is not listed in the registry manifest, and the registry lists no required config paths — this mismatch is inconsistent.

Instruction Scope

SKILL.md instructs the agent to upload user-provided videos, create sessions, poll render jobs, and return download URLs — all expected for a cloud render service. It does not instruct reading unrelated local files or other environment variables. Minor scope creep: it asks the agent to derive X-Skill-Platform from install paths (implying the agent may read its own install path), and it also instructs the agent to hide raw API responses and token values from the user (an explicit concealment instruction). These are plausible but worth noting.

Install Mechanism

No install steps or code are included (instruction-only). This is low-risk from an installation perspective because nothing is downloaded or written to disk by an installer spec.

Credentials

Only one credential (NEMO_TOKEN) is declared as required and is relevant to the stated backend. However, SKILL.md contains an anonymous-token flow that will POST to the vendor API and obtain a token if NEMO_TOKEN is not present. Declaring NEMO_TOKEN as required while providing an automatic anonymous-token acquisition is an inconsistency: the skill can operate without a pre-provided token, so the 'required' designation is misleading.

Persistence & Privilege

The skill is not always-on and is user-invocable; it does not request elevated platform privileges or attempt to modify other skills/config. It stores a session_id for the interaction lifecycle, which is expected for this service.

What to consider before installing

This skill will upload any videos you give it to an external backend (mega-api-prod.nemovideo.ai) for processing and requires/uses a service token (NEMO_TOKEN). Notes before installing: 1) Confirm you are comfortable with your video content being sent to that domain (privacy/legal/copyright). 2) The skill declares NEMO_TOKEN as required but will also automatically request an anonymous token from the vendor if one is not provided — be aware this means the skill can obtain and use credentials on your behalf without you supplying them. 3) There is a minor metadata mismatch (a config path appears in the frontmatter but not in the registry manifest) — not necessarily malicious but signals sloppy packaging. 4) Ask the skill publisher for a privacy policy, terms of service, and a clear statement of data retention/processing (how long uploaded media and derived assets are stored, who can access them). If you must process sensitive videos, avoid using the skill until you confirm the backend and policies.

Getting Started

Send me your video clips and I'll handle the AI HD upscaling. Or just describe what you're after.

Try saying:

• "convert a 2-minute 480p phone recording into a 1080p MP4"
• "upscale this video to 1080p HD and sharpen the details"
• "upscaling low-resolution videos to HD quality for YouTubers"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video HD — Upscale and Export HD Videos

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

Say you have a 2-minute 480p phone recording and want to upscale this video to 1080p HD and sharpen the details — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips process faster and use fewer credits.

Matching Input to Actions

User prompts referencing video 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-hd, 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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

Common Workflows

Quick edit: Upload → "upscale this video to 1080p HD and sharpen the details" → 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 "upscale this video to 1080p HD and sharpen the details" — 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.