4k With Session

Get 4K edited videos ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something like "e...

Security Scan

The skill's runtime instructions largely match a cloud video-editing service, but there are several incoherent or unexplained details (notably a 4K claim that contradicts the stated rendering resolution and inconsistent config-path metadata) that you should understand before installing or using it.

Purpose & Capability

The skill claims '4K' editing and 'download 4K MP4', but the Cloud Render Pipeline text says exports are compressed 'up to 1080x1920' (1080p), which contradicts the advertised 4K capability. The declared primary credential (NEMO_TOKEN) is appropriate for a cloud video service, but metadata also references a config path (~/.config/nemovideo/) while the top-level registry summary showed no required config paths — an internal inconsistency.

Instruction Scope

SKILL.md instructs the agent to call external endpoints (authentication, session creation, upload, SSE, render/polling) which is expected. It also directs the agent to derive attribution headers from the YAML frontmatter and to detect the install path to set X-Skill-Platform (this requires inspecting filesystem paths like ~/.clawhub/ or ~/.cursor/skills/). That filesystem inspection is narrow but outside purely 'upload/download' actions and could touch other agent-related directories; there are no instructions to read arbitrary user files or unrelated env vars, and it explicitly says not to print tokens or raw JSON.

Install Mechanism

No install spec or code files are present (instruction-only). That reduces disk-write and installation risk — nothing is downloaded or extracted by the skill itself.

Credentials

Only one credential is declared (NEMO_TOKEN) which aligns with a cloud API token. The instructions also provide a fallback to get an anonymous token via the public auth endpoint; this will create a short-lived token (100 credits, 7-day expiry). The skill references a config path in its YAML frontmatter (~/.config/nemovideo/), which may imply reading or storing local config; the registry summary earlier omitted that path, creating ambiguity. No other unrelated secrets are requested.

Persistence & Privilege

always is false and the skill is user-invocable only. There is no install step and no indication it attempts to persistently modify other skills or global agent settings.

What to consider before installing

This appears to be an instruction-only connector to a cloud video-editing API, but there are a few mismatches and ambiguities you should check before using it: 1) Confirm the actual output resolution — the skill advertises 4K but the pipeline doc says up to 1080x1920 (not 4K). Do not assume true 4K unless the provider confirms it. 2) Decide whether you are comfortable uploading source footage (the skill sends files to https://mega-api-prod.nemovideo.ai); review the provider's privacy/data-retention policy. 3) Be aware the skill will either use an existing NEMO_TOKEN env var or obtain an anonymous token on your behalf (100 credits, 7-day expiry). If you use a personal token, keep it secret; the skill asks not to print tokens but will send them to the third‑party API. 4) The instructions ask the agent to detect installation paths to set an attribution header — this requires reading common skill/install directories; if you prefer not to expose those paths, ask the author to avoid that behavior. 5) There's inconsistent metadata about a local config path (~/.config/nemovideo/) — clarify whether the skill will read or write that folder. If these questions are unanswered or concerning, avoid installing or invoke the skill only in a sandboxed environment or with disposable/anonymous credentials.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 4K MP4"
• "edit this 4K footage and save"

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.

4K With Session — Edit and Export 4K Videos

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

Say you have a 2-minute 4K drone recording and want to edit this 4K footage and save the session so I can come back and make changes later — the backend processes it in about 1-2 minutes and hands you a 4K MP4.

Tip: saving your session lets you return and re-edit without re-uploading the original footage.

Matching Input to Actions

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

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

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

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.

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

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.

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 "edit this 4K footage and save the session so I can come back and make changes later" — concrete instructions get better results.

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

Export as MP4 with H.264 codec to keep 4K quality at a manageable file size.

Common Workflows

Quick edit: Upload → "edit this 4K footage and save the session so I can come back and make changes later" → 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.