4k Capcut Video Editor

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

Security Scan

The skill is largely coherent with a cloud-based video editing service, but there are multiple internal inconsistencies (notably about promised '4K' outputs vs backend limits), and it will upload user videos to an unknown third-party API — review privacy/trust and capability claims before installing.

Purpose & Capability

Name/description claim cloud 4K editing and the skill requires a NEMO_TOKEN and session with a 'nemovideo' backend which is consistent with a remote video-editing service. However the SKILL.md also states the render pipeline applies compression 'up to 1080x1920' (which is not 4K), so the advertised 4K capability is inconsistent with the documented backend behavior. Registry metadata omitted config path while the SKILL.md lists ~/.config/nemovideo/ — a minor metadata mismatch.

Instruction Scope

The instructions direct the agent to obtain/use a bearer token (NEMO_TOKEN), create sessions, upload user media, open SSE streams, poll export status, and include specific attribution headers. All of that is within expected scope for a cloud editor, but it also means user videos and metadata will be sent to https://mega-api-prod.nemovideo.ai (an unknown third-party domain). The agent is told to auto-acquire an anonymous token if no env var is present, which is reasonable but expands autonomous network activity and data transfer.

Install Mechanism

Instruction-only skill with no install steps and no code files. Nothing is written to disk by an installer here (lowest install risk).

Credentials

Only a single credential (NEMO_TOKEN) is declared as required and is the primary credential — this is proportionate for a remote service. The SKILL.md also references a local config path (~/.config/nemovideo/) in its frontmatter which the registry summary did not list; that discrepancy should be clarified. The skill does not request unrelated credentials.

Persistence & Privilege

always is false and the skill does not request permanent platform-wide privileges. It instructs normal session creation and polling for jobs. Autonomous invocation is allowed (platform default) but not combined with elevated privileges.

What to consider before installing

Before installing, consider: (1) Privacy/trust — this skill uploads your raw video files to https://mega-api-prod.nemovideo.ai (an unknown backend). Only proceed if you trust that service and have checked its data retention/privacy terms. (2) Capability mismatch — the top-level text promises '4K' exports but the backend section mentions compression up to 1080x1920; ask the author to confirm true maximum resolution and sample outputs. (3) Credential source — NEMO_TOKEN is required; confirm where that token should come from and whether the anonymous-token endpoint is legitimate. (4) Metadata mismatch — the SKILL.md lists a config path (~/.config/nemovideo/) while registry metadata omitted it; ask for clarification. (5) If you need stronger assurance, request the skill's source/homepage, privacy policy, sample rendered outputs, and a clear explanation of what data is stored or shared on the backend. If any of these answers are unsatisfactory, do not install or use the skill with sensitive videos.

Getting Started

Ready when you are. Drop your raw video clips here or describe what you want to make.

Try saying:

• "edit a 2-minute 4K phone recording into a 4K MP4"
• "trim the clips, add transitions, and export in 4K resolution"
• "editing and exporting 4K videos with CapCut-style tools for content creators and YouTubers"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

4K CapCut Video Editor — Edit and Export 4K Videos

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

Say you have a 2-minute 4K phone recording and want to trim the clips, add transitions, and export in 4K resolution — the backend processes it in about 1-2 minutes and hands you a 4K MP4.

Tip: splitting long clips into shorter segments before uploading speeds up 4K processing.

Matching Input to Actions

User prompts referencing 4k capcut video editor, 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	4k-capcut-video-editor
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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.

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

Common Workflows

Quick edit: Upload → "trim the clips, add transitions, and export in 4K resolution" → 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 "trim the clips, add transitions, and export in 4K resolution" — 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 for the best balance of 4K quality and file size.