Video Editing With 4k

Cloud-based video-editing-with-4k tool that handles editing and exporting high-resolution 4K video projects. Upload MP4, MOV, AVI, MKV files (up to 500MB), d...

Security Scan

The skill's declared purpose (cloud 4K video editing) matches its instructions and requested credential (NEMO_TOKEN); nothing obvious is requesting unrelated secrets or installing code, but the skill is from an unknown source so exercise caution before uploading sensitive content or granting long-lived credentials.

Purpose & Capability

Name/description, required env var (NEMO_TOKEN), and the endpoints/flows in SKILL.md all align with a cloud video-editing service. The single primary credential requested (NEMO_TOKEN) is appropriate for a remote API service.

Instruction Scope

Runtime instructions describe authenticating (anonymous-token or provided NEMO_TOKEN), creating a session, uploading files, streaming SSE, polling status, and starting renders — all expected. The doc references deriving headers from YAML frontmatter and detecting install-path to set X-Skill-Platform, which could prompt the agent to inspect filesystem paths if implemented; SKILL.md itself does not explicitly instruct reading unrelated local files.

Install Mechanism

No install spec and no code files: instruction-only skill. This minimizes on-disk risk since nothing is downloaded or executed as part of installation.

Credentials

Only NEMO_TOKEN is required and is justified by the documented API calls. Metadata lists a config path (~/.config/nemovideo/) but the skill does not explicitly require arbitrary system credentials or unrelated environment variables.

Persistence & Privilege

always:false and default autonomous invocation are normal. The skill asks to keep session_id for ongoing operations (transient). It does not request persistent platform-wide changes or access to other skills' configs.

Assessment

This skill appears internally consistent for a cloud 4K video editor: it needs a NEMO_TOKEN (or will create a short-lived anonymous token) and then uploads files to the nemovideo.ai API. Before installing or using: 1) Verify the service domain (mega-api-prod.nemovideo.ai) is legitimate for the product you expect. 2) Avoid putting highly sensitive footage or secrets into uploads. 3) If you prefer control, set a dedicated NEMO_TOKEN with minimal scope rather than letting the skill generate/store long-lived tokens. 4) Be aware the agent may need to read small local paths if your environment supplies install-path metadata — deny filesystem access if you don’t want local files exposed. If you want higher assurance, request the skill's provenance or a signed homepage/source before use.

Getting Started

Share your raw 4K footage and I'll get started on AI 4K editing. Or just tell me what you're thinking.

Try saying:

• "edit my raw 4K footage"
• "export 4K MP4"
• "trim the shaky clips, color grade,"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Editing with 4K — Edit and Export 4K Videos

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

Here's a typical use: you send a a 2-minute 4K drone recording, ask for trim the shaky clips, color grade, and export in 4K resolution, and about 1-3 minutes later you've got a MP4 file ready to download. The whole thing runs at 4K by default.

One thing worth knowing — trim clips to under 2 minutes before uploading to speed up 4K processing.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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-editing-with-4k, 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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the shaky clips, color grade, and export in 4K resolution" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, MKV 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 → "trim the shaky clips, color grade, and export in 4K resolution" → 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.