Ai Video Editor Hd

edit raw video footage into HD edited videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. YouTubers and content creators use it for edi...

Security Scan

The skill's behavior mostly matches a cloud video-editing service, but there are inconsistencies (metadata vs frontmatter) and a request to access a user config path that isn't justified by the description — worth caution before installing.

Purpose & Capability

The name/description claim cloud-based HD video editing and the SKILL.md exclusively describes API calls to a nemovideo.ai backend — that is coherent with the stated purpose. However, the skill's frontmatter lists a required config path (~/.config/nemovideo/) while the registry metadata shows none; that config path is unnecessary for a purely API-based skill and is an unexplained mismatch.

Instruction Scope

Instructions stay within editing workflow: session creation, SSE chat, upload, export, polling for render status. The agent is instructed to upload user-provided video files to the nemovideo.ai endpoints and to create an anonymous token if NEMO_TOKEN is not present — all of which align with the editing purpose. The SKILL.md does not instruct reading arbitrary system files or unrelated environment variables.

Install Mechanism

No install spec and no code files — instruction-only. That minimizes install-time risk; nothing will be written or downloaded by an install step.

Credentials

The only declared credential is NEMO_TOKEN which is appropriate for a cloud API. But the frontmatter's configPaths (~/.config/nemovideo/) is declared (in the SKILL.md metadata) while registry-level metadata reported none — this is unexplained. Additionally, the skill will POST to an anonymous-token endpoint to mint a token if NEMO_TOKEN is absent, which is reasonable but means the skill can create credentials automatically. The requirement to auto-detect X-Skill-Platform from install path may require inspecting the agent environment.

Persistence & Privilege

always is false and the skill does not request elevated platform privileges or changes to other skills. Autonomous invocation is allowed (default) but not combined with other broad privileges in this package.

What to consider before installing

This skill appears to be an API client for a third-party video-editing service and will upload any videos you give it to mega-api-prod.nemovideo.ai. Before installing: verify the service domain and privacy/retention policy, prefer using the anonymous-token flow rather than placing a long-lived secret in your environment, and avoid uploading sensitive footage until you confirm the provider's trustworthiness. Ask the publisher why the frontmatter lists ~/.config/nemovideo/ (access to user config folders can be unnecessary) and request clarification about token lifetime, where uploads are stored, and whether files are retained long-term.

Getting Started

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

Try saying:

• "edit a 2-minute 1080p phone recording into a 1080p MP4"
• "cut the slow parts, add transitions, and export in HD"
• "editing raw footage into polished HD videos automatically for YouTubers and content creators"

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.

AI Video Editor HD — Edit and Export HD Videos

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

Here's a typical use: you send a a 2-minute 1080p phone recording, ask for cut the slow parts, add transitions, and export in HD, 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 process significantly faster.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-video-editor-hd
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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 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 → "cut the slow parts, add transitions, and export in HD" → 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 "cut the slow parts, add transitions, and export in HD" — 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 HD output.